MELSEC iq-f FX5 User's Manual (SLMP)

Transcription

1 MELSEC iq-f FX5 User's Manual (SLMP)

2

3 SAFETY PRECAUTIONS (Read these precautions before use.) Before using this product, please read this manual and the relevant manuals introduced in this manual carefully and pay full attention to safety in order to handle the product correctly. This manual classifies the safety precautions into two categories: [ WARNING] and [ CAUTION]. WARNING CAUTION Indicates that incorrect handling may cause hazardous conditions, resulting in death or severe injury. Indicates that incorrect handling may cause hazardous conditions, resulting in minor or moderate injury or property damage. Depending on the circumstances, procedures indicated by [ CAUTION] may also cause severe injury. It is important to follow all precautions for personal safety. Store this manual in a safe place so that it can be read whenever necessary. Always forward it to the end user. [DESIGN PRECAUTIONS] WARNING Make sure to set up the following safety circuits outside the PLC to ensure safe system operation even during external power supply problems or PLC failure. Otherwise, malfunctions may cause serious accidents. (1) Note that when the CPU module detects an error, such as a watchdog timer error, during selfdiagnosis, all outputs are turned off. Also, when an error that cannot be detected by the CPU module occurs in an input/output control block, output control may be disabled. External circuits and mechanisms should be designed to ensure safe machinery operation in such a case. Do not write any data to the "system area" of the buffer memory in an intelligent function module. Doing so may cause malfunction of the programmable controller system. When executing control (data change) to a running other station programmable controller by connecting the external device to the SLMP compatible device, configure interlock circuits in the program of the other station programmable controller to ensure that the entire system operates safely at any time. For other controls to a running other station programmable controller (such as program modification or operating status change), read relevant manuals carefully and ensure the safety before the operation. Especially, in the case of a control from an external device to a remote other station programmable controller, immediate action cannot be taken for a problem on the programmable controller due to a communication failure. Determine the handling method as a system when communication failure occurs along with configuration of interlock circuit on other station PLC program, by considering external equipment and other station PLC. Do not write any data into the "system area" or "write protect area" of the buffer memory in the SLMP compatible device or intelligent function module. Also, do not output (ON) any "use prohibited" signals among the signals which are output to the SLMP compatible device and intelligent function device. Executing data writing to the "system area" or "write protect area", or outputting "use prohibited" signals may cause malfunction of the programmable controller alarm. To maintain the safety of the programmable controller system against unauthorized access from external devices via the network, take appropriate measures. To maintain the safety against unauthorized access via the Internet, take measures such as installing a firewall. 1

4 [STARTUP AND MAINTENANCE PRECAUTIONS] WARNING Before modifying the program in operation, forcible output, running or stopping the PLC, read through this manual carefully, and ensure complete safety. An operation error may damage the machinery or cause accidents. Do not change the program in the PLC from two or more peripheral equipment devices at the same time. (i.e. from an engineering tool and a GOT) Doing so may cause destruction or malfunction of the PLC program. [STARTUP AND MAINTENANCE PRECAUTIONS] CAUTION Read relevant manuals carefully and ensure the safety before performing online operations (operation status change) with peripheral devices connected to the running SLMP compatible device or CPU modules of other stations. Improper operation may damage machines or cause accidents. 2

5 INTRODUCTION This manual explains the s and settings related to the SLMP function of the MELSEC iq-f Series. It should be read and understood before attempting to install or use the module. Always forward it to the end user. Regarding use of this product This product has been manufactured as a general-purpose part for general industries, and has not been designed or manufactured to be incorporated in a device or system used in purposes related to human life. Before using the product for special purposes such as nuclear power, electric power, aerospace, medicine or passenger movement vehicles, consult Mitsubishi Electric. This product has been manufactured under strict quality control. However when installing the product where major accidents or losses could occur if the product fails, install appropriate backup or failsafe functions in the system. Note If in doubt at any stage during the installation of the product, always consult a professional electrical engineer who is qualified and trained to the local and national standards. If in doubt about the operation or use, please consult the nearest Mitsubishi Electric representative. Since the examples indicated by this manual, technical bulletin, catalog, etc. are used as a reference, please use it after confirming the function and safety of the equipment and system. Mitsubishi Electric will accept no responsibility for actual use of the product based on these illustrative examples. This manual content, etc. may be changed without a notice for improvement. The information in this manual has been carefully checked and is believed to be accurate; however, if you notice a doubtful point, an error, etc., please contact the nearest Mitsubishi Electric representative. When doing so, please provide the manual number given at the end of this manual. 3

6 CONTENTS SAFETY PRECAUTIONS INTRODUCTION RELEVANT MANUALS TERMS CHAPTER 1 OUTLINE Outline of SLMP Features of SLMP CHAPTER 2 SLMP DATA COMMUNICATION Type and Application of the Data Communication Frame Allowable Access Range of Each Data Communication Frame SLMP frame Access range Concept of Control Procedure of SLMP Access Timing of the CPU Module Side Transfer Time CHAPTER 3 MESSAGE FORMAT Message Format Message format and control procedure Application data items Transfer data in character area Character areas CHAPTER 4 COMMANDS List of Commands and Functions Access Commands range Read (Batch) Write (Batch) Read Random Write Random Read Block Write Block Remote Control Before the remote operation Remote RUN Remote STOP Remote PAUSE Remote latch clear Remote RESET Processor type read Clear Error Self-Test

