Page 3: Safety Precautions
 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 MELSEC communication protocol.
Page 4 [Operation Precautions] CAUTION  When changing data and operating status, and modifying program of the running programmable controller from a personal computer connected to an intelligent function module, read relevant manuals carefully and ensure the safety before operation. Incorrect change or modification may cause system malfunction, damage to the machines, or accidents.
Page 5: Conditions Of Use For The Product
PRODUCT in one or more of the Prohibited Applications, provided that the usage of the PRODUCT is limited only for the specific applications agreed to by Mitsubishi and provided further that no special quality assurance or fail-safe, redundant or other safety features which exceed the general specifications of the PRODUCTs are required.
Page 6: Revisions
SH(NA)-080008-A First edition Oct., 2000 SH(NA)-080008-B Reflect the contents of the function version B. Put Windows base software products together from Mitsubishi Programmable Controller MELSEC series to Mitsubishi integrated FA software MELSOFT series. Standardize the name from software package (GPP function) to product name (GX Developer).
Page 7 The manual number is given on the bottom left of the back cover. Print Date Manual Number Revision Aug., 2005 SH(NA)-080008-G Correction About the Generic Terms and Abbreviations, Meanings and Descriptions of Terminology, Section 2.7, Section 3.3.2 POINT Addition Chapter 3 (4E frame) Jun., 2006 SH(NA)-080008-H Correction...
Page 8 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.
Page 9: Table Of Contents
INTRODUCTION Thank you for purchasing the MELSEC-Q/L series programmable controller. This manual describes the functions of the MELSEC-Q/L series programmable controllers. Before using this product, please read this manual and the relevant manuals carefully and develop familiarity with the functions and performance of the MELSEC-L series programmable controller to handle the product correctly.
Page 10: Table Of Contents
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3- 1 to 3- 303 3.1 Message Formats ..........................3- 3.1.1 How to read the command description sections ................3- 3.1.2 Message format and control procedures of QnA compatible 3E frame and 4E frame....3- 3.1.3 Data designation items for QnA compatible 3E frame and 4E frame ..........
Page 11: Table Of Contents
3.8.3 File control execution procedure for the Q/LCPU ................. 3-178 3.8.4 File control execution procedure for the QnACPU................ 3-183 3.8.5 Read directory/file information (command: 1810): for the Q/LCPU..........3-187 3.8.6 Search directory/file information (command: 1811): for the Q/LCPU........... 3-189 3.8.7 Open file (command: 1827): for the Q/LCPU................3-190 3.8.8 Close file (command: 182A): for the Q/LCPU ................
Page 12: Table Of Contents
3.16 Loopback Test............................. 3-271 3.16.1 Commands and contents of character area................3-271 3.16.2 Loopback test (command: 0619)....................3-272 3.17 Registering or Canceling Programmable Controller CPU Monitoring: for Serial Communication Modules....................3-273 3.17.1 Commands and contents of the character area................3-276 3.17.2 Programmable controller CPU monitoring registration (command: 0630)......... 3-282 3.17.3 Canceling programmable controller CPU monitoring (command: 0631) ........3-285 3.17.4 Data transmitted by the programmable controller CPU monitoring function ......
Page 13: Table Of Contents
5.4 Reading and Writing in the Buffer Memory of an Intelligent Function Module........5- 49 5.4.1 Commands and processing ......................5- 49 5.4.2 Understanding the intelligent function module number in the control procedure......5- 50 5.4.3 Reading from the buffer memory of an intelligent function module (command: TR) ....5- 52 5.4.4 Writing to the buffer memory of an intelligent function module (command: TW)......
Page 14 Appendix 2 Reading from and Writing to the Buffer Memory ............. APPX- 17 Appendix 3 Processing Time of the Programmable Controller CPU Side While Communicating Using the MC Protocol..................... APPX- 19 Appendix 3.1 Processing time of the programmable controller CPU (increase in scan time)..APPX- 19 INDEX INDEX- 1 to INDEX-...
Page 15: Relevant Manuals
RELEVANT MANUALS The details on the MELSEC communication protocol can be confirmed in this manual. In addition, use the following manuals according to the intended use. (1) Relevant manuals for the C24 Manual number Manual name (model code) Q Corresponding Serial Communication Module User's Manual (Basic) This manual provides an overview of the module and describes the applicable system configuration, the SH-080006 specifications, the procedures prior to operations, the basic methods of communicating with the external...
Page 16 (3) CPU module user’s manual Manual number Manual name (model code) QnUCPU User's Manual (Function Explanation, Program Fundamentals) SH-080807ENG (13JZ27) Functions, methods, and devices for programming (Sold separately) Qn(H)/QnPH/QnPRHCPU User's Manual(Function Explanation, Program Fundamentals) SH-080808ENG (13JZ28) Functions, methods, and devices for programming (Sold separately) MELSEC-L CPU Module User's Manual (Function Explanation, Program Fundamentals) SH-080889ENG...
Page 17: Manual Page Organization
MANUAL PAGE ORGANIZATION • How to use this manual This manual explains the communication functions via the MC protocol, with each section covering a specific function. (1) To learn about the communication functions using the MC protocol • A summary of the data communication using the MC protocol is explained in Section 1.1 •...
Page 18 • Structure of this manual The explanations of the message formats and the control procedures while communicating through the MC protocol are given in the following format: [Control procedure] (1) Reading eight points of data from internal This is a description of the request from the external relays M100 to M107 in communication in device side for the control...
Page 19: Generic Terms And Abbreviations
GENERIC TERMS AND ABBREVIATIONS This manual uses the following generic terms and abbreviations to explain the serial communication modules, Ethernet interface modules, and devices for data communication unless otherwise specified. (1) Generic terms and abbreviations for CPU modules For the module model names, refer to the manual for the CPU module used. Generic term Description /abbreviation...
Page 20 (2) Generic terms and abbreviations for manuals Generic term/abbreviation Description • Serial communication module Q Corresponding Serial Communication Module User’s Manual (Basic) MELSEC-L Serial Communication Module User’s Manual (Basic) User’s Manual (Basic) • Ethernet interface module Q Corresponding Ethernet Interface Module User’s Manual (Basic) MELSEC-L Ethernet Interface Module User’s Manual (Basic) •...
Page 21: Terms
TERMS The following table outlines the meanings and descriptions of the terms used in this and relevant manuals of the Ethernet Interface module. Term Description One of the message formats for the serial communication module used to communicate ASCII code data through the MC protocol.
Page 22 Term Description Programming tool Generic term for GX Works2 and GX Developer. One of the message formats for the serial communication modules used to communicate ASCII code data through the MC protocol. QnA-compatible 2C frame This is the same message format as the frames for communication through the dedicated protocol of (formats 1 to 4) QnA series serial communication modules.
Page 23: Overview Of The Melsec Communication Protocol
10 0 1 0 1 ERR. CH1. 10BASE-T USER BAT. BOOT RS-232 CH.2 10BASE PULL (FG) O U T (FG) RS-232 +12V MITSUBISHI RS-422 /485 QJ71C24 QJ71E71 QJ71C24 QJ71E71 MELSEC Q25HCPU MELSEC Q25HCPU ERR. ERR. MO DE D LINK MO DE...
Page 24 1 OVERVIEW An external device can access a Q/L series programmable controller using a program with which the programmable controller is accessed via one of the following A/QnA series modules. Accessing the programmable controller via the C24 It is possible to access the programmable controller using a program on the external device via the following A/QnA series modules.
Page 25: Features Of The Melsec Communication Protocol
1 OVERVIEW 1.2 Features of the MELSEC Communication Protocol This section explains the features of the MC protocol. The data communication using the MC protocol is a function that enables the reading/writing of data from/to the programmable controller CPU in order to control and monitor the programmable controller equipment from the external device side.
Page 26 1 OVERVIEW In a system using -Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H, MELSECNET/10, and Ethernet, an external device can access programmable controller CPUs of other stations over the respective network. The C24 is equipped with the programmable controller CPU monitoring function. By using this function, the programmable controller CPU status and data in the device memory can be sent to an external device at constant intervals, upon the occurrence of a mechanical error, or when certain conditions are satisfied.
Page 27: Types And Applications Of Data Communication Frames
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL This chapter explains the data communication using the MC protocol when an external device reads data from and writes data to a programmable controller CPU using the C24/E71.
Page 28 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL A compatible 1C and A compatible 1E frames These frames have the same message structure as when accessing the programmable controller CPU using an A series computer link module or Ethernet interface module. By utilizing the software for data communication on the external device that has been created for the A series programmable controllers, Q/L/QnACPUs linked by multidrop connection or network connection, and programmable...
Page 29: Accessible Range Of Each Data Communication Frames
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL When accessing via the C24 The external device accesses the programmable controller CPU using frames with a format number selected in the "Communication protocol setting" in the switch settings using the programming tool. When any of Formats 1 to 4 is selected, access is enabled using each of the four types of frames shown above and data communication is performed by the transmission/reception of command messages and response messages...
Page 30 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL (1) When using the C24 The network represents CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H, MELSECNET/10, or Ethernet. (2) When using the E71 The network represents CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H, MELSECNET/10, or Ethernet.
Page 31: How To Read The Control Procedures Of The Mc Protocol
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2.3 How to Read the Control Procedures of the MC Protocol This section explains the control procedures when an external device accesses the programmable controller CPU using the MC protocol. (1) Transmission of command messages Data communication through the MC protocol is performed using half-duplex communication.
Page 32: Access Timing Of The Programmable Controller Cpu Side
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2.4 Access Timing of the Programmable Controller CPU Side The following diagram illustrates the access timing of the programmable controller CPU side when an external device accesses the programmable controller CPU via the C24/E71.
Page 33 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL POINT (1) Note that when data is read/written from/to the external device while the programmable controller CPU is in operation, the scan time of the programmable controller CPU increases for the amount of time it takes to process the command from the external device.
Page 34: Setting Method For Writing To The Programmable Controller Cpu During Run
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2.5 Setting Method for Writing to the Programmable Controller CPU during RUN This section explains the setting for writing data from an external device to the running programmable controller CPU via the C24/E71. (1) Setting of the C24 Enable the "Online Change"...
Page 35: Accessing Other Stations
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2.6 Accessing Other Stations This section provides an overview on how to access programmable controllers of other stations that are connected via CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H, MELSECNET/10 and Ethernet. 2.6.1 Accessible programmable controllers of other stations The following tables summarize the accessible modules and modules that can act as message relays in a network when accessing programmable controllers of other...
Page 36 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL (b) CC-Link IE Field Network Model name Head Module LJ72GF15-T2 (c) MELSECNET/H, MELSECNET/10 Model name MELSECNET/H QJ72LP25-25, QJ72LP25G, QJ72LP25GE, QJ72BR15 remote I/O station MELSECNET/10 AJ72QLP25(G), AJ72QBR15, A1SJ72QLP25, A1SJ72QBR15, AJ72LP25(G/GE), remote I/O station AJ72BR15 6 Only reading/writing of the intelligent function module’s buffer memory is available for the MELSECNET/10 remote I/O stations.
Page 37 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL (2) Modules that can act as relays between the networks Model name CC-Link IE Controller QJ71GP21-SX, QJ71GP21S-SX Network CC-Link IE Field QJ71GF11-T2, LJ71GF11-T2, QS0J71GF11-T2 Network QJ71LP21, QJ71LP21-25, QJ71LP21S-25, QJ71LP21G, QJ71LP21GE, QJ71BR11, MELSECNET/H QJ71NT11B (MELSECNET/H mode) QJ71LP21, QJ71LP21-25, QJ71LP21S-25, QJ71LP21G, QJ71LP21GE, QJ71BR11 (MELSECNET/10 mode)
Page 38: Example Of Accessible Station When Each Frame Is Used
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2.6.2 Example of accessible station when each frame is used The following examples show some other stations whose programmable controllers are accessible. In the diagrams, the following symbols are used for each station. When the E71 is included in a network system, it is configured as a normal station (the "Ns"...
Page 39 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL (When stations connected to external devices are the Q/L/QnACPUs) 2 - 13 2 - 13...
Page 40 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL Station accessible from an external device External device connection station 1Ns4 2Ns3 2Ns4 1Mp1 1Ns3 2Mp1 4Ns1 2Ns2 A compatible 1E frame A compatible 1C frame QnA compatible 2C frame QnA compatible 3E frame 4E frame QnA compatible 3C frame QnA compatible 4C frame...
Page 41 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL Station accessible from an external device External device connection station 1Ns4 2Ns3 2Ns4 1Mp1 1Ns3 2Mp1 4Ns1 2Ns2 A compatible 1E frame A compatible 1C frame QnA compatible 2C frame QnA compatible 3E frame 4E frame QnA compatible 3C frame QnA compatible 4C frame...
Page 42: Example Of Designating Data Items For Accessing Other Station Designated Within Each Data Communication Frame
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2.6.3 Example of designating data items for accessing other station designated within each data communication frame This section shows examples of designating the "Network number", "PC number", "Request destination module I/O number" and "Request destination module station number"...
Page 43 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL When the external device connection station is 1) Designated value when accessing from an external device Data name 1Ns4/ 2Ns3/ 2Ns4/ 1Mp1 1Ns3 2Mp1 4Ns1 2Ns2 Network number PC number Request destination module I/O No. 03FF Request destination module station No.
Page 44 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL When the external device connection station is 5) Designated value when accessing from an external device Data name 1Ns4/ 2Ns3/ 2Ns4/ 1Mp1 1Ns3 2Mp1 4Ns1 2Ns2 Network number PC number Request destination module I/O No. 03FF Request destination module station No.
Page 45: Precautions On Data Communication
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2.7 Precautions on Data Communication This section explains some precautions that should be observed when performing data communication between an external device and the C24/E71. 2.7.1 When using E71 (1) Input signals of the E71 Perform read/write only when the following signals on the E71 are on.
Page 46 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL (8) When the E71 is loaded on the MELSECNET/H remote I/O station Communicate using the QnA compatible 3E frame or 4E frame. Communication cannot be performed using the A compatible 1E frame. Accessing other stations relaying through the E71 loaded on the remote I/O station, or accessing other stations relaying between E71 cannot be performed from the MELSECNET/H remote master station.
Page 47: When Using C24
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2.7.2 When using C24 (1) Conditions under which the transmission sequence of the C24 goes into the initial status The transmission sequence of the C24 returns to the initial status under the following conditions.
Page 48: Time Chart And Communication Time Of The Transmission Sequence Of The Serial Communication Module
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2.8 Time Chart and Communication Time of the Transmission Sequence of the Serial Communication Module The diagram below shows a communication time chart when an external device accesses the programmable controller CPU via the C24. (1) An external device accesses the programmable controller CPU on which the C24 is loaded (a) Reading data (In this example, the massage wait time is set)
Page 49 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL REMARKS The communication between the C24 and the programmable controller CPU is always performed after END. Therefore, the scan time becomes longer according to the communication time (the time to interrupt to the programmable controller CPU).
Page 50 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL (2) Transmission time of transmission sequence This section explains how to roughly estimate the time from when an external device starts data transmission till when the result is returned from the C24. Refer to Section 2.8 (1) in the previous page for the contents of T0 to T5.
Page 51: Transmission Time When Accessing Other Stations Via Cc-Link Ie Controller Network Cc-Link Ie Field Network, Melsecnet/H, Melsecnet/10
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2.9 Transmission Time When Accessing Other Stations via CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H, MELSECNET/10 This section explains the transmission time (T1) when accessing the programmable controller of another station on CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H, MELSECNET/10.
Page 52 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL (Worst-case transmission delay time: MELSECNET/H mode) Transmission time (T1) = {(12 + 5 + 10 + 5) 2 + 9 6 + ((2/1) -1) 9 2) + 50} 1 (ST ·  ·...
Page 53 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL (2) For MELSECNET/H (Remote I/O network) and MELSECNET/10 (Remote I/O network) Transmission time (T1) = (Transmission delay time + 1 link scan time or internal processing time)  (n + 1) When this value is more than the internal processing time.
Page 54: Compatibility With Multiple Cpu Systems
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2.10 Compatibility with Multiple CPU Systems This section explains communication using the MC protocol when the QCPU is configured as a multiple CPU system. POINT Read this section if the QCPU is configured as a multiple CPU system. Refer to the QCPU User's Manual (Multiple CPU System) first when using the C24/E71 with a multiple CPU system QCPU.
Page 55 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL (Example) POINT By setting the routing parameter (communication path) in advance, access to programmable controllers on the following network systems is also available. • CC-Link IE Controller Network • CC-Link IE Field Network •...
Page 56 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL (4) Stations that can access to the communication frame for the MC protocol (a) The stations that can access the MC protocol communication frame are indicated, including access with respect to a multiple CPU system. Use the following frames when accessing a non-control CPU in a multiple CPU system.
Page 57 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL [When using the E71] When accessing stations in the Range 4), set each station linked by multidrop connection to Format 5. Multidrop connection External device … Network No.1 Network No.n … (Relay station) Ethernet (Q series C24 installable station) Range 1...
Page 58: Compatibility With The Serial Communication Function In The Cpu Module
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2.11 Compatibility with the Serial Communication Function in the CPU Module (1) Serial Communications Function (a) The serial communications function is a function for connecting the RS-232 interface of the CPU module with an external device, and for monitoring and controlling the operation of the CPU module from the external device by communications through the MC protocol.
Page 59 2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL (b) The commands available for the serial communication function are listed below. For the devices that can be accessed and their ranges, refer to Section 3.3.1 (3). —— Command Number of points Description, processing (Subcommand) accessed...
Page 60: Compatibility With Programmable Controller Cpu With Built-In Ethernet Port
2 DATA COMMUNICATION USING THE MELSEC COMMUNICATION PROTOCOL 2.12 Compatibility with Programmable Controller CPU with Built-In Ethernet Port The programmable controller CPU with built-in Ethernet port can perform MC protocol communication through its built-in Ethernet port. From an external device such as a personal computer or HMI (Human Machine Interface), device data of the CPU module can be read or written using the MC protocol.
Page 61 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME This chapter explains how to specify the formats and data of messages, and the restrictions when performing MC protocol data communication with the C24/E71 using the frames shown below.
Page 62: Message Formats
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.1 Message Formats This section describes the message format for each command when data communication is performed using QnA compatible 3E/3C/4C frames or 4E frame. 3.1.1 How to read the command description sections The following explains how to read the message explanation diagrams shown in each of the command description sections in Sections 3.3.2 to 3.18.
Page 63: Message Format And Control Procedures Of Qna Compatible 3E Frame And 4E Frame
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.1.2 Message format and control procedures of QnA compatible 3E frame and 4E frame This section explains the message format and control procedures when data communication is performed using QnA compatible 3E frame or 4E frame for the E71. (1) Data format The data format for communications between the E71 and external devices is composed of “Header”...
Page 64 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (4) Subheader structure The following shows the structure of the Subheader field. QnA compatible 3E frame Command message Response message ASCII codes Command message Response message Binary codes 4E frame Command message Response message...
Page 65 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME When using ASCII code in QnA compatible 3E frame 1) When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area A...
Page 66 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 2) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area C Text (Command) Q header Request data section...
Page 67 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) When using binary code in QnA compatible 3E frame 1) When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area A...
Page 68 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 2) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area C Text (Command) Request data section Q header...
Page 69 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (c) When using ASCII code in 4E frame 1) When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area A Text (Command)
Page 70 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 2) When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area C Text (Command) Request data Subheader...
Page 71 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (d) When using binary code in 4E frame 1) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area A Text (Command)
Page 72 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 2) When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area C Text (Command) Subheader Q header...
Page 73: Data Designation Items For Qna Compatible 3E Frame And 4E Frame
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.1.3 Data designation items for QnA compatible 3E frame and 4E frame This section explains common data items in the application data section in each message and how to specify them when data communication is performed using QnA compatible 3E frame or 4E frame for the E71.
Page 74 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Request destination module I/O No., Request destination module station No. Specify this when the programmable controller CPU for the access station is as follows: • A programmable controller CPU for a multiple CPU system •...
Page 75 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (6) Request data section, response data section In the request data section, designate the corresponding data (head device, read/write range, write data, etc.) for when the external device has designated the commands and sub-commands shown above using communication based on MC protocol.
Page 76: Message Formats And Control Procedures Of Qna Compatible 3C Frame
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.1.4 Message formats and control procedures of QnA compatible 3C frame This section explains the control procedures and message formats of each protocol format when data communication is performed using QnA compatible 3C frame for the C24.
Page 77 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Communication in format 1 (for communication in ASCII code) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area A...
Page 78 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area C (Data name) –...
Page 79 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) Communication in format 2 (for communication in ASCII code) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area A...
Page 80 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area C (Data name) –...
Page 81 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (4) Communication in format 3 (for communication in ASCII code) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area A...
Page 82 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area C (Data name) –...
Page 83 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (5) Communication in format 4 (for communication in ASCII code) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area A...
Page 84 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area C (Data name) –...
Page 85: Message Formats And Control Procedures Of Qna Compatible 4C Frame
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.1.5 Message formats and control procedures of QnA compatible 4C frame This section explains the control procedures and message formats of each protocol format when data communication is performed using QnA compatible 4C frame for the C24.
Page 86 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (1) Communication in format 1 (for communication in ASCII code) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area A...
Page 87 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area C (Data name) –...
Page 88 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Communication in format 2 (for communication in ASCII code) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area A...
Page 89 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area C (Data name) –...
Page 90 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) Communication in format 3 (for communication in ASCII code) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area A...
Page 91 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area C (Data name) –...
Page 92 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (4) Communication in format 4 (for communication in ASCII code) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area A...
Page 93 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Character area C (Data name) –...
Page 94 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (5) Communication in format 5 (for communication in binary code) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Sum check is performed within this range.
Page 95 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME When the external device writes data to the programmable controller CPU on the local station External device side Programmable controller CPU side (Command message) Sum check is performed within this range. (excluding additional codes) (Ex.) When the result of the addition is 464 Data section...
Page 96: Data Designation Items For Qna Compatible 3C/4C Frames
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.1.6 Data designation items for QnA compatible 3C/4C frames This section explains common data items in each message and how to specify them when data communication is performed using QnA compatible 3C/4C frames for the C24.
Page 97 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME The following shows the message structure when sending EOT or CL. Formats 1 to 3 Format 4 Format 5 The transmission sequence can be initialized by the transmission sequence initialization (command: External device side External device side...
Page 98 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) Number of data bytes (for QnA compatible 4C frame format 5) The number of data bytes is used to inform the external device of the total number of bytes of data, excluding additional codes, between the frame ID number and data section or the frame ID number and complete code (error code).
Page 99 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME [Example] External device (Multidrop connection) Q series C24 Q series C24 Q series C24 Q series C24 Station number 0 Station number 1 Station number 2 Station number 31 PC number FF PC number FF PC number FF...
Page 100 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT (1) When the global function described in Section 3.10 is used, the designation of the station number in the protocol is "FF"/FF When a number from 0 to 31 (00 to 1F ) is designated, X1A/X1B of the designated station only is turned ON;...
Page 101 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (c) PC number 1) Data communication in ASCII code A value within the range shown below is converted to a 2-digit (hexadecimal) ASCII code and sequentially transmitted beginning from the most significant digit.
Page 102 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 2) Data communication in binary mode The higher three digits of the four-digit input/output signals of the objective programmable controller CPU, or two bytes of 03FF data, are transmitted in the order, low byte (L: bits 0 to 7) to high byte (H: bits 8 to 15).
Page 103 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Local station number 1) During communication in ASCII code, "00" is used for transmission. 2) During communication in binary code, the 1-byte value "00 " (0) is used for transmission. POINT When the external device and programmable controller CPU system configuration is m:n and data communication is performed by QnA compatible 3C frames or QnA...
Page 104 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (8) Sum check code The sum check code represents the low byte (8 bits) of the result of binary adding up (summing) the data within the sum check range (refer to Sections 3.1.4 to 3.1.5) in the message.
Page 105 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (Example 2) When data is read using QnA compatible 4C frame format 5 Data section (Corresponds to character area A) (Data name) External device side – (Example) Sum check is performed within this range.(excluding additional codes) =205 The sum check becomes “05”(ASCII code 30 , 35...
Page 106 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (11) Error code An error code tells the external device that the programmable controller CPU processing of the request it sent ended abnormally. 1) Data communication in ASCII code The error code is converted to a 4-digit (hexadecimal) ASCII code and sequentially transmitted beginning from the most significant digit.
Page 107 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME The numerical values in the symbols (< >, [ ] ) shown at the right side of the station in the figures provide the following information. < > : Station number of the C24 loaded to the corresponding station [ ] : Head input/output signal of the C24 loaded to the corresponding station Meaning of the symbols indicated by the arrows to each station in the...
Page 108 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME The external device connection station and access destination are explained in the section that describes the data communications formats in the QnA compatible 4C frames. The following diagrams show examples of external device connection stations sending the transmission data shown in the description of each format in Section 3.1.5 and the programmable controller CPU accessed by the external devices.
Page 109: Character Area Transmission Data
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.1.7 Character area transmission data This section explains how to transmit the bit device data and word device data handled in the character areas, as well as the order of transmission when communicating data between an external device and the programmable controller CPU by each command.
Page 110 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) When reading from or writing to a word device memory Each word of the word device memory is expressed in hexadecimal values in 4-bit units sequentially from the higher bit. (Example) Indicating the storage contents of data registers D350 and D351 Device...
Page 111 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Data communication using binary code (a) When reading to or writing from the bit device memory The bit device memory can be read and written in bit units (one device point) or word units (16 device points).
Page 112 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Reading from or writing to a word device memory Each word of a word device memory is designated by 16 bits and the designated number of points from the designated head device are sequentially expressed in one-point units in the order, low byte (L: bits 0 to 7) to high byte (H: bits 8 to 15).
Page 113 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME REMARKS (1) Reading/writing of the extension file register and reading/writing of the buffer memory On-demand data is handled the same way as a word device memory in the word designation. (2) When communicating using ASCII data, follow the steps below to pass character strings from an external device to the programmable controller CPU and output them using the PR command.
Page 114: List Of Commands And Functions For The Qna Compatible 3E/3C/4C Frames And 4E Frame
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.2 List of Commands and Functions for the QnA Compatible 3E/3C/4C Frames and 4E Frame The following table lists the commands and functions used by an external device to access the programmable controller CPU with commands using the QnA compatible 3E/3C/4C frames or 4E frame.
Page 115 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Programmable controller Command Access station (Refer to Section 2.6.1) — CPU status ( executable CC-Link module MELSEC Reference MELSEC During RUN IE Field Safety During NET/10 NET/H intelligent Function remote STOP...
Page 116 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Number of points processed per — Command Description of processing Access Access Access (subcommand) station – 1 station – 2 station – 3 Function This can also be Reads data in the buffer memory used for data Batch read...
Page 117 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Programmable controller Command Access station (Refer to Section 2.6.1) — CPU status ( executable module Reference CC-Link During RUN MELSEC MELSEC Safety IE Field During NET/H NET/10 intelligent Function Write Write...
Page 118 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Number of points processed per communication — Command Description of processing Access Access (subcommand) station-2 station-3 Access station-1 ( Function Directory file information read 1810 (0000) (for 36) Reads file list information.
Page 119 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Programmable controller Command Access station (Refer to Section 2.6.1) — executable CPU status ( module CC-Link IE Reference MELSEC During RUN MELSECN Field Safety During ET/H NET/10 intelligent Write Write Function...
Page 120 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 1 The online change (write during RUN) status can be set to the programmable controller CPU in the following screen of the programming tool. • In case of the C24: "Switch setting for I/O and intelligent functional module"...
Page 121 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 12 To access the built-in Ethernet port of the CPU module, refer to the following. • QnUCPU User’s Manual (Communication via Built-in Ethernet Port) • MELSEC-L CPU Module User's Manual (Built-In Ethernet Function) 13 Monitoring conditions cannot be designated in the Universal model QCPU, CC-Link IE Field Network and the LCPU.
Page 122: Device Memory Read/Write
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.3 Device Memory Read/Write This section describes what to designate in the control procedure when reading and writing to the device memory by explaining with some examples. 3.3.1 Commands, character area contents and device range The following describes the commands, character areas (in binary code, data fields) of the control procedures, and the range of accessible devices when reading and writing to device memory.
Page 123 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Programmable controller — Number of points processed per CPU status communication (refer to (refer to in Section 3.2) Command Description of processing Reference Section 3.2) (subcommand) During RUN Access Access Access...
Page 124 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (a) Data in the character areas when communicating in ASCII code The data order and contents of character areas A, B, and C are identical when the same command is used under the same conditions in the control procedure when communicating using ASCII code.
Page 125 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Data in data fields when communicating in binary code (Example) Reading data Data section (Corresponds to character area A) External device side Data section (Corresponds to character area B) –...
Page 126 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME c) The following items are designated by subcommands. In the following cases, the subcommand is 0000 /0001 • When neither monitor condition and device memory extension are designated. •...
Page 127 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 2) Device code This value identifies the device memory to be read or written. The device codes are shown in the table in (3). b) When data is communicated in ASCII code The device code is converted to a 2-digit ASCII code and sequentially transmitted beginning from the most significant digit.
Page 128 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME a) When data is communicated in ASCII code The number of processed points is converted to a 4-digit (hexadecimal) ASCII code and sequentially transmitted beginning from the most significant digit. (Example) 5 points : Becomes "0005"...
Page 129 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) Device range Device range means devices of the programmable controller CPU that can be accessed. Specify the device and device number that exist in the module targeted for data read or write.
Page 130 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Universal model QCPU and LCPU Device code Classification Device Type Device number range (Default) Remarks ASCII Binary code code Function input – – Hexadecimal – • Cannot be accessed. Internal Function output –...
Page 131 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Safety CPU Device code Classification Device Type Device number range (Default) Remarks ASCII Binary code code Internal Special relay Decimal – system Special register Word Decimal device Input Hexadecimal Output Hexadecimal...
Page 132 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Designate the following device code according to the programmable controller CPU file register configuration when accessing the file register from the external device. 1) When the file register is made up of multiple blocks •...
Page 133 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Writing data to the file register defined in the QnACPU EEPROM can only be performed when all of the following restrictions are cleared. If any of the following restrictions is not cleared, an abnormal completion message will be returned at the point when writing data to the file register is attempted.
Page 134 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME In the case of programmable controller CPUs other than Q/L/QnACPU Device code Device number range (Default) Device Type Remarks ASCII Binary QnA compatible 3C/4C QnA compatible 3E Representation code code frame...
Page 135 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME In the case of other than programmable controller CPUs 1) CC-Link IE Field Network head module Device code Device Type Device number range (Default) Remarks ASCII Binary code code Special relay 000000 to 002047...
Page 136: Multiple Block Batch Read And Batch Write
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.3.2 Multiple block batch read and batch write The examples shown in this section explain the control procedure for reading and writing by randomly designating multiple blocks, where one block consists of n points of a bit device memory (1 point = 16 bits) and a word device memory (1 point = 1 word).
Page 137 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (1) Data order in the character area during the multiple block batch read This section explains how data is ordered in the character areas during multiple block batch read. (a) Data order when communicating in ASCII code (Data name) External device...
Page 138 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Data order in the character area during the multiple block batch write This section explains how data is ordered in the character areas during multiple block batch write. (a) Data order when communicating in ASCII code (Data name) External device...
Page 139 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) Contents of the character areas during multiple block batch read and batch write This section explains what is contained in the character area when a multiple block batch read or batch write function is performed. The contents are the same as when using the other commands, except for the data shown below.
Page 140 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (c) Device code This value identifies the head device memory for each block for which batch read or batch write is performed. The device code for each device is shown in Section 3.3.1(3). 1) Data communication in ASCII code Each device code is converted to 2-digit ASCII code (hexadecimal) and transmitted.
Page 141 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (4) Multiple block batch read (command: 0406) The examples shown in this section explain the control procedure for reading by randomly designating multiple blocks, where one block consists of n points of contiguous bit device memory (1 point = 16 bits) and word device memory (1 point = 1 word).
Page 142 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) The following device memories are read while communicating in binary code • Word device memory : 2 blocks D0 to D3 (4 points), W100 to W107 (8 points) •...
Page 143 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (5) Multiple block batch write (command: 1406) The examples shown in this section explain the control procedure for writing by randomly designating multiple blocks, where one block consists of n points of contiguous bit device memory (1 point = 16 bits) and word device memory (1 point = 1 word).
Page 144 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) The following device memories are written while communicating in binary code • Word device memory : 2 blocks D0 to D3 (4 points), W100 to W107 (8 points) •...
Page 145: Batch Read In Bit Units (Command: 0401)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.3.3 Batch read in bit units (command: 0401) The examples shown in this section explain the control procedure of a batch read command executed on the bit device memory. The order and content of data items of the areas marked by "...
Page 146 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT (1) Designate the number of device points within the following range: When accessing the Q/LCPU on the station where the C24/E71 is loaded (local station), or the Q/LCPU on the station connected on a Q/L series supporting network system (CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H, MELSECNET/10, or Ethernet) (other station)
Page 147: Batch Write In Bit Units (Command: 1401)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.3.4 Batch write in bit units (command: 1401) The examples shown in this section explain the control procedure of a batch write command executed on the bit device memory. The order and content of data items of the areas marked by "...
Page 148 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Writing eight points from internal relays M100 to M107 while communicating in binary code Number of points to be written Turns OFF when four bits are 0. Turn ON when four bits are 1.
Page 149: Random Write In Bit Units (Test) (Command: 1402)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.3.5 Random write in bit units (test) (command: 1402) The examples shown in this section explain the control procedure for writing by designating bit device memories at random. The order and content of data items of the areas marked by "...
Page 150 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Turning OFF internal relay M50 and turning ON output relay Y2F while communicating in binary code Write in bit unit Number of points to be written When set (ON) : 01 When reset (OFF) : 00 (Refer to Section 3.3.1.) (Data name)
Page 151: Batch Read In Word Units (Command: 0401)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.3.6 Batch read in word units (command: 0401) The examples shown in this section explain the control procedure of batch read commands executed on the bit device memory (16bit units) and word device memory (word units) The order and content of data items of the areas marked by "...
Page 152 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Reading the two points (32 bits) from internal relays M100 to M131 while communicating in binary code Number of points to be read (Refer to Section 3.3.1.) (Data name) External device side...
Page 153 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Reading a word device memory (a) Reading the current values of the three points from timers T100 to T102 while communicating in ASCII code Number of points to be read (Refer to Section 3.3.1.) (Data name) External device...
Page 154 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT (1) Designate the number of device points within the following range (for bit devices, one point equals to 16 bits). When accessing the Q/LCPU on the station where the C24/E71 is loaded (local station), or the Q/LCPU on the station connected on a Q/L series supporting network system (CC-Link IE Controller Network, CC- Link IE Field Network, MELSECNET/H, MELSECNET/10, or Ethernet)
Page 155: Batch Write In Word Units (Command: 1401)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.3.7 Batch write in word units (command: 1401) The examples shown in this section explain the control procedure of batch write commands executed on the bit device memory (16bit units) and word device memory (word units) The order and content of data items of the areas marked by "...
Page 156 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Writing two points (32 bits) from internal relays M100 to M131 while communicating in binary code Number of points to be written (Refer to Section 3.3.1.) (Refer to Section 3.1.7.) (Data name) External device side...
Page 157 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Writing to a word device memory (a) Writing three points to D100 to D102 while communication in ASCII code Number of points to be written (Refer to Section 3.3.1.) (Refer to Section 3.1.7.) (Data name) External device...
Page 158 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT (1) Designate the number of device points within the following range. When accessing the Q/LCPU on the station where the C24/E71 is loaded (local station), or the Q/LCPU on the station connected on a Q/L series supporting network system (CC-Link IE Controller Network, CC- Link IE Field Network, MELSECNET/H, MELSECNET/10, or Ethernet) (other station)
Page 159: Random Write In Word Units (Test) (Command: 1402)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.3.8 Random write in word units (test) (command: 1402) The examples shown in this section explain the control procedure of writing data by randomly designating bit device memories (16/32 bit units) and word device memories (1/2 word units).
Page 160 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Writing to the following device memories while communicating in binary code • Word access : D0, D1, M100 to M115 X20 to X2F • Double word access : D1500 to D1501, Y160 to Y17F, M1111 to M1142 Write in word Write 550 W rite 575...
Page 161 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT (1) Designate the number of device points within the following ranges. For a bit device, one word access point is 16 bits and one double word access point is 32 bits.
Page 162: Random Read In Word Units (Command: 0403)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.3.9 Random read in word units (command: 0403) The examples shown in this section explain the control procedure of reading data by randomly designating bit device memories (16/32 bit units) and word device memories (1/2 word units).
Page 163 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3 - 103 3 - 103...
Page 164 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT If an intelligent function module or a programming tool tries to monitor the C24/E71 where conditional monitoring is being performed, the C24/E71 will return an error completion code to the external device. (When unconditional monitoring is being performed, the C24/E71 can perform conditional or unconditional monitoring.) Command Function...
Page 165 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Data order of character areas when monitor conditions are designated 1) Data order while communicating in ASCII code Character area A (Data name) External device side Designate the monitor condition file and step No. Character area A (continued) Designate the monitor condition word Designate the monitor...
Page 166 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 2) Data order while communicating in binary code Character area (corresponding character area A) (Data name) External device side Designate the Designate the monitor condition file and step No. Designate the monitor condition monitor condition...
Page 167 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME REMARKS The following table summarizes the subsequent data that must be designated to the character area depending on whether the subcommand monitor condition is designated or not. Condition designation When monitor condition is When monitor condition is designated not designated...
Page 168 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Monitor condition This value designates the condition under which data is read. The table below summarizes the combinations of monitor conditions that can be designated. (Three conditions cannot be designated at the same time.) Monitor condition File and step number Word device value...
Page 169 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME File No. Description Designation contents 0000 Filename not designated Designated when file and step numbers are not designated in the monitor conditions. 0001 TO 0100 File number Designated when the file number is known. Designated when the file number is retrieved by the C24/E71.
Page 170 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME c) When file and step number are not designated (02 and 04 used) in the monitor conditions, the filename and extension are replaced by a string of spaces or 20 codes even if the monitor condition designated is selected by a subcommand.
Page 171 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME SFC block number and SFC step number These data items designate the SFC block number and SFC step number containing the sequence steps that will determine when to read data (when the designated sequence step is being executed).
Page 172 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (Example) 0000001C when sequence program number 28 is designated. 8000001C when the interrupt pointer I28 is designated. d) When file and step numbers are not designated in the monitor conditions, the sequence step number becomes 00000000 even if the monitor condition designated is selected by a subcommand.
Page 173 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 11) Monitor condition value (for bits) The monitor condition value (for bits) is used for designating whether or not to read data (rising or falling). It can be designated when a subcommand selected that monitor conditions should be designated and the monitor condition designated is a bit device.
Page 174 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME [Control procedure] (a) Reading the following device memories while communicating in ASCII code • Word access : D0, T0, M100 to M115, X20 to X2F • Double word access : D1500 to D1501, Y160 to Y17F, M1111 to M1142 Word units Monitor condition not designated...
Page 175 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Reading the following device memories while communicating in binary code • Word access : D0, T0, M100 to M115, X20 to X2F • Double word access : D1500 to D1501, Y160 to Y17F, M1111 to M1142 Word units Designate Designate...
Page 176 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT Designate the number of access points within the following range. For bit devices, one word access point is 16 bits and one double word access point is 32 bits. For word devices, one word access point is one word and one double word access point is two words.
Page 177 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) Random read in word units (when monitor condition is designated) The examples shown in this section explain the control procedure of reading data by randomly designating bit device memories (16-bit units) and word device memories (word units) with a monitor condition designated.
Page 178 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Reading randomly while communicating in binary code under the following conditions Monitor condition When the value of link register W100 reaches "7B " (123) during step number 1000 of the program file CONB1.QPG is executed. 2) Device memories to be read •...
Page 179 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT Designate the number of access points within the following range. For bit devices, one word access point is 16 bits and one double word access point is 32 bits. For word devices, one word access point is one word and one double word access point is two words.
Page 180: Monitoring Device Memory
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.3.10 Monitoring device memory The monitor data registration function registers the name and number of the devices on the external device to be monitored in the C24/E71. The monitor function reads the data content of the device registered to be monitored from the programmable controller CPU and processes it in the external device.
Page 181 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT The monitor function for device memory can read data in the follow ways. The designation method, contents of each data field in the character areas in the control procedure, and the timing to monitor (read) are the same as when the random read word units function is used.
Page 182 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Monitor data registration (command: 0801) (when the monitor condition is not designated) The examples shown in this section explain how to register monitor data in order to monitor the device memories by randomly designating bit device memories (16/32 bit units) and word device memories (1/2 word units) without a monitor condition (reading condition) designated.
Page 183 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Registering monitor data for the following device memories while communicating in binary code • Word access : D0, T0, M100 to M115, X20 to X2F • Double word access : D1500 to D1501, Y160 to Y17F, M1111 to M1142 Monitor condition not designated Number of points to be registered (Refer to Section 3.3.1.)
Page 184 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) Monitor data registration (command: 0801) (When designating the monitor condition) The examples shown in this section explain the control procedure for registering monitor data in order to monitor the device memories by randomly designating the bit device memories (16/32 bit units) and word device memories (1/2 word units) with the monitor condition (reading condition) designated.
Page 185 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Monitor condition not designated File and step No. designated Word device value designated (Refer to Section 3.3.8.) (Data name) External device side (Example) Number of points to be registered (Refer to Section 3.3.8.) (Refer to Section 3.3.1.) For the number of word access points...
Page 186 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Monitor data is registered in the following ways while communicating in binary code Monitor condition When the value of link register W100 reaches "7B " (123) while step number 1000 of the program file CONB1.QPG is being executed 2) Device memories to be monitored (read) •...
Page 187 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (4) Monitoring registered device memories (command: 0802) The following section explains the control procedure for monitoring a device memory registered using the monitor data registration (command: 0801). The monitoring control procedure is the same regardless of whether or not a monitor condition is designated during monitor data registration.
Page 188 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) When monitoring while communicating in binary code the following device memories with monitor data are registered (Device memories with monitor data registered) • Word access : D0, T0, M100 to M115, X20 to X2F •...
Page 189: Buffer Memory Read/Write
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.4 Buffer Memory Read/Write This function is used to read from and write to the buffer memory of the C24/E71 (including the use of multidrop connection) that is connected to the external device. •...
Page 190 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) Contents of character area The following explains the contents of the character area when the external device reads from or writes to the buffer memory of the C24/E71. (a) Head address This value designates the head address of the range to which data is read (or written).
Page 191: Reading Buffer Memory (Command: 0613)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.4.2 Reading buffer memory (command: 0613) The examples shown in this section explain the control procedure for carrying out a batch read of the C24/E71 buffer memory. The data arrangement and contents of the areas marked with " " in the control procedure diagram differ depending on the module, communication frame and format used.
Page 192 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Reading 10 words from the contents of the addresses 78 to 81 (120 to 129) of the buffer memory area while communicating in binary code Fixed to 0000 Number of words to be read (Refer to Section 3.4.1.) (Data name)
Page 193: Writing To Buffer Memory (Command: 1613)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.4.3 Writing to buffer memory (command: 1613) The examples shown in this section explain the control procedure for carrying out a batch write of the C24/E71 buffer memory. The data arrangement and contents of the areas marked with "...
Page 194: Reading From And Writing To The Buffer Memory Of An Intelligent Function Module
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.5 Reading from and Writing to the Buffer Memory of an Intelligent Function Module The examples shown in this section explain the control procedure for reading/writing data in the buffer memory of an intelligent function module ( 1). This command accesses the buffer memory of an intelligent function module using byte units.
Page 195 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (Example) When the head address is 1E1 : It is converted to 000001E1 sequentially transmitted beginning from E1 The head address is designated according to the following method when reading from and writing to the buffer memory of an intelligent function module.
Page 196 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Number of bytes This value designates 2 bytes  the number of addresses of the area from which data is read (or written) and is designated by even byte. 1) Data communication in ASCII mode The number of addresses ...
Page 197 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (When modules occupy two slots) How many points an intelligent function module occupying two slots can occupy by each slot is predetermined for each module. The module number is designated as the first three digits of the four digits that express the head address of the slot side allocated to a special function module.
Page 198 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (Intelligent function modules of a network system remote I/O station) The module numbers of the MELSECNET/H, MELSECNET/10 remote I/O station special function modules all become the first three digits of the four digits that express the head number of the "input/output signal as seen from the remote I/O station".
Page 199: Accessible Intelligent Function Modules
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.5.2 Accessible intelligent function modules The following table summarizes the intelligent function modules which can be read from/written to the buffer memory using commands "0601" and "1601", along with their "head address"...
Page 200 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Module model name Buffer memory head address (Hexadecimal) Module number when loaded in slot 0 Model AD61 (S1) High-speed Counter Module Model A616AD Analog-Digital Conversion Module Model A616DAI/DAV Digital-Analogue Conversion Module Model A616TD Temperature-Digital Conversion Module 0000 Model A62DA(S1) Digital-Analogue Conversion Module...
Page 201: Reading The Buffer Memory Of An Intelligent Function Module (Command: 0601)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Example of head addresses of an intelligent function module designated by external device The following table shows head addresses designated by external device when Q62DA is used. Address used in FROM/TO Buffer memory Head address...
Page 202 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Reading four bytes from the buffer memory addresses 1 to 2 the Q62DA, whose input/output signal is 30 to 4F (module number: 03 ) while communicating in binary code. POINT (1) Designate the head address and number of bytes within the following ranges.
Page 203: Writing To The Buffer Memory Of An Intelligent Function Module (Command: 1601)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.5.4 Writing to the buffer memory of an intelligent function module (command: 1601) The example shown in this section explain the control procedure for writing to the buffer memory of an intelligent function module. The order and content of data items of the areas marked by "...
Page 204: Programmable Controller Cpu Status Control
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.6 Programmable Controller CPU Status Control This function is used to remotely RUN/STOP/PAUSE/RESET a Q/L/QnACPU, clear the device memory of a Q/L/QnACPU, and read the model name of a Q/LCPU from an external device.
Page 205 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Contents of the character area Here, the contents of the character area when an external device controls the status of the Q/L/QnACPU, are described. (a) Mode This is used to force the Q/L/QnACPU to execute a remote RUN/remote PAUSE.
Page 206: Remote Run (Command: 1001)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.6.2 Remote RUN (command: 1001) The examples shown in this section explain the control procedure of remote RUN. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 207: Remote Stop (Command: 1002)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.6.3 Remote STOP (command: 1002) The examples shown in this section explain the control procedure of remote STOP. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 208: Remote Pause (Command: 1003)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.6.4 Remote PAUSE (command: 1003) The examples shown in this section explain the control procedure of remote PAUSE. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 209: Remote Reset (Command: 1006)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.6.5 Remote RESET (command: 1006) The examples shown in this section explain the control procedure of remote RESET. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 210: Remote Latch Clear (Command: 1005)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.6.6 Remote latch clear (command: 1005) The examples shown in this section explain the control procedure of remote latch clear. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 211: Cpu Model Name Read (Command: 0101)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.6.7 CPU model name read (command: 0101) The examples shown in this section explain the control procedure for reading the model name of the programmable controller CPU. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 212 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME This function reads the model name of the target programmable controller in the form of model name code and model name (for monitor). The model name code and the model name can be read as follows. Content to be read Model name of programmable controller Model name code (hexadecimal)
Page 213: Drive Memory Defragmentation (For Other Station Qnacpu)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.7 Drive Memory Defragmentation (for Other Station QnACPU) An external device uses this function to perform the following operations on the QnACPU drive of another station that stores the program file containing the parameters and sequence programs.
Page 214: Commands And Contents Of Character Area
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.7.1 Commands and contents of character area This section explains the commands used and the character area (data section in communication in binary code) in the control procedure used to defragment the drive memory.
Page 215 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Setting flag This flag indicates whether or not the keyword registered in the designated drive by the user matches the keyword of (a) above. 1) Data communication in ASCII code The values shown below are converted to a 2-digit (hexadecimal) ASCII code and sequentially transmitted beginning from the most significant digit ("0").
Page 216 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (e) Number of clusters to be read This value designates the number of clusters within the drive memory range who are to be read. It is designated in multiples of 16 (10 , 20 ...
Page 217: Reading The Status Of The Drive Memory Usage (Command: 0205)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.7.2 Reading the status of the drive memory usage (command: 0205) The examples shown in this section explain the control procedure to read the usage status of a drive memory. The order and content of data items of the areas marked by "...
Page 218: Drive Memory Defragmentation (Command: 1207)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.7.3 Drive memory defragmentation (command: 1207) The examples shown in this section explain the control procedure for defragmenting the drive memory. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 219 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT (1) The drive memory should be defragmented in the following cases. • When the QnACPU of the designated station is in the STOP status • When files cannot be stored because the drive memory usage status (checked by the command 0205) is scattered (fragmented) In the following cases, an error occurs and an abnormal response is returned.
Page 220: File Control
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8 File Control This function reads, registers, and deletes files in Q/L/QnACPU modules. This function is used for the following. • To read parameters and sequence programs from an external device •...
Page 221 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.1 Commands and contents of character area The following explains the file control procedure commands and what is included in the character area (data section in communication in binary code). (1) Commands The following two tables list the file control commands for the Q/L/QnACPU.
Page 222 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) File control commands for the QnACPU – Number of points Programmable controller processed per CPU status Command communication Processing Reference (subcommand) Access station-2 During RUN During (QCPU as described in Write Write STOP...
Page 223 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Contents of character area The following explains the contents of the character area of the messages described in the sections beginning from Section 3.8.5 when an external device controls the Q/L/QnACPU files.
Page 224 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (c) Drive name and number This data section designates the drive of the Q/L/QnACPU whose files are to be controlled. Refer to Section 3.7.1 for how to designate drive names for QnACPUs and their corresponding drives.
Page 225 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME The file number of an already registered file can be checked using the functions described in Sections 3.8.6, 3.8.16, and 3.8.17. On a QnACPU, when registering a new file, the unused file numbers can be checked using the read file number usage status function described in Section 3.8.16 (3).
Page 226 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (Pattern 2) For mainly QnACPU files • Files to be accessed should be designated using the following data order. File name + Extension + Attribute When this file name is less than 8 characters, append a space (code: ) to the name to make it 8 characters.
Page 227 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (g) Time of last updating and date of last updating This data section indicates the date and time when the current data was registered. 1) Data communication in ASCII code The value shown below is converted to a 4-digit (hexadecimal) ASCII code and sequentially transmitted beginning from the most significant digit (time, year).
Page 228 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME File size This value indicates the size of the current file in number of bytes. 1) Data communication in ASCII code The 2-word value is converted to an 8-digit (hexadecimal) ASCII code and sequentially transmitted beginning from the most significant digit.
Page 229 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Offset address This data designates the head address of the file range for which data is read and written. The address (one address/one byte) is counted from the head (offset address: 0 ) of each file and is designated an even address.
Page 230 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (m) Data written (write same data function): For QnACPU files This data section is for the write same data function, and used to write the same data to the existing QnACPU files. 1) Data communication in ASCII code The value for one word is converted to a 4-digit (hexadecimal) ASCII code and sequentially transmitted beginning from the most significant...
Page 231 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (p) Modification pattern (for changing filename and file size): For QnACPU files This data section designates what data is to be modified when the data (filename, size, date and time created) of the existing file is to be modified. 1) Data communication in ASCII code The value shown below is converted to a 4-digit (hexadecimal) ASCII code and sequentially transmitted beginning from the most significant...
Page 232 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME • Changing the file information in batch (command: 1204; subcommand: 0002) – – – – – – – – – b5 b4 b3 b2 b1 b0 …… Can be designated between 01 to 3F File name and extension modification yes/no designation 0: Do not modify the file name and extension...
Page 233 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME File number usage status: For QnACPU files This data section returns the usage status of the file numbers for 256 files to the external device when reading the usage status of a file number. The data is arranged from the first byte shown below.
Page 234 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME File lock mode: For QnACPU files This flag designates whether or not a file lock is to be forcefully cleared in order to allow access to the designated file from another device. 1) Data communication in ASCII code The value shown below is converted to a 4-digit (hexadecimal) ASCII code and sequentially transmitted beginning from the most significant...
Page 235 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Number of directory characters: For Q/LCPU files This data is used to designate the storage area for files to be read, written, registered, etc. 1) Data communication in ASCII code "0000"...
Page 236: Precautions On File Control
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 4) When a file close instruction is issued for a designated file, the normal closing and forced closing differ as follows. • Normal close This option does not close files that are opened by other modules and devices.
Page 237 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME If there is system protection on the Q/L/QnACPU when using the following functions, an error occurs and an abnormal complete message is returned. Reference Function For Q/LCPU For QnACPU Create new file (filename registration) Section 3.8.10 Section 3.8.20...
Page 238: File Control Execution Procedure For The Q/Lcpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.3 File control execution procedure for the Q/LCPU The following flow charts show the procedures for executing file control on the Q/LCPU. (1) Procedure to read the contents of a file Start (Function name) (Command)
Page 239 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Procedure for creating a new file and writing data to it Start (Function name) (Command) (Reference section) Read directory/file 1810 Section 3.8.5 information or File search Check for file presence (checking file presence) Section 3.8.6 1811...
Page 240 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) Procedure for copying a file Start (Function name) (Command) (Reference section) 1810 Section 3.8.5 Read directory/file information or File search Check for file presence (checking file presence) Section 3.8.6 1811 Copy the file...
Page 241 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (4) Procedure for overwriting data in an existing file Procedure to modify the file information Start (Function name) (Command) (Reference section) 1810 Section 3.8.5 Read directory/file information or File search Check for file presence (checking file presence) Section 3.8.6...
Page 242 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (5) Procedure for deleting a file Start (Function name) (Reference section) (Command) 1810 Section 3.8.5 Read directory/file information or File search Check for file presence (checking file presence) Section 3.8.6 1811 (File found)
Page 243: File Control Execution Procedure For The Qnacpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.4 File control execution procedure for the QnACPU The following flow charts illustrate the procedure for executing file control on the QnACPU. (1) Procedure for reading the contents of a file Start (Function name) (Command)
Page 244 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Procedure for creating a new file and write data to it Procedure for copying the data of an existing file to a new file Start (Function name) (Reference section) (Command) 0203...
Page 245 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) Procedure for overwriting data in an existing file Procedure for modifying the file information Start (Reference section) (Function name) (Command) 0203 File presence read Section 3.8.17 Check file presence and its size 0201 Section 3.8.16 File information read...
Page 246 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (4) Procedure for deleting a file Start (Reference section) (Function name) (Command) 0203 Section 3.8.17 File presence read Check for file presence 0201 Section 3.8.16 File information read 0202 (File found) ( 1)
Page 247: Read Directory/File Information (Command: 1810): For The Q/Lcpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.5 Read directory/file information (command: 1810): for the Q/LCPU The examples shown in this section explain the control procedure for reading the directory and file information. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 248 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Communication in binary code POINT (1) Designate the following items within the following ranges indicated below. The values for these items will also be returned within the following ranges. : 1 ...
Page 249: Search Directory/File Information (Command: 1811): For The Q/Lcpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.6 Search directory/file information (command: 1811): for the Q/LCPU The examples shown in this section explain the control procedure for searching the directory and file information. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 250: Open File (Command: 1827): For The Q/Lcpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.7 Open file (command: 1827): for the Q/LCPU The examples shown in this section explain the control procedure for opening a file. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 251 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) When opening LCPU files (subcommand "0004") The following conditions apply to the example of opening a file below. Keyword AbCd1234 • • • (24 spaces, code: 20 Drive No.
Page 252: Close File (Command: 182A): For The Q/Lcpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.8 Close file (command: 182A): for the Q/LCPU The examples shown in this section explain the control procedure for closing a file. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 253: Read File (Command: 1828): For The Q/Lcpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.9 Read file (command: 1828): for the Q/LCPU The examples shown in this section explain the control procedure for reading a file. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 254 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Communication in binary code (Data name) External device side (Example) (Data name) Programmable controller CPU side (Example) POINT (1) When reading data, the maximum number of bytes per data is predetermined. Read all the data written to the designated file by dividing it into several parts by adjusting the offset address and number of bytes read.
Page 255: Create New File (Command: 1820): For The Q/Lcpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.10 Create new file (command: 1820): for the Q/LCPU The examples shown in this section explain the control procedure for creating a new file. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 256: Write To File (Command: 1829): For The Q/Lcpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.11 Write to file (command: 1829): for the Q/LCPU The examples shown in this section explain the control procedure for writing to a file. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 257 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Communication in binary code (Data name) External device side (Example) (Data name) Programmable controller CPU side (Example) POINT (1) The maximum number of bytes per write operation when writing data is fixed. Write all the data read from the Q/LCPU and stored in the external device to the designated file by dividing it into several parts by adjusting the offset address and number of bytes written.
Page 258: Delete Files (Command: 1822): For The Q/Lcpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.12 Delete files (command: 1822): for the Q/LCPU The examples shown in this section explain the control procedure for deleting a file. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 259 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) When deleting LCPU files (subcommand "0004") The following conditions apply to the example of deleting a file below. Keyword AbCd1234 • • • (24 spaces, code: 20 Drive No.
Page 260: Copy Files (Command: 1824): For The Q/Lcpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.13 Copy files (command: 1824): for the Q/LCPU The examples shown in this section explain the control procedure for copying a file. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 261 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Communication in binary code (Data name) External device side (Example) (Data name) Programmable controller CPU side (Example) (2) When copying LCPU files (subcommand "0004") The following conditions apply to the example of copying a file below. Keyword copy source/destination AbCd1234 •...
Page 262 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Communication in binary code POINT (1) The maximum number of bytes per copy operation when copying is fixed. Write all the data written to the existing file to the newly registered file by dividing it into several parts by adjusting the offset address and number of bytes written.
Page 263: Change Date Of File Creation (Command: 1826): For The Q/Lcpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.14 Change date of file creation (command: 1826): for the Q/LCPU The examples shown in this section explain the control procedure for changing the date of file creation. The order and content of data items of the areas marked by "...
Page 264: Change File Attributes (Command: 1825): For The Q/Lcpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.15 Change file attributes (command: 1825): for the Q/LCPU The examples shown in this section explain the control procedure for changing file attributes. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 265 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) When changing attributes of LCPU files (subcommand "0004") The following conditions apply to the example of changing file attributes below. Keyword AbCd1234 • • • (24 spaces, code: 20 Drive number Filenames whose attributes are to be changed...
Page 266: Read File Information List: For The Qnacpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.16 Read file information list: for the QnACPU (1) Reading the file information list without header statement (command: 0201): For QnACPU The examples shown in this section explain the control procedure for reading file information within the range of designated file numbers.
Page 267 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Reading file information for two files from memory card A (RAM area, drive name: 01 ) file number 10 (A ) while communicating in binary code. Keyword valid Fixed to 0000 Memory card A (Refer to Section 3.7.1.)
Page 268 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Read file information list with header statement (command: 0202): for QnACPU The examples shown in this section explain the control procedure for reading file information within the range of designated file numbers with header. The order and content of data items of the areas marked by "...
Page 269 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Reading file information for two files from memory card A (RAM area, drive name: 01 ) file number 10 (A ) while communicating in binary code. Keyword valid Fixed to 0000 Memory card A (Refer to Section 3.7.1.)
Page 270 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) Read file number usage status (command: 0204): For QnACPU The examples shown in this section explain the control procedure for reading the usage status of a file number. The order and content of data items of the areas marked by "...
Page 271 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Reading the usage status of the memory card A (RAM area, drive name: ) file number usage status while communicating in binary code. Keyword valid Fixed to 0000 Memory card A (Refer to Section 3.7.1.) (Data name)
Page 272: Reading File Presence Information (File Search) (Command: 0203): For The Qnacpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.17 Reading file presence information (file search) (command: 0203): for the QnACPU The examples shown in this section explain the control procedure for searching for the designated file, and reading the file No. and file size if the file is found. The order and contents of data items of the areas marked by "...
Page 273 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) When searching for the memory card A (RAM area, drive name: ) filename "ABC12.QPG" by communication in binary code Keyword valid Fixed to 0000 Memory card A (Refer to Section 3.7.1.) (Refer to Section 3.8.1.) Filename with extension (Data name)
Page 274: Registering And Clearing File Locks (Command: 0808): For The Qnacpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.18 Registering and clearing file locks (command: 0808): for the QnACPU The examples shown in this section explain the control procedure for registering and clearing the following file locks: •...
Page 275 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) When performing file lock registration in normal execution mode for the memory card A (RAM area, drive name: 01 ) file No. 1 with filename "ABC12.QPG" by communication in binary code 0001 (Registration) Normal execution...
Page 276: Reading The Contents Of A File (Command: 0206): For The Qnacpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.19 Reading the contents of a file (command: 0206): for the QnACPU The examples shown in this section explain the control procedure for reading the data written in the designated file. The order and contents of data items of the areas marked by "...
Page 277 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) When reading the 50-byte data beginning from offset address 100 of the memory card A (RAM area, drive name: 01 ) file No. 1 with filename "ABC12.QPG" by communication in binary code Keyword valid Memory card A Fixed to 0000...
Page 278: Creating A New File (Filename Registration) (Command: 1202): For The Qnacpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.20 Creating a new file (filename registration) (command: 1202): for the QnACPU The examples shown in this section explain the control procedure for registering a new file to and reserving a file area on the designated disk. The order and contents of data items of the areas marked by "...
Page 279 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) When registering a new 172-byte file to and reserve a file area on memory card A (RAM area, drive name: 01 ) with filename "ABC12.QPG" by communication in binary code Fixed to 0000 Keyword valid Refer to...
Page 280: Writing To A File (Command: 1203): For The Qnacpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.21 Writing to a file (command: 1203): for the QnACPU (1) Batch write The examples shown in this section explain the control procedure for writing the data of the file that has been read from the QnACPU and stored in the external device to the designated file.
Page 281 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) When writing 416-byte data, beginning from the offset address 7C , to the memory card A (RAM area, drive name: 01 ) file No. 1 with filename "ABC12.QPG"...
Page 282 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Writing the same data (FILL) The examples shown in this section explain the control procedure for writing n- bytes of arbitrary one-word data to the designated file. The order and contents of data items of the areas marked by "...
Page 283 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) When writing 416 bytes of "FFFF ", beginning from offset address 7C , to the memory card A (RAM area, drive name: 01 ) file No. 1 with filename "ABC12.QPG"...
Page 284: Deleting Files (Command: 1205): For The Qnacpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.22 Deleting files (command: 1205): for the QnACPU The examples shown in this section explain the control procedure for deleting an existing file. The order and contents of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 285 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) When deleting existing memory card A (RAM area, drive name: ) with filename "ABC12.QPG" by communication in binary code Fixed to 0000 Keyword valid Memory card A (Refer to Section 3.7.1.) (Refer to Section 3.8.1.) Filename with extension...
Page 286: Copying Files (Command: 1206): For The Qnacpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.23 Copying files (command: 1206): for the QnACPU The examples shown in this section explain the control procedure for writing (overwriting) the data written in an existing file to a new file. The order and contents of data items of the areas marked by "...
Page 287 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) When copying the contents of an existing file in memory card A (RAM area, drive name: 01 ) to a new file by communication in binary code Designate offset address 1E0 for both files and copy 480 bytes of data.
Page 288: Changing The File Information (Command: 1204): For The Qnacpu
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.8.24 Changing the file information (command: 1204): for the QnACPU (1) Changing the file creation date (command: 1204, subcommand: 0000) The examples shown in this section explain the control procedure for changing the date and time when the designated file was last updated.
Page 289 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) When changing the time when memory card A (RAM area, drive name: 01 filename "ABC12.QPG" was last updated by communication in binary code (The file No. is unknown and the time of last update is the QnACPU time.) Fixed to 0000 (Modifies the date and time of last update.) Keyword valid...
Page 290 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Changing the filename, attribute, and file size (command: 1204, subcommand: 0001) The examples shown in this section explain the control procedure for changing the filename, attribute, and file size of the designated file. The order and contents of data items of the areas marked by "...
Page 291 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) When changing the filename and attribute of memory card A (RAM area, device name: 01 ) file No.1 with filename "ABC12.QPG" by communication in binary code (Changes the filename to "ABC1234.QPG" and the attribute to read only.) 0001 ( Modifications of the filename, attribute and file size) Modifications of the filename...
Page 292 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) Batch modification of file information (command: 1204, subcommand: 0002) The examples shown in this section explain the control procedure for changing file information in batches. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 293 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) When changing the filename, attribute, and date and time of last update of memory card A (RAM area, drive name: 01 ) file number 1/filename "ABC12.QPG" by communication in binary code. (Use the date and time of the QnACPU for the date and time of last updating.
Page 294: Registering, Deleting And Reading User Frames: For Serial Communication Modules
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.9 Registering, Deleting and Reading User Frames: for Serial Communication Modules User frames are used to communicate data by making it possible for the user to select the data format for the beginning and end of the messages exchanged between and external device and Q/LCPU.
Page 295 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Contents of the character area The following explains the contents of the character area when an external device registers, deletes, or reads a user frame from the C24. (a) Frame number This value specifies the user frame number to be registered, deleted, or read.
Page 296 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (c) Frame byte count This value designates the number of bytes in the frame to be registered or read. The variable data part is calculated with the 2-bytes of FF as one byte.
Page 297: Registering And Deleting User Frames (Command: 1610)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.9.2 Registering and deleting user frames (command: 1610) The examples shown in this section explain the control procedure for registering user frames to the C24. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 298 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Registering and deleting by communication in binary code (a) Registering a frame with frame number 3E8 for transmitting and receiving ETX + sum check code + CR + LF (codes and order after registration: 03 , F0 , 0D , 0A...
Page 299: Reading User Frames (Command: 0610)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.9.3 Reading user frames (command: 0610) The examples shown in this section explain the control procedure for reading the registered contents (order of registered data) of user frames from the C24. The order and content of data items of the areas marked by "...
Page 300 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Reading the contents registered in frame number 3E8 communication in binary code The contents registered are frames for transmitting and receiving ETX + sum check code + CR + LF. In this example, the lower byte (8 bits) of the binary code obtained by summing the data section except the head frame is designated as the sum check code as 0000...
Page 301: Global Function: For Serial Communication Modules
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.10 Global Function: for Serial Communication Modules The global function turns global signals (X1A/X1B) of the programmable controller CPU of the C24 loaded station connected to an external device over a multidrop link on/off.
Page 302 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Contents of the character area This section explains data in the character area that designates the global signals when an external device turns the global signal on/off. Station number This value designates the station number whose global signal is instructed by the opposite station to be turned on/off.
Page 303: Control Procedure Of The Global Function (Command: 1618)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.10.2 Control procedure of the global function (command: 1618) The examples shown in this section explain the control procedure for turning on/off the global signals to the programmable controller CPU from an external device. The order and contents of data items of the areas marked by "...
Page 304 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Turning on/off the global signals using binary code format 5. (a) Turning on the global signal X1A of all stations in a multidrop link. 0001H (Global signal ON) (Refer to Section 3.8.1.) 1 Designates the station (all stations/one designated station only) whose global signal is to be turned ON and OFF using the station No.
Page 305: Data Transmission To An External Device (On-Demand Function): For Serial Communication Modules
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.11 Data Transmission to an External Device (On-Demand Function): for Serial Communication Modules Functions that request data transmission from the programmable controller CPU to an external device when communicating data in the MC protocol, are referred to as on- demand function.
Page 306: Execution Procedure Of The On-Demand Function
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.11.1 Execution procedure of the on-demand function (1) Execution procedure on the programmable controller CPU side 3 - 246 3- 246...
Page 307 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Execution procedure on the external device side (3) The following describes the timing charts when an on-demand transmission request was issued. In case of full-duplex communication When the C24 is receiving data: The C24 does not transmit any on-demand data is completed before transmitting a response message (STX to) in reply to the command message (ENQ to).
Page 308 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME In case of half-duplex communication: Refer to the User's Manual (Application). When the C24 is receiving data: The C24 does not transmit any on-demand data until the reception of a command message (ENQ to) from the external device is completed.
Page 309: Data Transmission Format Of The On-Demand Function
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.11.2 Data transmission format of the on-demand function The format number of the communication protocol setting by the programming tool of the C24 determines the arrangement of the on-demand data transmitted by the on- demand function.
Page 310 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) On-demand data transmission format in A compatible 1C frame format 4 (4) On-demand data transmission format in QnA compatible 4C frame format 5 POINT To send on-demand data in the format other than above (e.g. user-defined QnA compatible 3C/4C frame format), use the data communication function by the user frames described in the User's Manual (Application).
Page 311: Control Procedure Of The On-Demand Function (Command: 2101)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.11.3 Control procedure of the on-demand function (command: 2101) The examples in this section explain the control procedure for sending on-demand data to an external device with the on-demand function. The arrangement and contents of the data items shown in the control procedure diagram differ depending on the frame and format used in communication.
Page 312 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT (1) When control procedure format 2 is used, the block number should be "00". (2) The number of characters in the transmission data section of the on-demand data is the data length ...
Page 313 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Format 5 (a) When the "Word/byte units designation" in GX Works2 or GX Configurator- SC is set to "0" (word units) The following diagram shows the control procedure when two words are designated as transmission data.
Page 314 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME When the "Word/byte units designation" in GX Works2 or GX Configurator- SC is set to "1" (byte units) The following diagram shows the control procedure when two words (four bytes) are designated as transmission data.
Page 315 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (3) Sample sequence program using the on-demand function (the ONDEMAND instruction) The following is a sample program demonstrating the use of the on-demand function, using the controls described in (1) and (2) above as an example. (The C24 I/O signals are X/Y80 to X/Y9F, transmission from CH1) Refer to the User's Manual (Basic) for more information about the ONDEMAND instruction.
Page 316: Initializing The Transmission Sequence: For Serial Communication Modules
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.12 Initializing the Transmission Sequence: for Serial Communication Modules This function initializes the data communication transmission sequence by the QnA compatible 4C frame format 5 of the MC protocol, and instructs the C24 to wait for commands from an external device.
Page 317: Transmission Sequence Initialization (Command: 1615)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.12.2 Transmission sequence initialization (command: 1615) The following example explains the control procedure for initializing the transmission sequence. [Control procedure] The QnA compatible 4C frame format 5 is used to describe the control procedure in this example.
Page 318: Mode Switching: For Serial Communication Module
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.13 Mode Switching: for Serial Communication Module This function forcefully switches the current communication protocol (operation mode) and transmission specifications of the designated interface from an external device after the C24 is started.
Page 319: Commands And Contents Of The Character Area
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.13.1 Commands and contents of the character area The following explains the commands and the contents of the character area (data section in communication in binary code) when the C24 mode is switched from an external device.
Page 320 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Switching instruction This data designates which mode switching will be performed. Data communication in ASCII code The value shown below is converted to a 2-digit (hexadecimal) ASCII code and sequentially transmitted beginning from the most significant digit.
Page 321 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (d) Transmission setting and communication speed setting This data is for designating the transmission specifications after the mode is switched. 1) Data communication in ASCII code The value shown below is converted to a 2-digit (hexadecimal) ASCII code and sequentially transmitted from the most significant digit.
Page 322 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME [Communication speed setting] 2 3 4 Bit position Bit position Communication speed Communication speed Remarks b15 to b8 b15 to b8 14400bps 50bps Slow down the 19200bps 300bps communication speed when 28800bps 600bps...
Page 323: Mode Switching (Command: 1612)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.13.2 Mode switching (command: 1612) The examples shown in this section explain the control procedure for switching the C24 mode from an external device. The order and contents of data items of the area marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 324 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Switching the mode of the interface on the CH1 side while communicating in binary code Fixed to 0000 (Refer to section 3.13.1.) (Data name) External device side (Example) 1612 (Data name)
Page 325: Turning Off Displayed Leds And Initializing Communication Error Information And Error Code: For Serial Communication Module
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.14 Turning Off Displayed LEDs and Initializing Communication Error Information and Error Code: for Serial Communication Module This function is used by the external device to turn off the ERR LEDs of the C24 LED display, or to initialize the communication error information and error code stored in the buffer memory.
Page 326 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Contents of the character area The following explains the contents of the character area when initializing communication error information and error codes of the C24 from an external device.
Page 327 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Communication error information-1 and communication error information-2 These values indicate the communication error information to be initialized. • Communication error information-1 (mainly for designation for the CH1 side) •...
Page 328: Turning Off Displayed Leds And Initializing Communication Error Information And Error Code (Command: 1617)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.14.2 Turning off displayed LEDs and initializing communication error information and error code (command: 1617) The examples shown in this section explain the control procedure for turning off the displayed LEDs of the C24 and for initializing the communication error information and error code from an external device.
Page 329 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.15 Turning Off the COM.ERR.LED: for the E71 This function is for turning off the COM.ERR.LED on the front of the E71 from an external device. POINT This function can be used only for the E71 in the same Ethernet as the external device that requests to turn off the COM.ERR.LED.
Page 330: Turning Off The Com.err.led (Command: 1617)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.15.2 Turning off the COM.ERR.LED (command: 1617) The example shown in this section explain the control procedure for turning off the displayed LED on the front of the E71 from an external device. The order and contents of data items of the area marked by "...
Page 331: Loopback Test
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.16 Loopback Test A loopback test checks whether or not the communication function between an external device and the C24/E71 operates normally. The examples show the control procedure using this function. POINT A loopback test allows to check whether or not the connection between the external device and the C24/E71 is correct and that the data communication...
Page 332: Loopback Test (Command: 0619)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.16.2 Loopback test (command: 0619) The examples shown in this section explain the control procedure for an external device performing a loopback test with the C24/E71. The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.
Page 333: Registering Or Canceling Programmable Controller Cpu Monitoring For Serial Communication Modules
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.17 Registering or Canceling Programmable Controller CPU Monitoring: for Serial Communication Modules These functions are for registering (including the start instruction) or canceling programmable controller CPU monitoring from an external device or the programmable controller CPU in order to utilize the programmable controller CPU monitoring function of the C24.
Page 334 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Interfaces to which the programmable controller CPU monitoring function transmits information The information is transmitted to the interfaces for which the MC protocol or non- procedure protocol is set. The explanation of the programmable controller CPU monitoring function using the non-procedure protocol is provided in the User's Manual (Application).
Page 335 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT (1) The programmable controller CPU monitoring registration can be performed from an external device, the programmable controller CPU or GX Works2/GX Configurator-SC. (2) The external device or programmable controller CPU cannot register programmable controller CPU monitoring to the same C24 twice in order to register a monitoring device, etc.
Page 336 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.17.1 Commands and contents of the character area The following explains the commands and the contents of the character area (data section in communication in binary code) in the control procedure when the programmable controller CPU monitoring function is used from an external device.
Page 337 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (c) Programmable controller CPU monitoring function (cycle monitoring function) This value designates the transmission timing (constant cycle transmission or condition agreement transmission) when transmitting the resulting monitoring information of the programmable controller CPU (device information or CPU status information) to an external device.
Page 338 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3) Designate the device registration to the C24 within the following ranges  (total number of word blocks + total number of bit blocks) 10 blocks 960 points  (total number of device points of all word blocks + total number of device points of all bit blocks) The range for devices that can be registered is designated by item (g) below for each block.
Page 339 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (h) Transmission method in condition agreement transmission This flag designates which method should be used to transmit the results of monitoring the programmable controller CPU when condition agreement transmission is designated in programmable controller CPU monitoring function (c).
Page 340 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Monitoring condition value This value designates the target status/numerical value of the monitoring condition (i) when condition agreement transmission is designated in programmable controller CPU monitoring function (c). •...
Page 341 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME REMARKS In the command message, designate the following values in the data item for designating access destination stations for a local station other than those mentioned above. Designated data Data item Data communication in ASCII code Data communication in binary code...
Page 342: Programmable Controller Cpu Monitoring Registration (Command: 0630)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.17.2 Programmable controller CPU monitoring registration (command: 0630) The examples shown in this section explain the control procedure for registering programmable controller CPU monitoring from an external device. The order and contents of data items of the area marked by "...
Page 343 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (1) Communication in ASCII code (Refer to section 3.17.1.) (Refer to section 3.3.1.) (Refer to section 3.17.1.) (Data name) External device H – – H – – H – –...
Page 344 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) Communication in binary code (Refer to section 3.17.1.) (Refer to section 3.3.1.) (Refer to section 3.17.1.) (Data name) External device side – (Example) D0=99 D0 to D3 Word device registration (first block) –...
Page 345: Canceling Programmable Controller Cpu Monitoring (Command: 0631)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.17.3 Canceling programmable controller CPU monitoring (command: 0631) The examples shown in this section explain the control procedure for canceling the programmable controller CPU monitoring from an external device. The order and contents of data items of the area marked by "...
Page 346: Data Transmitted By The Programmable Controller Cpu Monitoring Function
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.17.4 Data transmitted by the programmable controller CPU monitoring function The examples shown in this section explain the monitor information transmitted from the C24 by registering programmable controller CPU monitoring from an external device.
Page 347 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (1) When CPU status data and device data are transmitted in constant cycle transmission The example shown in this section explain the transmission when the device data shown in Section 3.17.2 is registered using the A compatible 1C frame format 1. If "constant cycle transmission"...
Page 348 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME • When the "Word/byte units designation" in GX Works2 or GX Configurator-SC is set to "1" (byte units) External device side (Refer to section 5.1.) (Refer to section 3.17.1.) (Data name) : Fixed value Programmable...
Page 349 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Communication in binary code • When the "Word/byte units designation" in GX Works2 or GX Configurator-SC is set to "0" (word units) External device side (Refer to section 3.1.5.) (Refer to section 3.17.1.) (Data name) : Fixed value...
Page 350 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME • When the "Word/byte units designation" in GX Works2 or GX Configurator-SC is set to "1" (byte units) External device (Refer to section 3.1.5.) (Refer to section 3.17.1.) side (Data name) : Fixed value...
Page 351 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (2) When CPU status data or device data are transmitted in condition agreement transmission The examples shown in this section explain the transmission when the programmable controller CPU monitoring is registered as shown in Section 3.17.2 using the A compatible 1C frame format 1.
Page 352 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 2) Communication in binary code • When the "Word/byte units designation" in GX Works2 or GX Configurator-SC is set to "0" (word units) External device side (Data name) : Fixed value Programmable controller CPU side...
Page 353 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (b) Transmitting word device data The examples shown in this section explain the transmission of word device data D0 to D3 (four points) by D0 = 99, when the programmable controller CPU monitoring shown in Section 3.17.2 is registered.
Page 354 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 2) Communication in binary code • When the "Word/byte units designation" in GX Works2 or GX Configurator-SC is set to "0" (word units) External device side (Data name) : Fixed value Programmable controller CPU side...
Page 355 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME (c) Transmitting bit device data The examples shown in this section explain the transmission of bit device data M0 to M31 (two points) by M0 = ON, when the programmable controller CPU monitoring shown in Section 3.17.2 is registered.
Page 356 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 2) Communication in binary code • When the "Word/byte units designation" in GX Works2 or GX Configurator-SC is set to "0" (word units) External device side (Data name) : Fixed value Programmable controller CPU side...
Page 357: Remote Password Unlock/Lock
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.18 Remote Password Unlock/Lock The remote password function prevents unauthorized access from remote users to the CPU module. If a remote password is specified, the validity of the password is checked when a remote user attempts to access the CPU module.
Page 358 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME REMARKS For the target of the remote password check function when a CPU module with built- in Ethernet port is used, refer to the following. • QnUCPU User’s Manual (Communication via Built-in Ethernet Port) •...
Page 359 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT (1) When the connection used for data communication is set as an object of the remote password check, communication is enabled from after the completion of the unlock process until the lock process is executed. All commands received while the remote password is in locked status will generate an error response.
Page 360 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME Accessing via the C24 (the interface using the modem function is the object) POINT (1) When the C24 communicating data using the modem function is set as an object of the remote password check, communication is enabled from after the completion of the unlock process until the line is disconnected.
Page 361: Contents Of The Command And Character Section
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.18.1 Contents of the command and character section This section explains the commands and character section (the data section when communicating with binary code) of the control procedure when performing the remote password unlock process/lock process from an external device.
Page 362: Remote Password Unlock/Lock (Command: 1630, 1631)
3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME 3.18.2 Remote password unlock/lock (command: 1630, 1631) This section explains the control procedure for unlocking or locking the remote password protection using examples. The arrangement and contents of the data items in the section marked with in the control procedure diagram will vary depending on the module used and the frame and format at the time of communication.
Page 363 3 WHEN COMMUNICATING USING THE QnA COMPATIBLE 3E/3C/4C FRAMES OR 4E FRAME POINT Specify local station for the message format when performing the remote password unlock process/lock process. The unlock process/lock process cannot be done for the Q/LCPU of other station. (Example) Example of a message for the remote password unlock process command using the QnA compatible 4C frame (format 1) –...
Page 364: Control Procedures And Message Formats
4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES 4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES This chapter explains the message data formats, how to designate data and the restrictions when data communication via the C24 is performed with QnA compatible 2C frames using the MC protocol.
Page 365 4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES (b) When the external device writes data to programmable controller (Command message) External device Area C side Programmable controller CPU side Area B (Response message) Area C indicates transmission from an external device to the C24. Area B indicates transmission from the C24 to an external device.
Page 366 4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES (3) Control procedure (a) Communication in format 1 1) When the external device reads data from the Q/LCPU (Example) Using command 1, the external device reads five points of data from X40 to X44 in the Q/LCPU. External device side Programmable controller CPU side (Command message) Character area A...
Page 367 4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES (b) Communication in format 2 1) When the external device reads data from the Q/LCPU (Example) Using command 1, the external device reads five points of data from X40 to X44 in the Q/LCPU. External device side Programmable controller CPU side (Command message) Character area A...
Page 368 4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES (c) Communication in format 3 1) When the external device reads data from the Q/LCPU (Example) Using command 1, the external device reads five points of data from X40 to X44 in the Q/LCPU. External device side Programmable controller CPU side (Command message) Character area A...
Page 369 4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES (d) Communication in format 4 1) When the external device reads data from the Q/LCPU (Example) Using command 1, the external device reads five points of data from X40 to X44 in the Q/LCPU. External device side Programmable controller CPU side (Command message) Character area A...
Page 370: Contents Of The Data Designation Items
4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES 4.2 Contents of the Data Designation Items Each frame format contains several data items for data transmission, as defined by the control procedure. Some of the data items of the QnA compatible 2C, 3C and 4C frames are common, but not all.
Page 371: List Of Commands And Functions For Qna Compatible 2C Frames
4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES 4.3 List of Commands and Functions for QnA Compatible 2C Frames The following table outlines commands and functions that are used when communicating in QnA compatible 2C frames. All the commands are for reading and writing data from/to the device memory of the programmable controller CPU on which the C24 is loaded using the MC protocol.
Page 372: Precautions On The Data Communication
4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES 4.4 Precautions on the Data Communication Certain precautions should be observed while communicating data using QnA compatible 2C frames. Some precautions are common to communication in this format and in the QnA compatible 3C/4C frame formats.
Page 373: Example Of Data Communication Using Qna Compatible 2C Frames
4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES 4.5 Example of Data Communication Using QnA Compatible 2C Frames The following shows examples of the control procedure for data communication using format 1 QnA compatible 2C frames. Refer to Section 4.1(3) for examples of the control procedures for commands 1 and 3. (1) Batch read in word units (command: 2) (a) Reading two points (32 bits) from internal relays M100 to M131 Number of points to be read...
Page 374 4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES (2) Batch write in word units (command: 4) (a) Writing two points (32 bits) to internal relays M100 to M131 Number of points to be written Character area C (Data name) Data for the number of designed device points.
Page 375 4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES (3) Random read in word units (command: 5) Reading the following device memory • Word access : D0, T0, M100 to M115, X10 to X1F • Double word access : D1500 to D1501, Y160 to Y17F, M1111 to M1142 Number of points to be read Character area A (Data name)
Page 376 4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES (4) Test in bit units (command: 6) Turning off the internal relay M50 and turning on the output relay Y2F When set (ON): 01 Number of points to be written When reset (OFF): 00 Character area C (Data name) External device...
Page 377 4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES The following shows the correspondence between the data to be tested by each word unit and the bit device: M100 to M115 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0 X10 to X1F 1 0 0 0 0 0 1 1 0 0 0 0 0 1 0...
Page 378 4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES (7) Monitor in word units (command: 9) Monitoring the following device memory for which monitoring data has been registered (Device memory with monitor data registered) • Word access : D0, T0, M100 to M115, X10 to X1F •...
Page 379 4 WHEN COMMUNICATING USING THE QnA COMPATIBLE 2C FRAMES MEMO 4 - 16 4 - 16...
Page 380 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES This chapter explains the message data formats, how to designate data and the restrictions when data communication via the C24 is performed with QnA compatible 1C frames using the MC protocol.
Page 381: How To Read The Control Procedure And Command Reference Sections
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.1.1 How to read the control procedure and command reference sections This section explains how to read the control procedure and message diagrams in the Section 5.2 to 5.4. (1) How to read the MC protocol control procedure This section explains how to read the transmission data that is shown in the description of each control procedure format in Sections 5.2 and succeeding sections.
Page 382 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (b) When the external device writes data to programmable controller (Command message) External device Area C side Area B Programmable controller CPU side (Response message) Area C indicates transmission from an external device to the C24. Area B indicates transmission from the C24 to an external device.
Page 383 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.1.2 Control procedures and message formats This section illustrates the control procedure and message format of each command when data communication is performed in each format of the A compatible 1C frames. section shown in the message explanation diagram of this section are items common to all command and corresponds to the portion of the message explanation...
Page 384 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (1) Communication in format 1 (a) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (At normal (At abnormal (Command message) completion) completion)
Page 385 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (2) Communication in format 2 (a) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (At normal (At abnormal (Command message) completion) completion)
Page 386 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (3) Communication in format 3 (a) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (At normal (At abnormal (Command message) completion) completion)
Page 387 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (4) Communication in format 4 (a) When the external device reads data from the programmable controller CPU on the local station External device side Programmable controller CPU side (At normal (At abnormal (Command message) completion) completion)
Page 388: Contents Of Data Designation Items Of A Compatible 1C Frames
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.1.3 Contents of data designation items of A compatible 1C frames This section explains the data items when communicating data via the C24 with A compatible 1C frames whose contents and method of designation are different from those of QnA compatible 3C/4C frames.
Page 389 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (2) Block number Block numbers are arbitrary numbers given to the corresponding message by an external device and used as data reference numbers. The contents and method of designation are the same as for communication using QnA compatible 3C/4C frames.
Page 390 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES [Example of PC number designation] (Meaning of the symbols for each station shown in the diagrams) • Network system (CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H, MELSECNET/10) (a) In case of a CC-Link IE Controller Network, MELSECNET/H (PLC to PLC network), MELSECNET/10 (PLC to PLC network) •...
Page 391 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (b) In case of a CC-Link IE Field Network • Hierarchical system PC number to be designated Station Programmable controller CPU accessed by an connected external device to external 1Ns3/ 0 1Ns2 1Ns4 device 1Ns3/...
Page 392 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (5) Commands A command is used to designate the type of access such as reading and writing to be done from the external device to the applicable programmable controller. The commands described in Sections 5.2 to 5.5 are designated by converting them to 2-digit (hexadecimal) ASCII codes.
Page 393: Understanding Transmission Data In The Character Areas
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (10) Sum check code The sum check code is obtained by converting the lower byte (8 bits) of the binary sum of the target data of the sum check into a 2-digit ASCII code (hexadecimal).
Page 394: List Of Commands And Functions For A Compatible 1C Frames
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.1.5 List of Commands and functions for A compatible 1C frames The following table lists the commands and functions when an external device accesses the programmable controller CPU using A compatible 1C frames. Command –...
Page 395 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES Access station ( Programmable controller CPU status ( – During RUN Reference QCPU During Safety MELSECNET/H ACPU LCPU remote station STOP Function Write enabled Write disabled Bit units Section 5.2.2 Batch read Word Section 5.2.5 units...
Page 396 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES The online change (write during RUN) status can be set to the programmable controller CPU in the following screen of the programming tool. • In case of the C24: "Switch setting for I/O and intelligent functional module" screen For programmable controller CPUs other than the AnA/AnU/QnA/L/QCPU, device X (input) has two processing points per point.
Page 397 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.2 Device Memory Read/Write This section explains control procedures for reading/writing data from/to the device memory and provides examples for each procedure. To read/write data from/to the extended file register, use the commands dedicated for the extended file register.
Page 398 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES AnA/AnUCPU common commands Programmable controller CPU Command status ( Number of points Item Processing processed per Reference During RUN During communication Symbol ASCII code Write Write STOP enabled disabled Reads bit devices (X, Y, M, Bit units , 52 256 points...
Page 399 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (2) Accessible device range (a) Device range when using the ACPU common commands The following table outlines the devices and device number range that can be designated when accessing the device memory. Each device consists of five characters, which are designated in the order shown in the following table.
Page 400 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES The range of accessible devices when accessing the MELSECNET/H remote I/O station is indicated below. For link relay (B), data register (D) and link register (W), the devices after the numbers shown in the table below cannot be accessed.
Page 401 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES Precautions when reading/writing data from/to the Q/L/QnACPU Devices that have the same names as those found in AnCPU, AnNCPU, AnACPU and AnUCPU can be accessed within the range shown in the table.
Page 402: Batch Read In Bit Units (Command: Br, Jr)
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.2.2 Batch read in bit units (command: BR, JR) The example shown in this section explain the control procedure for batch reading bit device memory using the BR and JR commands. The order and contents of data items for the parts marked with "...
Page 403: Batch Write In Bit Units (Command: Bw, Jw)
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.2.3 Batch write in bit units (command: BW, JW) The example shown in this section explain the control procedure for batch writing bit device memory using the BW and JW commands. The order and contents of data items for the parts marked with "...
Page 404: Test In Bit Units (Random Write) (Command: Bt, Jt)
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.2.4 Test in bit units (random write) (command: BT, JT) The example shown in this section explain the control procedure for writing data by randomly designating bit device memory using the BT and JT commands. The order and contents of data items for the parts marked with "...
Page 405: Batch Read In Word Units (Command: Wr, Qr)
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.2.5 Batch read in word units (command: WR, QR) The example shown in this section explain the control procedure for batch reading bit device memory (16 bit units) and word device memory (word units) using the WR and QR commands.
Page 406 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES REMARKS When specifying bit devices, set the head device numbers in multiples of 16 (in decimal, 0, 16 …). (2) Reading the word device memory When using WR (ACPU common command) : 5 characters (in the following case, TN123 is designated) When using QR (AnA/AnUCPU common command) : 7 characters Number of points to be read...
Page 407: Batch Write In Word Units (Command: Ww, Qw)
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.2.6 Batch write in word units (command: WW, QW) The example shown in this section explain the control procedure for batch-writing the bit device memory (16 bit units) and the word device memory (word units) using the WW and QW commands.
Page 408 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES REMARKS When specifying bit devices, set the head device numbers in multiples of 16 (in decimal, 0, 16 …). (2) Writing to the word device memory When using WW (ACPU common command) : 5 characters (in the following case, D0000 is designated) When using QW (AnA/AnUCPU common command) : 7 characters Four characters are used for one device point.
Page 409: Test In Word Units (Random Write) (Command: Wt, Qt)
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.2.7 Test in word units (random write) (command: WT, QT) The example shown in this section explain the control procedure for writing by randomly designating the word device memory and bit device memory (16 bit units) using the WT and QT commands.
Page 410 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.2.8 Monitoring device memory The monitor data registration function registers the name and number of the devices to be monitored from an external device to the C24. The monitor function allows to read the data contents of the registered devices from the programmable controller CPU and process it in the external device.
Page 411 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (2) Monitor data registration for device memory (commands: BM, JM, WM, QM) The example shown in this section explain the control procedure for registering the name and number of devices to be monitored in the C24 using the BM/JM/WM/QM command.
Page 412 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (b) Registering monitor data to the bit device memory and the word device memory in word units. [Control procedure] (Conditions for monitor data registration) Message wait is 0 ms. 2) Register monitor data for the current values of D15, W11E, and T123 as well as for the 4 points (4 words) of Y060 to Y06F.
Page 413 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (3) Monitoring the device memory to which monitor data is registered (command: MB, MJ, MN, MQ) The example shown in this section explain the control procedure for monitoring devices registered in the C24 by monitor data registration of item (2) using the MB/MJ/MN/MQ command.
Page 414 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (b) Monitoring the bit device memory and the word device memory to which the monitor data is registered in word units. [Control procedure] Device memory registered using the WM command is monitored with the MN command.
Page 415: Extension File Register Read And Write
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.3 Extension File Register Read and Write The extension file register uses free areas in the user memory area of the programmable controller CPU as a file register. It serves as a memory area for storing necessary data and results of operations in various data processing performed using the software packages for extension file registers "SWOGHP-UTLPC-FN1"...
Page 416: Ana/Anucpu Common Commands And Device Numbers
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.3.2 AnA/AnUCPU common commands and device numbers (1) This section explains AnA/AnUCPU common commands used for directly reading from and writing to the extension file register. This command allow the access to extension file register blocks numbered from 1 to 256 by designating addresses from device number 0 of block numbered from 1 as the device number, regardless of each block number.
Page 417 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES The device numbers that can be designated vary depending on the memory cassette type and the parameter settings of the programmable controller CPU. (For more detailed explanations, refer to the operating manual of UTLP-FN1, or the User's Manual of the programmable controller CPU to be accessed.) A device number is not assigned to a block number that does not exist in the memory cassette.
Page 418 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES REMARKS The following table shows the range of device numbers designated when the AnA/AnUCPU common commands, NR and NW, are used for the first 28 blocks. Device number Position of target block Device number Position of target block 114688...
Page 419: Precautions When Reading And Writing In The Extension File Register
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.3.3 Precautions when reading and writing in the extension file register The following precautions should be observed when reading and writing in the extension file register using the commands described in Sections 5.3.4 through 5.3.9. (1) Only programmable controller CPUs that can handle an extension file register can be accessed.
Page 420: Batch Reading Of The Extension File Register (Command: Er)
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.3.4 Batch reading of the extension file register (command: ER) The example shown in this section explain the control procedure for batch reading from the extension file register using the ER command. The order and contents of data items for the parts marked with "...
Page 421: Batch Writing Of The Extension File Register (Command: Ew)
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.3.5 Batch writing of the extension file register (command: EW) The example shown in this section explain the control procedure for batch writing from the extension file register using the EW command. The order and contents of data items for the parts marked with "...
Page 422: Direct Reading Of The Extension File Register (Command: Nr)
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.3.6 Direct reading of the extension file register (command: NR) The example shown in this section explain the control procedure for reading directly from the extension file register using the NR command. The order and contents of data items for the parts marked with "...
Page 423: Direct Writing Of The Extension File Register (Command: Nw)
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.3.7 Direct writing of the extension file register (command: NW) The example shown in this section explain the control procedure for writing directly from the extension file register using the NW command. The order and contents of data items for the parts marked with "...
Page 424: Test Of Extension File Register (Random Write) (Command: Et)
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.3.8 Test of extension file register (random write) (command: ET) The example shown in this section explain the control procedure for writing data by randomly designating device numbers in the extension file register with the ET command.
Page 425: Monitoring Extension File Register
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.3.9 Monitoring extension file register The monitor data registration function registers the name and number of the devices to be monitored from an external device to the C24. The monitor function allows to read the data contents of the registered devices from the programmable controller CPU and processing it in the external device.
Page 426 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (2) Monitor data registration of extension file register (command: EM) The example shown in this section explain the control procedure for registering device numbers of the extension file register to be monitored to the C24 with the EM command.
Page 427 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES (3) Monitor extension file register (command: ME) The example shown in this section explain the control procedure for monitoring the extension file register that is registered in C24 in item (2), "Monitor data registration (EM)"...
Page 428: Reading And Writing In The Buffer Memory Of An Intelligent Function Module
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.4 Reading and Writing in the Buffer Memory of an Intelligent Function Module The following examples explain the control procedure when reading data from and writing data to the buffer memory of an intelligent module (special function module) in an A series programmable controller CPU station or a MELSECNET/H, MELSECNET/10 remote I/O station.
Page 429: Understanding The Intelligent Function Module Number In The Control Procedure
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.4.2 Understanding the intelligent function module number in the control procedure (1) Module number of an intelligent function module that occupies 1 slot The intelligent function module number designated in the control procedure is the first 2 digits of the last (3-digit) number of the input/output signal (I/O address) of the slot on which the module is loaded.
Page 430 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES In case of a module that assign the last half slots as empty slots (A61LS, etc.) ……Intelligent function module number "01 " 32 points 16 points In case of a module in which both an intelligent function module and an input/output module are assigned (In case of the A81CPU) ……Intelligent function module number "02...
Page 431: Reading From The Buffer Memory Of An Intelligent Function Module (Command: Tr)
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.4.3 Reading from the buffer memory of an intelligent function module (command: TR) The example shown in this section explain the control procedure for reading from the buffer memory of an intelligent module with the TR command. The order and contents of data items for the parts marked with "...
Page 432: Writing To The Buffer Memory Of An Intelligent Function Module (Command: Tw)
5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.4.4 Writing to the buffer memory of an intelligent function module (command: TW) The example shown in this section explain the control procedure for writing to the buffer memory of an intelligent module with the TW command. The order and contents of data items for the parts marked with "...
Page 433 5 WHEN COMMUNICATING USING THE A COMPATIBLE 1C FRAMES 5.5 Loopback Test A loopback test checks whether or not the communication function between an external device and the C24 module operates normally. The examples show the control procedure using this function. The order and contents of data items for the parts marked with "...
Page 434 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES This chapter explains the message format, how to designate data items in a message and restrictions when communicating data via the E71 using the MC protocol and A compatible 1E frames.
Page 435: Message Formats And Control Procedures
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.1 Message Formats and Control Procedures This section explains the message format and control procedure for each command when data communication is performed using A compatible 1E frames. Data communication using A compatible 1E frames is equivalent to the functions for reading/writing data from/to the programmable controller CPU supported by A series Ethernet interface modules, and only the commands mentioned in Section 6.2 can be used.
Page 436 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) When an external device writes data to the programmable controller CPU (Command message) External Area C device side Programmable controller CPU side (Response message) Area C indicates transmission from the external device to the programmable controller CPU.
Page 437: Message Format And Control Procedure
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.1.2 Message format and control procedure This section explains the message format and control procedure when data communication is performed using A compatible 1E frames for the E71. Message format This section explains the message format for transmission between the E71 and an external device.
Page 438 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Control procedure The following diagrams illustrate the control procedure for communicating with A compatible 1E frame and the order of data items in the application data field. The header section shown in the message explanation diagram of this section corresponds to the portion of the message explanation diagrams indicated in Section 6.3.2 of this chapter and after.
Page 439 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (b) Communication in binary code When the external device reads data from the programmable controller CPU on the local station When the external device writes data to the programmable controller CPU on the local station 6 - 6 6 - 6...
Page 440: Contents Of Data Designation Items Of A Compatible 1E Frames
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.1.3 Contents of data designation items of A compatible 1E frames This section explains the data items of commands and responses when communicating using the MC protocol and A compatible 1E frames. In the response that is returned by the E71 to an external device, the data is automatically specified by the E71;...
Page 441 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES POINT To access a programmable controller CPU on another station, set network parameters for the following network systems or set "Valid Module During Other Station Access". • CC-Link IE Controller Network •...
Page 442 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (b) In case of a CC-Link IE Field Network • Hierarchical system PC number to be designated Station Programmable controller CPU accessed by an connected external device to external 1Ns3/ 0 1Ns2 1Ns4 device 1Ns3/...
Page 443 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (5) Text (command) This data contains the E71 commands that indicate functions for when an external device reads/writes data from/to the target programmable controller station. The contents and order of data in the text (command) field differ depending on the function used.
Page 444 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (7) Complete code The result of processing when an external device reads/writes data from/to the target programmable controller station is indicated by the following values. : Normal completion Other than 00 : Abnormal completion (a) When communicating in binary code, the complete code is expressed in binary values.
Page 445 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES REMARKS The following example shows the designation of the subheader to the ACPU monitoring timer when communicating using the MC protocol under the following conditions. (Designated value) • Target station : Programmable controller CPU station : FF on which the E71 is loaded (local station)
Page 446 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Format when communicating in ASCII code (a) The order when sending a command (external device E71) Application data Subheader PC number ACPU monitoring timer Header "0" "0" "F" "F" "0" "0"...
Page 447 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.1.4 Understanding transmission data in the character areas The transmission order of bit device data and word device data indicated in the transmission data (each character area) when communicating using the MC protocol and A compatible 1E frames is the same as when communicating using QnA compatible 3E/3C/4C frames or 4E frame.
Page 448: List Of Commands And Functions For A Compatible 1E Frames
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.2 List of Commands and Functions for A Compatible 1E Frames The following table lists the commands and functions when an external device accesses the programmable controller CPU using A compatible 1E frames. –...
Page 449 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES Programmable controller Access station ( – CPU status ( During RUN Reference MELSECNET/10 MELSECNET/H Q/LCPU Safety During ACPU remote remote Write Write Function STOP station station enabled disabled Bit units Section 6.3.2 Batch read Word units Section 6.3.5...
Page 450 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES The online change (write during RUN) status can be set to the programmable controller CPU in the following screen of the programming tool. • In case of the E71: "Ethernet operation setting" screen For programmable controller CPUs other than the AnA/AnU/QnACPU/LCPU/QCPU, device X (input) has two processing points per point.
Page 451 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.3 Device Memory Read/Write This section explains control procedures for reading/writing data from/to the device memory and provides examples for each procedure. To read/write data from/to the extended file register, use the commands dedicated for the extended file register.
Page 452 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Designation method and accessible range of devices. In device read/write, each device is set by a device code and number as shown in the diagram below. B0 B31 Device code Device number (Set in hexadecimal) [Example] In case of D100 D100 = 4420 00000064...
Page 453 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES Device list (CPU module with restriction) : Accessible : Not accessible – : No device. High Performance model QCPU, QJ72LP25-25, Process CPU, Device Basic model QCPU, QJ72LP25G, Device ( Device range Device number Redundant CPU, code...
Page 454 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES Device list (CPU module with restriction) : Accessible : Not accessible – : No device. A2US-S1, A2AS-S1, A2US, Q2A, Q2A-S1, Q3A, Device A2AS-S30, A3U, Device ( Device range Device number A2AS, Q2AS, Q2AS-S1, Q4A,...
Page 455 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES POINT Use the device number range of the access-target programmable controller CPU. (For the Q/L/QnACPU, the range will be the same as that of the AnACPU.) Bit devices and word devices are classified according to the following. Bit devices : X, Y, M, L, B, F, T (contact), T (coil), C (contact), C (coil) Word devices...
Page 456 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES Precautions when reading/writing data from/to the Q/L/QnACPU Only the devices with the same names as those found in the AnCPU, AnNCPU, AnACPU and AnUCPU can be read/written within the device range of AnACPU. The following devices cannot be accessed from the external devices: •...
Page 457 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES MEMO 6 - 24 6 - 24...
Page 458: Batch Read In Bit Units (Command: 00)
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.3.2 Batch read in bit units (command: 00) The examples shown in this section explain the command/response format when batch-reading the bit device memory. For more details on the order and contents of data items of the areas marked by " " shown in the control procedure diagram, refer to Section 6.1.
Page 459 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Communication in ASCII code (Data name) Head device External device side H L H L H L (Example) Data for the number (Data name) of designed device points Characters for the Programmable controller CPU side number of device points...
Page 460: Batch Write In Bit Units (Command: 02)
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.3.3 Batch write in bit units (command: 02) The examples shown in this section explain the command/response format when batch writing to the bit device memory. For more details on the order and contents of data items of the areas marked by " " shown in the control procedure diagram, refer to Section 6.1.
Page 461 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Communication in ASCII code (Data name) Data for the number ACPU of designed device points Head device monitoring Characters for the timer External device number of device points side H L H (Example) (Data name) Programmable controller CPU side...
Page 462: Test In Bit Units (Random Write) (Command: 04)
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.3.4 Test in bit units (random write) (command: 04) The examples shown in this section explain the command/response format when writing data by designating bit device memories at random. For more details on the order and contents of data items of the areas marked by " " shown in the control procedure diagram, refer to Section 6.1.
Page 463 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Communication in ASCII code (Data name) Designated device Designated device External device side (Example) ON Y94 OFF M60 Designated device (Data name) ON B26 Programmable controller CPU side (Example) 6 - 30 6 - 30...
Page 464: Batch Read In Word Units (Command: 01)
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.3.5 Batch read in word units (command: 01) The examples shown in this section explain the command/response format when batch reading the word device memory and the bit device memory (16 point units). For more details on the order and contents of data items of the areas marked by "...
Page 465 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Communication in ASCII code (Data name) Head device External device side (Example) Data for the number (Data name) of designed device 32/16 = 2 points points Characters for the Programmable controller CPU side number of device points (Example)
Page 466: Batch Write In Word Units (Command: 03)
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.3.6 Batch write in word units (command: 03) The examples shown in this section explain the command/response format when batch writing to a word device memory and bit device memory (16 point units). For more details on the order and contents of data items of the areas marked by "...
Page 467 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Communication in ASCII code (Data name) Data for the number of Head device designed device points (Characters for the number of device points) External device side H L H (Example) D100 (Data name) Programmable controller CPU side...
Page 468: Test In Word Units (Random Write) (Command: 05)
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.3.7 Test in word units (random write) (command: 05) The examples shown in this section explain the command/response format when writing data by designating word device memories and bit device memories (16 point units) at random.
Page 469 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Communication in ASCII code (Data name) Data for the number of designed Data for the number of designed ACPU ON/OFF ON/OFF monitoring device points device points designation designation timer (Characters for the number of device points) (Characters for the number of device points) External device side...
Page 470 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.3.8 Monitoring device memory The on/off status and contents of devices in the programmable controller CPU can be monitored from an external device by registering the devices and device numbers to be monitored by the external device to the E71 in advance and issuing a monitor command from the external device.
Page 471 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Monitor data registration (command: 06, 07) The examples shown in this section explain the command/response format when registering devices to be monitored. For more details on the order and contents of data items of the areas marked by "...
Page 472 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (3) Monitor in bit units (command: 08) The examples shown in this section explain the command/response format when monitoring bit devices for which monitor data is registered. For more details on the order and contents of data items of the areas marked by "...
Page 473 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (4) Monitor in word units (command: 09) The examples shown in this section explain the command/response format when monitoring word devices and bit devices (16 point units) for which monitor data is registered.
Page 474 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (b) Communication in ASCII code (Data name) External device side (Example) (Data name) Data for the number of designed device points (Characters for the number of device points) Programmable controller CPU side (Example) Indicates the content of W1E.
Page 475 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.4 Extension File Register Read and Write The extension file register uses free areas in the user memory area of the programmable controller CPU as a file register. It serves as a memory area for storing necessary data and results of operations in various data processing performed using the software packages for extension file register "SWOGHP-UTLPC-FN1"...
Page 476 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.4.2 AnA/AnUCPU common commands and device numbers (1) This section explains the AnUCPU dedicated commands used for directly reading from and writing to the extension file register. This command allow the access to extension file register blocks numbered from 0 to 256 by designating addresses from device number 0 of block number 1 as the device number, regardless of each block number.
Page 477 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES The device numbers that can be designated vary depending on the memory cassette type and the parameter setting of the programmable controller CPU. (For a more detailed explanation, refer to the operating manual for UTLP-FN1, or the User's Manual for the programmable controller CPU to be accessed.) A device number is not assigned to a block number that does not exist in the memory cassette.
Page 478 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES REMARKS The following table shows the range of device numbers designated when the AnA/AnUCPU common commands (3B , 3C ) are used for the first 28 blocks. Device number Position of target block Device number Position of target block 114688...
Page 479: Precautions When Reading And Writing From/To The Extension File Register
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.4.3 Precautions when reading and writing from/to the extension file register The following precautions should be observed when reading and writing from/to the extension file register using the commands described in Sections 6.4.4 through 6.4.9. (1) Only programmable controller CPUs that can handle an extension file register can be accessed.
Page 480: Batch Reading Of The Extension File Register (Command: 17)
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.4.4 Batch reading of the extension file register (command: 17) The examples shown in this section explain the command/response format when batch-reading extension file registers. For more details on the order and contents of data items of the areas marked by " " shown in the control procedure diagram, refer to Section 6.1.
Page 481 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Communication in ASCII code (Data name) Device No. External device side H L H (Example) Data for the number of designated device points in (Data name) the designated block No. Designates the block No.2 Designates R70 Characters for the...
Page 482: Batch Writing Of The Extension File Register (Command: 18)
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.4.5 Batch writing of the extension file register (command: 18) The examples shown in this section explain the command/response format when batch-writing extension file registers. For more details on the order and contents of data items of the areas marked by " " shown in the control procedure diagram, refer to Section 6.1.
Page 483 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Communication in ASCII code (Data name) Head device No. External device side (Example) Designates the Designates R100 block No.3 Data for the number of designated device points in the designated block No. (Characters for the number of device points) (Data name) Programmable controller...
Page 484: Direct Reading Of The Extension File Register (Command: 3B)
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.4.6 Direct reading of the extension file register (command: 3B) The examples shown in this section explain the command/response format when directly reading extension file registers. For more details on the order and contents of data items of the areas marked by " " shown in the control procedure diagram, refer to Section 6.1.
Page 485 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Communication in ASCII code (Data name) Device No. External device side H L H L H L (Example) (Data name) Data for the number of designed device points Programmable controller CPU side (Characters for the number of device points) H L H (Example)
Page 486: Direct Writing Of The Extension File Register (Command: 3C)
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.4.7 Direct writing of the extension file register (command: 3C) The examples shown in this section explain the command/response format when directly writing to extension file registers. For more details on the order and contents of data items of the areas marked by " " shown in the control procedure diagram, refer to Section 6.1.
Page 487: Test Of Extension File Register (Random Write) (Command: 19)
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.4.8 Test of extension file register (random write) (command: 19) The examples shown in this section explain the command/response format when writing data by designating extension file registers at random. For more details on the order and contents of data items of the areas marked by " " shown in the control procedure diagram, refer to Section 6.1.
Page 488: Monitoring Extension File Registers
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.4.9 Monitoring extension file registers The contents of extension file registers in the programmable controller CPU can be monitored from an external device by registering the relevant block numbers and device numbers to the E71 in advance and executing a monitoring command from the external device.
Page 489 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Monitor data registration of extension file register (command: 1A) The examples shown in this section explain the command/response format when registering device numbers of extension file registers to be monitored. For more details on the order and contents of data items of the areas marked by "...
Page 490 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (3) Monitor (command: 1B) The examples shown in this section explain the command/response format when monitoring extension file registers registered by monitor data registration. For more details on the order and contents of data items of the areas marked by "...
Page 491 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.5 Reading and Writing in the Buffer Memory of an Intelligent Function Module The following explains how to designate the control procedure, as well as the contents of setting items and designation examples, when reading data from and writing data to the buffer memory of an intelligent module (special functional module) in an A series programmable controller CPU station or a MELSECNET/10 (both are other station).
Page 492: Understanding The Intelligent Function Module Numbers In The Control Procedure
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.5.2 Understanding the intelligent function module numbers in the control procedure (1) Module number of an intelligent function module that occupies 1 slot The intelligent function module number designated in the control procedure is the first 2 digits of the last (3-digit) number of the input/output signal (I/O address).
Page 493 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES In case of a module that assign the last half slots as empty slots (A61LS, etc.) ……Intelligent function module number "01 " 16 points In case of a module in which both an intelligent function module and an input/output module are assigned (In case of the A81CPU) ……Intelligent function module number "03...
Page 494: Reading From The Buffer Memory Of An Intelligent Function Module (Command: 0E)
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.5.3 Reading from the buffer memory of an intelligent function module (command: 0E) The examples shown in this section explain the command/response format when reading data from the buffer memory of the intelligent function module. For more details on the order and contents of data items of the areas marked by "...
Page 495 6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES (2) Communication in ASCII code (Data name) Head External device address side H L H L H L H L (Example) (Data name) Indicates the head buffer Data for the number of designed device memory address (007F0 points...
Page 496: Writing To The Buffer Memory Of An Intelligent Function Module (Command: 0F)
6 WHEN COMMUNICATING USING THE A COMPATIBLE 1E FRAMES 6.5.4 Writing to the buffer memory of an intelligent function module (command: 0F) The examples shown in this section explain the command/response format when writing data to the buffer memory of the intelligent function module. For more details on the order and contents of data items of the areas marked by "...
Page 497: Appendix 1 Reading And Writing By Designation Of The Device Memory Extension
APPENDICES APPENDICES Appendix 1 Reading and Writing by Designation of the Device Memory Extension The extension designation of the device memory is used by an external device to designate other devices than the ones described in Section 3.3.1 (3) using the commands listed in Section 3.3.1 (1).
Page 498 APPENDICES [Designation-4] A designation of target device number for devices of [Designation-1] and [Designation-2] above and Section 3.3.1 (3) by qualifying devices with device numbers and index registers. For example, by designating D0 and Z0, device memory (D4) can be accessed. Access to D4 is achieved as expressed in this sequence program (Stored value)
Page 499: Appendix 1.1 Data Order And Contents In The Character Areas When The Device Memory Extension Is Designated
APPENDICES Appendix 1.1 Data order and contents in the character areas when the device memory extension is designated This section explains what is designated in the additional area for extension designation, etc. when designating extension of a device memory that reads and writes data.
Page 500 APPENDICES (b) Contents of character areas when designating extension of device memory The following tables show each value to be designated in the character areas when designating extension of device memory. (Data communication in ASCII code) Value designated by an external device Number of designated characters [Designation-1]...
Page 501 APPENDICES c) The following contents are designated with a subcommand. 1 1/0 Units designation 0: Read/write in word units, or use commands for which no units need to be specified. 1: Read/write in bit units. Monitor condition designation (Select when the random read and monitor data registration functions are used) 0: Monitor without conditions (when using functions other than the above) 1: Monitor with conditions Device memory extension designation...
Page 502 APPENDICES Extension setting qualification (for [Designation-3]) This value is used to designate modules of arbitrary network number and input/output signal, by using the designated value in the extension setting as offset value for the network number and input/output signal, and furthermore using the index register. a) Data communication in ASCII code The value shown below is transmitted sequentially beginning from the most significant digit.
Page 503 APPENDICES 4) Device qualification and indirect designation (Device qualification: for [Designation-4]) This data item is for designating an arbitrary device number of the same device by using the designation value in head device (or device) as the offset value for the device number, and further adding the value in the index register.
Page 504: Appendix 1.2 Device Memory Which Can Have Designated Extensions And An Example Of Designation
APPENDICES Appendix 1.2 Device memory which can have designated extensions and an example of designation (a) Device memory which can have extensions designated The extension designation is possible for the following device memory of the modules on the stations where the C24/E71 is loaded or on the Q/L/QnACPU station connected over CC-Link IE Controller Network, CC- Link IE Field Network, MELSECNET/H, or MELSECNET/10.
Page 505 APPENDICES Example of device memory extension designation The following diagrams illustrate examples of device memory extension designation (using subcommands without monitor condition). [Designation-1] Accessing the following device memory • Target module : Network module with network number 8 (008 • Device number : X100: Access in bit units (Designation method when performing data communication in ASCII code) (Data name) External device...
Page 506 APPENDICES [Designation-2] Accessing the following buffer memory • Target module : Intelligent function module with input/output signal 010 • Head address : 3072 (C00 (Designation method when performing data communication in ASCII code) (Data name) External device side (Example) (Designation method when performing data communication in binary code) (Data name) External device side...
Page 507 APPENDICES [Designation-3] Accessing the following device memory • Target module : Network module whose network number indicated by 12 (0C ) + Z0 • Head address : W100 (Designation method when performing data communication in ASCII code) (Data name) External device side (Example) (Designation method when performing data communication in binary code)
Page 508 APPENDICES [Designation-4] Accessing the following device memory • Device number : Internal relay (M) : Access in bit units designated by M200 + Z3 (Designation method when performing data communication in ASCII code) (Data name) External device side (Example) (Designation method when performing data communication in binary code) (Data name) External device side...
Page 509 APPENDICES Accessing the following device memory • Target module : Network module with network number 8 (008 • Device number : Link input (X) : Access in bit units indicated by X100 + (Designation method when performing data communication in ASCII code) (Data name) External device side...
Page 510 APPENDICES Accessing the following buffer memory • Target module : Intelligent function module with head input/output signal 010 • Head address : The address indicated by 3072 (C00 ) + Z7 Accessing the following buffer memory • Target module : Intelligent function module whose head input/output signal is indicated by 010 + Z12 •...
Page 511 APPENDICES [Designation-5] Accessing the following device memory • Device number : Device memory address : Access in word stored in data register (D) units indicated by D100 + Z4 (Designation method when performing data communication in ASCII code) (Data name) External device side (Example)
Page 512: Appendix 1.3 Restrictions When Designating The Device Memory Extension
APPENDICES Appendix 1.3 Restrictions when designating the device memory extension This section explains the restrictions that apply when designating the device memory extension. (a) Commands that can designate the device memory extension The following table outlines the device memory extension designation items for each of the commands for reading from/writing to the device memory for QnA compatible 3E/3C/4C frames and 4E frame.
Page 513: Appendix 2 Reading From And Writing To The Buffer Memory
APPENDICES Appendix 2 Reading from and Writing to the Buffer Memory This section explains functions used by an external device to read or write data in the buffer memory of an intelligent function module (including special function modules) loaded on a Q/LCPU station on which the C24/E71 is loaded (local station), or on a programmable controller station without the C24/E71 in a network system (other station).
Page 514 APPENDICES (2) Target functions/commands of the read/write methods shown in the table • QnA extension designation: Read/write with the device memory extension designation shown in Appendix 1. • Commands for QnA compatible 3E, QnA compatible 3C, QnA compatible 4C frames and 4E frame "0613"...
Page 515: Appendix 3 Processing Time Of The Programmable Controller Cpu Side While Communicating Using The Mc Protocol
APPENDICES Appendix 3 Processing Time of the Programmable Controller CPU Side While Communicating Using the MC Protocol This section explains the processing time on the programmable controller CPU side while communicating using the MC protocol. Appendix 3.1 Processing time of the programmable controller CPU (increase in scan time) In data communication using the MC protocol, the programmable controller CPU, while in the RUN status, processes requests from an external device for the number of processing points that can be performed for each END processing.
Page 516 APPENDICES POINT The programmable controller CPU performs only one of the above operations during END processing. If the programming tool and modules simultaneously access the programmable controller CPU, the newly-requested processing has to wait until the current processing ends. In this case, the number of scans required for the processing increases even more.
Page 517 APPENDICES (b) For Q02HCPU Intervening time [ms] Number of scans required for (Increase in scan time) processing Number of Sub- Q02HCPU Command access command Number of Number of points 1)/2) Online change Online change Item access points: access points: enabled disabled When 1) When 2)
Page 518 APPENDICES (c) For Q06UDHCPU Intervening time [ms] ( Number of scans required for (Increase in scan time) processing ( Number of Sub- Q06UDHCPU Command access command Number of Number of points 1)/2) Online change Online change Item access points: access points: enabled disabled When 1)
Page 519 APPENDICES POINT The programmable controller CPU performs only one of the above operations during END processing. If the programming tool and modules simultaneously access the programmable controller CPU, the newly-requested processing has to wait until the current processing ends. In this case, the number of scans required for the processing increases even more.
Page 520 APPENDICES For Q06UDVCPU Intervening time [ms] ( Number of scans required for (Increase in scan time) processing ( Number of Sub- Q06UDVCPU Command access command Number of Number of points 1)/2) Online change Online change Item access points: access points: enabled disabled When 1)
Page 521 APPENDICES POINT The programmable controller CPU performs only one of the above operations during END processing. If the programming tool and modules simultaneously access the programmable controller CPU, the newly-requested processing has to wait until the current processing ends. In this case, the number of scans required for the processing increases even more.
Page 522 APPENDICES For L02CPU, L02CPU-P Intervening time [ms] ( Number of scans required for (Increase in scan time) processing ( Number of Sub- L02CPU, L02CPU-P Command access command Number of Number of points 1)/2) Online change Online change Item access points: access points: enabled disabled...
Page 523 APPENDICES POINT The programmable controller CPU performs only one of the above operations during END processing. If the programming tool and modules simultaneously access the programmable controller CPU, the newly-requested processing has to wait until the current processing ends. In this case, the number of scans required for the processing increases even more.
Page 524 APPENDICES For L26CPU, L26CPU-BT, L26CPU-PBT Intervening time [ms] ( Number of scans required for (Increase in scan time) processing ( Number of L26CPU, L26CPU-BT, Sub- Command access L26CPU-PBT command points 1)/2) Number of Number of Item Online change Online change access points: access points: enabled...
Page 525 APPENDICES POINT The programmable controller CPU performs only one of the above operations during END processing. If the programming tool and modules simultaneously access the programmable controller CPU, the newly-requested processing has to wait until the current processing ends. In this case, the number of scans required for the processing increases even more.
Page 526 APPENDICES (2) Processing time of the programmable controller CPU when the serial communication function is used (In the case of command (format 4) for QnA compatible 4C frame) Intervening time [ms] Number of scans required for (Increase in scan time) processing Number of Q00CPU, Q01CPU...
Page 527 INDEX Access timing of the programmable controller Global function ...........3 - 241 CPU side ............2 - 6 Accessible intelligent function modules..3 - 139 Accessible range ........... 2 - 3 Header............3 – 3 Accessible station........2 - 12 Head device ..........3 - 67 Application data..........
Page 528 Remote operation........3 – 144 Clear mode ..........3 - 145 Mode ............. 3 – 145 Remote password ........3 – 297 Request destination module I/O number..3 - 41 Sum check code......... 3 – 44 Subheader ..........3 - 3, 6 - 4 Text (Command) ........
Page 529 6. Failure caused by reasons unpredictable by scientific technology standards at time of shipment from Mitsubishi. 7. Any other failure found not to be the responsibility of Mitsubishi or that admitted not to be so by the user. 2. Onerous repair term after discontinuation of production (1) Mitsubishi shall accept onerous product repairs for seven (7) years after production of the product is discontinued.
Page 530 Microsoft, Windows, Windows NT, and Windows Vista are registered trademarks of Microsoft Corporation in the United States and other countries. Pentium is a trademark of Intel Corporation in the United States and other countries. Ethernet is a trademark of Xerox Corporation. The SD logo and SDHC logo are trademarks.
Page 532 Phone: +380 (0)44 / 494 33 55 Fax: +370 (0)5 / 232 2980 Fax: +380 (0)44 / 494-33-66 Mitsubishi Electric Europe B.V. /// FA - European Business Group /// Gothaer Straße 8 /// D-40880 Ratingen /// Germany Tel.: +49(0)2102-4860 /// Fax: +49(0)2102-4861120 /// info@mitsubishi-automation.com /// www.mitsubishi-automation.com...

This manual is also suitable for:

Melsec qj71c24 Melsec qj71c24-r2 Melsec qj71e71-100 Melsec qj71e71-b5 Melsec qj71e71-b2 Melsec lj71c24 ... Show all

Mitsubishi MELSEC Q Series Reference Manual

Quick Links

Related Manuals for Mitsubishi MELSEC Q Series

Summary of Contents for Mitsubishi MELSEC Q Series