7 4.6 Remote Password Unlock or Lock Lock Unlock APPENDIX 95 Appendix 1 Memory Specification Access to module access device Access with indirect of the device No. by using index register or long index register Access with indirect of the device No. by using the values stored in word device Appendix 2 Command Comparison between MC Protocol and SLMP Appendix 3 CPU Module Processing Time of SLMP Appendix 4 Added and Enhanced Functions INDEX 18 REVISIONS WARRANTY TRADEMARKS CONTENTS 5

8 RELEVANT MANUALS Manual name <manual number> MELSEC iq-f FX5 User's Manual (Startup) <JY997D5821> MELSEC iq-f FX5U User's Manual (Hardware) <JY997D5531> MELSEC iq-f FX5UC User's Manual (Hardware) <JY997D6141> MELSEC iq-f FX5 User's Manual (Application) <JY997D5541> MELSEC iq-f FX5 Programming Manual (Program Design) <JY997D5571> MELSEC iq-f FX5 Programming Manual (Instructions, Standard Functions/ Function Blocks) <JY997D5581> MELSEC iq-f FX5 User's Manual (Serial Communication) <JY997D5591> MELSEC iq-f FX5 User's Manual (MELSEC Communication Protocol) <JY997D681> MELSEC iq-f FX5 User's Manual (MODBUS Communication) <JY997D5611> MELSEC iq-f FX5 User's Manual (Ethernet Communication) <JY997D5621> MELSEC iq-f FX5 User's Manual (SLMP) <JY997D561> (This manual) MELSEC iq-f FX5 User's Manual (CC-Link IE) <JY997D6421> MELSEC iq-f FX5 User's Manual (Positioning Control) <JY997D5631> MELSEC iq-f FX5 User's Manual (Analog Control) <JY997D651> GX Works3 Operating Manual <SH-81215ENG> TERMS Description Performance s, procedures before operation, and troubleshooting of the CPU module. Describes the details of hardware of the FX5U CPU module, including input/ output s, wiring, installation, and maintenance. Describes the details of hardware of the FX5UC CPU module, including input/ output s, wiring, installation, and maintenance. Describes basic knowledge required for program design, functions of the CPU module, devices/labels, and parameters. Describes s of ladders, ST, FBD/LD, and other programs and labels. Describes s of instructions and functions that can be used in programs. Describes N:N network, MELSEC Communication protocol, inverter communication, non-protocol communication, and predefined protocol support. Explains methods for the device that is communicating with the CPU module by MC protocol to read and write the data of the CPU module. Describes MODBUS serial communication. Describes the functions of the built-in Ethernet port communication function. Explains methods for the device that is communicating with the CPU module by SLMP to read and write the data of the CPU module. Describes the functions of the CC-Link IE field network. Describes the positioning function. Describes the analog function. System configuration, parameter settings, and online operations of GX Works3. Unless otherwise specified, this manual uses the following terms. indicates a variable part to collectively call multiple models or versions. (Example) FX5U-32MR/ES, FX5U-32MT/ES FX5U-32M /ES For details on the FX3 devices that can be connected with the FX5, refer to the User s Manual (Hardware) of the CPU module to be used. Terms Description s FX5 FX3 FX5 CPU module FX5U CPU module FX5UC CPU module module FX5 extension module FX3 extension module Generic term for FX5U and FX5UC PLCs Generic term for FX3S, FX3G, FX3GC, FX3U, and FX3UC PLCs Generic term for FX5U CPU module and FX5UC CPU module Generic term for FX5U-32MR/ES, FX5U-32MT/ES, FX5U-32MT/ESS, FX5U-64MR/ES, FX5U-64MT/ES, FX5U-64MT/ESS, FX5U-8MR/ES, FX5U-8MT/ES, FX5U-8MT/ESS, FX5U-32MR/DS, FX5U-32MT/DS, FX5U-32MT/DSS, FX5U-64MR/DS, FX5U-64MT/DS, FX5U-64MT/DSS, FX5U-8MR/DS, FX5U-8MT/DS, and FX5U-8MT/DSS Generic term for FX5UC-32MT/D, FX5UC-32MT/DSS, FX5UC-64MT/D, FX5UC-64MT/DSS, FX5UC-96MT/D, and FX5UC-96MT/DSS Generic term for FX5 extension modules and FX3 function modules Generic term for I/O modules, FX5 extension power supply modules, and FX5 intelligent function modules Generic term for FX3 extension power supply module and FX3 intelligent function module 6

9 Terms module (extension cable type) module (extension connector type) I/O module Input module Input module (extension cable type) Input module (extension connector type) Output module Output module (extension cable type) Output module (extension connector type) Input/output module Input/output module (extension cable type) Input/output module (extension connector type) Powered input/output module High-speed pulse input/output module power supply module FX5 extension power supply module FX5 extension power supply module (extension cable type) FX5 extension power supply module (extension connector type) FX3 extension power supply module Intelligent module Intelligent function module FX5 intelligent function module FX3 intelligent function module Expansion board Communication board Expansion adapter Communication adapter Analog adapter Bus conversion module Bus conversion module (extension cable type) Bus conversion module (extension connector type) Connector conversion module Connector conversion module (extension cable type) Connector conversion module (extension connector type) Extended extension cable Connector conversion adapter Battery Description Generic term for Input modules (extension cable type), Output modules (extension cable type), Input/output modules (extension cable type), Powered input/output module, High-speed pulse input/output module, power supply module (extension cable type), Connector conversion module (extension cable type), Intelligent function modules, and Bus conversion module (extension cable type) Generic term for Input modules (extension connector type), Output modules (extension connector type), Input/ output modules (extension connector type), power supply module (extension connector type), Connector conversion module (extension connector type), and Bus conversion module (extension connector type) Generic term for input modules, output modules, Input/output modules, powered input/output modules, and high-speed pulse input/output modules Generic term for Input modules (extension cable type) and Input modules (extension connector type) Generic term for FX5-8EX/ES and FX5-16EX/ES Generic term for FX5-C16EX/D, FX5-C16EX/DS, FX5-C32EX/D, and FX5-C32EX/DS Generic term for output modules (extension cable type) and output modules (extension connector type) Generic term for FX5-8EYR/ES, FX5-8EYT/ES, FX5-8EYT/ESS, FX5-16EYR/ES, FX5-16EYT/ES, and FX5-16EYT/ESS Generic term for FX5-C16EYT/D, FX5-C16EYT/DSS, FX5-C32EYT/D, and FX5-C32EYT/DSS Generic term for input/output modules (extension cable type) and input/output modules (extension connector type) Generic term for FX5-16ER/ES, FX5-16ET/ES, and FX5-16ET/ESS Generic term for FX5-C32ET/D and FX5-C32ET/DSS Generic term for FX5-32ER/ES, FX5-32ET/ES, FX5-32ET/ESS, FX5-32ER/DS, FX5-32ET/DS, and FX5-32ET/ DSS Generic term for FX5-16ET/ES-H and FX5-16ET/ESS-H Generic term for FX5 extension power supply module and FX3 extension power supply module Generic term for FX5 extension power supply module (extension cable type) and FX5 extension power supply module (extension connector type) Different name for FX5-1PSU-5V Different name for FX5-C1PS-5V Different name for FX3U-1PSU-5V The abbreviation for intelligent function modules Generic term for FX5 intelligent function modules and FX3 intelligent function modules Generic term for FX5-4SSC-S, FX5-8SSC-S, and FX5-CCLIEF Generic term for FX3U-4AD, FX3U-4DA, FX3U-4LC, FX3U-1PG, FX3U-2HC, FX3U-16CCL-M, FX3U-64CCL, and FX3U-128ASL-M Generic term for board for FX5U CPU module Generic term for FX5-232-BD, FX5-485-BD, and FX5-422-BD-GOT Generic term for adapter for FX5 CPU module Generic term for FX5-232ADP and FX5-485ADP Generic term for FX5-4AD-ADP, FX5-4DA-ADP, FX5-4AD-PT-ADP, and FX5-4AD-TC-ADP Generic term for Bus conversion module (extension cable type) and Bus conversion module (extension connector type) Different name for FX5-CNV-BUS Different name for FX5-CNV-BUSC Generic term for Connector conversion module (extension cable type) and Connector conversion module (extension connector type) Different name for FX5-CNV-IF Different name for FX5-CNV-IFC Generic term for FX5-3EC and FX5-65EC Different name for FX5-CNV-BC Different name for FX3U-32BL 7

10 Terms Peripheral device GOT Software packages Engineering tool GX Works3 Communication-related Built-in RS-485 port Serial port SLMP SLMP-compatible device MC protocol MC protocol-compatible device External device Own station Other station Description Generic term for engineering tools and GOTs Generic term for Mitsubishi Graphic Operation Terminal GOT1 and GOT2 series The product name of the software package for the MELSEC programmable controllers The product name of the software package, SWnDND-GXW3, for the MELSEC programmable controllers (The 'n' represents a version.) Built-in RS-485 port of the CPU module. Generic term for the four ports consisting of the FX5 Series built-in RS-485 port (CH1), communication board (CH2), communication adapter 1 (CH3), and communication adapter 2 (CH4). The abbreviation for Seamless Message Protocol. A protocol for accessing SLMP-compatible devices and PLCs that are connected to SLMP-compatible devices from external devices. Generic term for devices that can receive SLMP messages. The abbreviation of the MELSEC communication protocol. A protocol for accessing MC protocol-compatible devices and PLCs that are connected to MC protocolcompatible devices from external devices. Generic term for devices that can receive MC protocol messages. Generic term for devices of communication target (such as personal computer, HMI) Own station indicates the station directly connected to external device. Other station indicates a station connected to the own station on the network. External device Other station Own station Networks Other station Relay station Module access device Buffer memory A station that includes two or more network modules. Transient transmission is performed through this station to stations on other networks. A generic term for the module access device of the MELSEC iq-r series/melsec iq-f series and intelligent function module device of the MELSEC-Q/L series Memory areas of Intelligent function modules and SLMP-compatible devices for storing setting values and monitor values. 8

11 1 OUTLINE This manual describes the method for reading or writing data in a CPU module with the data communication function of the external equipment using SLMP. When transferring data using SLMP, always refer to Page 12 SLMP DATA COMMUNICATION Outline of SLMP SLMP is a protocol used for access from a CPU module or an external device (such as a personal computer or an HMI) to an SLMP compatible device through Ethernet. SLMP communications are available among devices that can transfer messages by SLMP. The message format of 3E frame of SLMP is the same as that of the QnA compatible 3E frame of MC protocol. Therefore, external devices used with MC protocol can be connected to an SLMP compatible device directly. For details on MC protocol, refer to the following manual. MELSEC-Q/L MELSEC Communication Protocol Reference Manual data in a CPU module can be written or read from a personal computer or an HMI by using SLMP. Writing and reading the device allows operation monitoring, data analyzing, and production managing of a CPU module by a personal computer or an HMI. In addition, external illegal access can be prevented by the remote password function. CPU module Hub HMI SLMP communication The following shows the flow for starting SLMP communication. 1. Connect cables and external devices. Configure the connection for the SLMP communication. 2. Set parameters. Set parameters with engineering tool. 3. Write the set parameters to the CPU module. Write set parameters to a CPU module. Validate the parameters by turning off to on or reset. 1 OUTLINE 1.1 Outline of SLMP 9

12 1.2 Features of SLMP System monitoring from an external device (such as personal computer, HMI) An external device can send a request message in SLMP message format to an CPU module to enable device read, allowing system monitoring. Using SLMP allows not only device data reading but also device data writing and resetting an CPU module Reading devices message 1 15 External device Message format of SLMP CPU module Header Subheader Destination Command Ethernet Message format of SLMP Header Subheader Destination Data Response message Connecting an external device used with MC protocol An external device that uses the QnA compatible 3E frame of MC protocol can be connected to an CPU module directly. External device (MC protocol) CPU module Personal computer HMI QnA compatible 3E frame (Cognex product etc.) Access via network SLMP allows an external device to access modules in the same network and other networks seamlessly via an SLMP compatible device. CC-Link IE Field Network External device Ethernet SLMP-compatible device Switching hub SLMP-compatible device 1 15 Read/write OUTLINE 1.2 Features of SLMP

13 Easy SLMP communication with the predefined protocol support function SLMP communication can be easily used with the predefined protocol support function of the engineering tool. Like external devices communicating on SLMP, CPU modules can control SLMP-compatible devices. 1 SLMP-compatible device message SLMP Header Read command of internal memory Memory type Head memory number Read point SLMP Header Data [ + ] Data of internal memory Data [ +1 ] Data [ +2 ] Response message Data [ +2 ] 1 OUTLINE 1.2 Features of SLMP 11

14 2 SLMP DATA COMMUNICATION This chapter describes the SLMP data communication by which the external equipment reads or writes data to a CPU module. 2.1 Type and Application of the Data Communication Frame This section describes the type and application of the frame (data communication message) by which the external equipment accesses a CPU module with SLMP. When the external equipment accesses a CPU module using Ethernet, the data communication is executed by sending or receiving a command message (access request) and response message (response) of the following frame. Target communication method Applicable communication frames Communication data Section of control procedure Ethernet 3E frame ASCII or binary Page 16 MESSAGE FORMAT There are 2 types of ASCII : ASCII (X, Y OCT) and ASCII (X, Y HEX). The method of the device number for the X (input) and Y (output) to be accessed is different from each other. ( Page 44 Access) ASCII (X, Y OCT): octal ASCII (X, Y HEX): hexadecimal Unless otherwise specified, the both of them are described as ASCII. ASCII (X, Y HEX) cannot be used depending on the version. For supported versions, refer to Page 17 Added and Enhanced Functions. 3E frame The message format is the same as the QnA compatible 3E frame of MC protocol. The main purpose of the frame is to access all the devices of the CPU module from the external equipment. The frame enables access to the device of the MELSEC iq-r/l/q/a Series PLC CPUs via the CC-Link IE controller network, CC-Link IE field network, or Ethernet. When using binary s, the communication time will decrease since the amount of communication data is reduced by approximately half comparing to using ASCII s SLMP DATA COMMUNICATION 2.1 Type and Application of the Data Communication Frame

15 2.2 Allowable Access Range of Each Data Communication Frame The following shows the frame and access range of a message used in SLMP. SLMP frame 2 Frame Ethernet communication frame (3E frame) Access range Type of the network which connects the external device with the connecting stations Ethernet Reference Page 16 MESSAGE FORMAT Ethernet communication frame When the external device is connected directly with the CPU module via Ethernet In the following system configuration, communication with the CPU module is possible using the Ethernet communication frame from the external device. External device Connecting station A A Ethernet A Assigned symbol A Description Station directly connected to the external device 2.3 Concept of Control Procedure of SLMP This section describes the concept of the procedure (control procedure) when the external equipment accesses a CPU module with SLMP. Sending a command message Data communication using SLMP communication is executed in half-duplex communication. To access the CPU module, send the next command message after receiving a response message for the preceding command message from the CPU module. (Until the receiving of the response message is completed, the next command message cannot be sent.) External equipment (Command message) (Command message) CPU module (Response message) (Response message) When a response message of completion for a command message cannot be received When a response message of completion with an error is received, take corrective actions depending on the error in the response message. 2 SLMP DATA COMMUNICATION 2.2 Allowable Access Range of Each Data Communication Frame 13

16 2.4 Access Timing of the CPU Module Side The following shows the access timing of the CPU module side when the CPU module is accessed from the external equipment using the built-in Ethernet port. RUN External device Read/Write command (Command) Response to a command (Response) 1) ACK *1 2) ACK *1 CPU module Step END Step END Step END Step END END processing END processing END processing Processing for a command from the external equipment STOP External device Read/Write command (Command) Response to a command (Response) 1) ACK *1 2) ACK *1 CPU module END END END END END END processing END processing END processing END processing Processing for a command from the external equipment *1 ACK shown in the figure is a response which is sent or received between the CPU module and external equipment (a response for receiving a massage) when the CPU module is accessed from the external equipment using TCP/IP communication. This response is not the same as the one for the processing requested from the external equipment by a command message (processing result). When access is executed using UDP/IP communication via the built-in Ethernet port, an ACK response is not sent. 1. To send a read request or a write request to the CPU module side from the external equipment, a command message is sent. 2. The CPU module reads or writes the data according to the description requested from the external equipment when the END instruction of the CPU module is executed and sends a response message (response) including the processing result to the external equipment of the request source. Access between the external equipment and CPU module is processed at each END processing when the CPU module is running for a command request. (The scan time becomes longer by the processing time of the command request.) When accesses are requested simultaneously to the CPU module from multiple external equipment, the processing requested from the external device may be on hold until several END processings take place depending on the request timing SLMP DATA COMMUNICATION 2.4 Access Timing of the CPU Module Side

17 2.5 Transfer Time Link time Calculation method Calculate the minimum processing time of the SLMP communication by the following calculation formula. However, the processing time may become longer depending on the load of the network (how much a line is crowded), window size of each connecting device, number of connections to be used simultaneously, and system configuration. As a guideline, recognize the value calculated by the following calculation formula as the processing time when a communication is executed by only one connection. Minimum processing time of the SLMP communication (for batch read or batch write) Tfs = Ke + (Kdt Df) + Scr Number of scans required for processing + ACK processing time of external equipment Tfs: Time from when the request data of a personal computer is received until the CPU module completes the processing (Unit: ms) *1 Ke, Kdt: Constant (Refer to the following table.) Df: Number of words of the request data + Number of words of the response data (application data part) Scr: Scan time *1 The following shows the timing from when the request data of a personal computer is received until the CPU module completes the processing. External device (personal computer) 2 Command Response ACK (only message ACK (only message for TCP) for TCP) Step END Step END Scan time of the CPU module Communication description Tfs TCP/IP communication UDP/IP communication Ke Kdt Ke Kdt Batch read Batch write Ex. [Calculation example 1] Time from when the request data of a personal computer is received until the processing is completed, when a TCP/IP communication is executed between personal computers and 32 points data read from the data register (D) of own station by the SLMP communication in binary (Unit: ms) The scan time of the mounted station is 4 ms. Tfs = 1 + (.1 32) ACK processing time of external equipment [Calculation example 2] Time from when the request data of a personal computer is received until the processing is completed, when a TCP/IP communication is executed between personal computers and 32 points data written to the data register (D) of own station by the SLMP communication in binary (Unit: ms) The scan time of the mounted station is 4 ms. Tfs = 1 + (.1 32) ACK processing time of external equipment 2 SLMP DATA COMMUNICATION 2.5 Transfer Time 15

18 3 MESSAGE FORMAT This chapter describes the message data format, the data method, and limitations etc. when performing SLMP data communication using the 3E frame to the Ethernet port. Frame type Ethernet port Remark 3E frame Communicable The message format is the same as the QnA compatible 3E frame 3.1 Message Format This section describes the message format for each command when performing the data communication using the 3E frame. Message format and control procedure This section describes the message format and the control procedures when performing the data communication using the 3E frame. Data format The data format for communicating between the built-in Ethernet port and the external device consists of header and application data. message Header Subheader network No. station No. module I/O No. Application data multidrop station No. data length Reserve Command data Response message Header Subheader network No. station No. Application data module I/O No. multidrop station No. Response data length End Response data Header This header is for TCP/IP and UDP/IP. Add the header for external equipment to CPU module (command message) at the external equipment side before sending the message (normally the header is added automatically). It is not necessary to set the header for CPU module to external equipment (response message) by the user because the header is added by the CPU automatically MESSAGE FORMAT 3.1 Message Format

19 Application data Application data is divided into subheader and text. The subheader indicates whether a message is the command message or the response message. (Refer to Page 18 Subheader configuration.) Text is the request data (command) and the response date (response) in each function. (For details on each function, refer to Page 4 List of Commands and Functions or and after.) When communicating data in ASCII Application data External equipment Subheader Text (command) 4 bytes The text differs depending on the function and whether the command ends normally or not. 3 CPU module 4 bytes The text differs depending on the function. Subheader Text (response) Application data When communicating data in binary Application data External equipment Subheader Text (command) 2 bytes The text differs depending on the function and whether the command ends normally or not. CPU module 2 bytes The text differs depending on the function. Subheader Text (response) Application data It is not necessary to set the response to a command from the external equipment by the user because the response is created and sent by the CPU module. 3 MESSAGE FORMAT 3.1 Message Format 17

20 Subheader configuration This section describes the subheader configuration. When communicating data in ASCII Command message 5 35H 3H 3H 3H Response message D 44H 3H 3H 3H When communicating data in binary Command message Response message 5H H DH H Control procedure This section describes the control procedures and the format of the application data when performing the data communication. The (Thick line) part shown in the message explanation diagram of this section are items common to all commands and correspond to the * portion of the message explanation diagrams indicated in Page 73 Write Block or after in this chapter. For the data contents and the data method of the (Thick line) part, refer to Page 23 Application data items. Data (ASCII/binary) to be used when communicating, it is determined by the parameters of the GX Works3. [Module Parameter] [Ethernet Port] [Communication Data Code] 18 3 MESSAGE FORMAT 3.1 Message Format

21 When communicating data in ASCII When data is read from a CPU module by external equipment External equipment CPU module (command message) Text (command) Character area A (Data name) (Example) Header 5 35H 3H Subheader 3H 3H Network number station number H L H L F F 3H 3H 46H 46H H - 3 3H 33H module I/O number multi-drop station number - L H L F F 46H 46H 3H 3H H 3H data length Reserved Command - - L H - - L H - - L 1 8 3H 31H 38H 3H 3H 3H 3H H - - L data area 3 ((Example) For 24 bytes) CPU module (When completed normally) Text (response) Header D 44H 3H Subheader 3H External equipment (response message) 3H Network number station number H L H L F F 3H 3H 46H 46H H - 3 3H 33H module I/O number multi-drop station number Response data length End - L H L H - - L H - - L F F C 46H 46H 3H 3H 3H 3H 3H 43H 3H 3H 3H 3H Character area B Response data area ((Example) For 12 bytes) The order of data items differs depending on the command or subcommand. For details, refer to the description on command details in Section 4.2 or later. (When completed with error) Header D 44H 3H Subheader 3H 3H Network number (access station) Text (response) station number (access station) H L H L F F 3H 3H 46H 46H H - 3 3H 33H module I/O number multi-drop station number Response data length End other than H Network number (responding station) station number (responding station) module I/O number Error information area multi-drop station number (For C51H) - L H L H - - L H - - L H L H L H - - L H L H - - L F F 1 6 C 5 1 F F 3 F F 46H 46H 3H 3H 3H 3H 31H 36H 43H 3H 35H31H 3H 3H 46H 46H 3H 33H 46H 46H 3H 3H Command H - - L (22 bytes) 3 MESSAGE FORMAT 3.1 Message Format 19

22 When data is written from external equipment to a CPU module External equipment CPU module (command message) Text (command) Character area C (Data name) (Example) Header 5 35H 3H Subheader 3H 3H Network number station number H L H L F F 3H 3H 46H 46H H - 3 3H 33H module I/O number multi-drop station number data length Reserved - L H L H - - L H - - L H - - L H - - L F F 2 46H 46H 3H 3H 3H 3H 32H 3H 3H 3H 3H 3H Command data area ((Example) For 32 bytes) CPU module External equipment (response message) (When completed normally) Text (response) The order of data items differs depending on the command or subcommand. For details, refer to the description on command details in Section 4.2 or later. Header D 44H 3H Subheader 3H 3H Network number station number H L H L F F 3H 3H 46H 46H H - 3 3H 33H module I/O number multi-drop station number Response data length End - L H L H - - L H - - L F F 4 46H 46H 3H 3H 3H 3H 3H 34H 3H 3H 3H 3H (4 bytes) (When completed with error) Header D 44H 3H Subheader 3H 3H Network number (access station) Text (response) station number (access station) H L H L F F 3H 3H 46H 46H H - 3 3H 33H module I/O number multi-drop station number Response data length End other than H Network number (responding station) station number (responding station) module I/O number Error information area (For C51H) - L H L H - - L H - - L H L H L H - - L H L F F 1 6 C 5 1 F F 3 F F 46H 46H 3H 3H 3H 3H 31H 36H 43H 3H 35H31H 3H 3H 46H 46H 3H 33H 46H 46H 3H 3H (22 bytes) multi-drop station number Command H - - L H - - L 2 3 MESSAGE FORMAT 3.1 Message Format

23 When communicating data in binary When data is read from a CPU module by external equipment External equipment CPU module (command message) Text (command) Character area A data area (Data name) (Example) Header Subheader Network number station number module I/O number L H 5H H H FFH FFH 3H multi-drop station number H L CH data length H H Reserved Command L H L H L H H H 3 ((Example) For 12 bytes) CPU module External equipment (response message) (When completed normally) Text (response) Header Subheader Network number station number module I/O number L H DH H H FFH FFH 3H multi-drop station number H L 6H Response data length H H L H End H H The order of data items differs depending on the command or subcommand. For details, refer to the description on command details in Section 4.2 or later. Character area B Response data area ((Example) For 6 bytes) (When completed with error) Text (response) Error information area Header Subheader Network number (access station) station number (access station) module I/O number multi-drop station number Response data length End other than H (For C51H) Network number (responding station) station number (responding station) module I/O number multi-drop station number L H L H L H L H L H L H DH H H FFH FFH 3H H BH H 51H CH H FFH FFH 3H H Command (11 bytes) 3 MESSAGE FORMAT 3.1 Message Format 21

24 When data is written from external equipment to a CPU module External equipment CPU module (command message) Text (command) Character area A data area (Data name) (Example) Header Subheader Network number station number module I/O number L H 5H H H FFH FFH 3H multi-drop station number H L CH data length H H Reserved Command L H L H L H H H ((Example) For 12 bytes) CPU module External equipment (response message) (When completed normally) Text (response) The order of data items differs depending on the command or subcommand. For details, refer to the description on command details in Section 4.2 or later. Header Subheader Network number station number module I/O number L H DH H H FFH FFH 3H multi-drop station number H L 2H Response data length H H L H End H H (2 bytes) (When completed with error) Text (response) Error information area Header Subheader Network number (access station) station number (access station) module I/O number multi-drop station number Response data length End other than H (For C51H) Network number (responding station) station number (responding station) module I/O number multi-drop station number L H L H L H L H L H L H DH H H FFH FFH 3H H BH H 51H CH H FFH FFH 3H H Command (11 bytes) 22 3 MESSAGE FORMAT 3.1 Message Format

25 Application data items This section describes the data contents and the method of common data items in the application data in each message when performing the data communication using the 3E frame. network number and request station number message Header Subheader network No. station No. module I/O No. Application data multidrop station No. data length Reserve Command data 3 Response message Header Subheader network No. station No. Application data module I/O No. multidrop station No. Response data length End Response data Specify the request network number and request station number to be used as an access in hexadecimal. Specify the request network number and request station number according to installation conditions of access stations based on the following table. Data of the response message is a value set in the request message. No. Access Station to be specified network number 1 *1 Connecting station (Within the range indicated in No. 1 in the figure below) 2 Other stations or relay station (Within the range indicated in No. 2 in the figure below) 3 Multi-drop connecting station via network (Within the range indicated in No. 3 in the figure below) (Specify the fixed value indicated on the right) H station number Access station 1 to EFH (1 to 239) 1 to 78H (1 to 12): Station number 7DH: Assigned control station/ Master station 7EH: Present control station/ Master station A station on the network where multi-drop connecting stations are connected (In the figure below, [A] is specified) FFH 1 to EFH (1 to 239) 1 to 78H (1 to 12): Station number 7DH: Assigned control station/ Master station 7EH: Present control station/ Master station *1 Please use No.1 to access FX5CPU. Another station Another station Multi-drop connection External device Connecting station Network No. 1 Relay station Network No. n Multi-drop connecting station A Multi-drop connecting station Multi-drop connecting station Ethernet MELSEC iq-r series etc. Another station Another station No. 1 No. 2 No. 3 3 MESSAGE FORMAT 3.1 Message Format 23

26 Ex. When specifying 26 (1AH) as the station number n and 16 (1H) as the station number of station A ASCII 1 A 1 31H 41H 31H 3H Network number Station number Binary 1AH 1H Network number Station number Precautions The stations of network number 24 to 255 cannot be accessed. FX5CPU cannot perform multi-drop connection. FX5CPU cannot perform connection via network. module I/O number message Header Subheader network No. station No. module I/O No. Application data multidrop station No. data length Reserve Command data Response message Header Subheader network No. station No. Application data module I/O No. multidrop station No. Response data length End Response data Select the module number of the access from the table below. When the send of the request message is a multi-drop connecting station that is connected to the request station, set the I/O number (upper 3-digits) of the serial communication module which is performing the multi-drop connection. No. Module to be accessed *1 station module I/O number 1 *2 Own station 3FFH 2 Other station (control CPU) 3FFH 3 The module which is performing multi-drop connection with serial communication module ("A" in the figure below), which is connected to the network H to 1FFH *1 FX5CPU cannot perform multi-drop connection. FX5CPU cannot perform connection via network. *2 Please use No.1 to access FX5CPU. External device Connecting station Another station Network No. 1 Relay station Another station Network No. n Multi-drop connecting station A Multi-drop connection Multi-drop connecting station Multi-drop connecting station Ethernet MELSEC iq-r series etc. Another station Another station No. 1 No. 2 No MESSAGE FORMAT 3.1 Message Format

27 Ex. When specifying the default processor (5H) as the request module I/O number ASCII 5 3H 3H 3H 35H module I/O No. Binary 5H H module I/O No. multi-drop station number message 3 Header Subheader network No. station No. module I/O No. Application data multidrop station No. data length Reserve Command data Response message Header Subheader network No. station No. Application data module I/O No. multidrop station No. Response data length End Response data Specify the station number of the SLMP compatible device linked by the multi-drop connection in the access, within the range shown in the table below. When not specifying the SLMP compatible device linked by the multi-drop connection, set H. No. Access station of external equipment multi-drop station number 1 Stations on the multi-drop connection ("F" in the figure below) 2 A station that relays the network and the multi-drop connection ("E" in the figure below) Set the station number (H to 1FH ( to 31)) ("F" in the figure below) H () 3 *1 Other than above H () *1 Please use No.3 to access FX5CPU. External device Connecting station A Another station B Network No. 1 Relay station C Another station D Network No. n Multi-drop connecting station E Multi-drop connection Multi-drop connecting station F Multi-drop connecting station F Ethernet B D MELSEC iq-r series etc. Another station Another station No. 3 No. 2 No. 1 Ex. When specifying H as the requested multi-drop station number ASCII 3H 3H ed multi-drop station number Binary H ed multi-drop station number 3 MESSAGE FORMAT 3.1 Message Format 25

28 data length message Header Subheader network No. station No. module I/O No. Application data multidrop station No. data length Reserve Command data Specify the total data size from the reserve to the request data in hexadecimal. (Unit: byte) Ex. When the request data length is 24 (18H) bytes ASCII 1 8 3H 3H 31H 38H data length Binary 18H H data length Response data length Response message When normally completed, the total data size from the end to the response data is set in hexadecimal. When completed with error, the total data size from the end to the error information is set in hexadecimal. (Unit: byte) (When completed normally) Header Subheader network number station number module I/O number multi-drop station number Response data length End Response data (When completed with error) Header Subheader network number (access station) station number (access station) module I/O number multi-drop station number Response data length End network station Command number number multi-drop module I/O (responding (responding station station) station) number number Error information 26 3 MESSAGE FORMAT 3.1 Message Format

29 Reserved message Header Subheader network No. station No. module I/O No. Application data multidrop station No. data length Reserve Command data Setting range: Set H (). 3 Ex. ASCII Binary 3H 3H 3H 3H H H End Response message Header Application data Subheader network No. station No. module I/O No. multidrop station No. Response data length End Response data The command processing result is stored. When normally completed, "" is stored. When completed with error, an error set at the request is stored. (For the set error and corresponding error contents, refer to manuals of the SLMP compatible device of the response station.) Ex. When completed When failed (for 4H) ASCII ASCII 4 3H 3H 3H 3H 3H 34H 3H 3H Binary Binary H H H 4H data message Header Subheader network No. station No. module I/O No. Application data multidrop station No. data length Reserve Command data Set a command to be executed and data for the argument of the subcommand. (Some commands and subcommands do not require the request data.) For details of the request data, refer to Page 44 Access. 3 MESSAGE FORMAT 3.1 Message Format 27

30 Response data Response message Header Subheader network No. station No. Application data module I/O No. multidrop station No. Response data length End Response data The processing result of the request data is stored. (Some commands do not return response messages.) For details of the response data, refer to Page 44 Access. Error information The request network number, request station number, request module I/O number, and request multi-drop station number of the station which responded with errors are stored. Numbers which differ from the requested station specified by the request message may be stored because the information of the station which responded with errors is stored. The command and the subcommand specified by the request message of the request data are stored. Transfer data in character area This section describes how to transfer bit device data and word device data and data alignment in the character area sent and received between the external equipment and the CPU module by using each command. The transfer data explained below is handled as the character area B for reading and monitoring and the character area C for writing, testing, and registering the monitor data are stored. Character area message Header Subheader network No. station No. module I/O No. Application data multidrop station No. data length Reserve Command data Character area A and C Response message Header Subheader network No. station No. Application data module I/O No. multidrop station No. Response data length End Response data Character area B 28 3 MESSAGE FORMAT 3.1 Message Format