Download  Print this page

Advertisement

MELSEC iQ-F
FX5 User's Manual (SLMP)

Advertisement

Table of Contents

   Summary of Contents for Mitsubishi Electric MELSEC iQ-F Series FX5

  • Page 1 MELSEC iQ-F FX5 User's Manual (SLMP)
  • Page 3: Safety Precautions

    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].
  • Page 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.
  • Page 5: Introduction

    • 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.
  • Page 6: Table Of Contents

    CONTENTS SAFETY PRECAUTIONS ..............1 INTRODUCTION .
  • Page 7 Lock ................. . . 91 Unlock .
  • Page 8: Relevant Manuals

    RELEVANT MANUALS User's manuals for the applicable modules Manual name <manual number> Description MELSEC iQ-F FX5 User's Manual (Startup) Performance specifications, procedures before operation, and troubleshooting of the <JY997D58201> CPU module. MELSEC iQ-F FX5U User's Manual (Hardware) Describes the details of hardware of the FX5U CPU module, including input/output <JY997D55301>...
  • Page 9: Terms

    TERMS 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 FX5 User’s Manual (Hardware). Terms Description ■Devices...
  • Page 10 Terms Description ■Software packages Engineering tool The product name of the software package for the MELSEC programmable controllers GX Works3 The product name of the software package, SWnDND-GXW3, for the MELSEC programmable controllers (The 'n' represents a version.) ■Manuals User's manual Generic term for separate manuals •...
  • Page 11: Chapter 1 Outline

    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 11 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.
  • Page 12: Features Of Slmp

    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 Request message Message format of SLMP...
  • Page 13: Chapter 2 Slmp Data Communication

    SLMP DATA COMMUNICATION This chapter describes the SLMP data communication by which the external equipment reads or writes data to a CPU module. 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.
  • Page 14: Access Range

    Access range 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. Connecting station External device Ethernet Assigned symbol...
  • Page 15: Access Timing Of The Cpu Module Side

    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 Response to a command Read/Write command (Response) (Command)
  • Page 16: Transfer Time

    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.
  • Page 17: Chapter 3 Message Format

    MESSAGE FORMAT This chapter describes the message data format, the data specification method, and limitations etc. when performing SLMP data communication using the 3E frame to the built-in Ethernet port. Frame type Built-in Ethernet port Remark 3E frame Communicable The message format is the same as the QnA compatible 3E frame Message Format This section describes the message format for each command when performing the data communication using the 3E frame.
  • Page 18: Message Format And Control Procedure

    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.
  • Page 19 ■When communicating data in binary code The text differs depending Application data on the function and whether the command 2 bytes ends normally or not. External equipment Subheader Text (command) Subheader Text (response) CPU module 2 bytes The text differs depending on the function.
  • Page 20 ■When communicating data in ASCII code • When data is read from a CPU module by external equipment External equipment CPU module (command message) Character area A Text (command) Request data area (Data name) (Example) 35H 30H 30H 30H 46H 46H 30H 33H 46H 46H 30H 30H...
  • Page 21 • When data is written from external equipment to a CPU module External equipment CPU module (command message) Character area C Text (command) Request data area (Data name) (Example) 35H 30H 30H 30H 46H 46H 30H 33H 46H 46H 30H 30H 30H 30H 32H 30H 30H 30H...
  • Page 22 ■When communicating data in binary code • When data is read from a CPU module by external equipment External equipment CPU module (command message) Character area A Text (command) Request data area (Data name) (Example) 50H 00H 00H FFH FFH 03H 00H 0CH 10H 00H ((Example) For 12 bytes)
  • Page 23 Subcommand Command Request destination Subcommand multi-drop station number Request destination module I/O number Command Request destination station number (responding station) Network number (responding station) Reserved End code End code other than 0H Request data length Response data length Request destination Response data length multi-drop station number Request destination...
  • Page 24: Application Data Specification Items

    Application data specification items This section describes the data contents and the specification method of common data items in the application data in each message when performing the data communication using the 3E frame. Request destination network number and request destination station number ■Request message Header Application data...
  • Page 25 When specifying 26 (1AH) as the station number n and 16 (10H) as the station number of station A ASCII code Binary code 1AH 10H Station number Network number Station number Network number Precautions The stations of network number 240 to 255 cannot be accessed. FX5CPU cannot perform multi-drop connection.
  • Page 26 When specifying the default processor (0005H) as the request destination module I/O number Binary code ASCII code 05H 00H Request destination Request destination module I/O No. module I/O No. Request destination multi-drop station number ■Request message Header Application data Subheader Request Request Request...
  • Page 27 Request data length ■Request message Header Application data Subheader Request Request Request Request Request Reserve Command Subcommand Request destination destination destination data data destination network station No. module I/O multidrop length station No. Specify the total data size from the reserve to the request data in hexadecimal. (Unit: byte) When the request data length is 24 (18H) bytes ASCII code Binary code...
  • Page 28 Reserved ■Request message Header Application data Subheader Request Request Request Request Request Reserve Command Subcommand Request destination destination destination destination data data network station No. module I/O multidrop length station No. Setting range: • Set 0000H (0). ASCII code Binary code 00H 00H End code ■Response message...
  • Page 29: Transfer Data In Character Area

    Response data ■Response message Header Application data Subheader Request Request Request Request Response Response destination destination destination destination data length code data network station No. module I/O multidrop station No. 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 43 Device Access.
  • Page 30 Communicating data (when communicating in ASCII code) ■When bit device memory is read or written The bit device memory is handled in 1-bit (1-point) units or in 1-word (16-point) units. The transfer data in each case is described below. • In 1-bit (1-point) units When the bit device memory is handled in 1-bit (1-point) units, a specified number of devices starting from the specified start device are expressed in turn from the left end in "1 (31H)"...
  • Page 31 ■When word device memory is read or written In the case of word device memory, one word is expressed in 4-bit units in turn from the most significant bit in hexadecimal. When indicating the contents stored in the data registers D350 and D351 Device Number of Head device No.
  • Page 32 Communicating data (When communicating data in binary code) ■When bit device memory is read or written The bit device memory is handled in 1-bit (1-point) units or in 1-word (16-point) units. The transfer data in each case is described below. •...
  • Page 33 ■When word device memory is read or written In the word device memory, one word is specified by 16-bit and a specified number of devices starting from specified start device are expressed in 1-point units in turn from Low byte (L: bit 0 to 7) to High byte (H: bit 8 to 15). When indicating the contents stored in the data registers D350 and D351 Head Number...
  • Page 34: Character Areas

    Character areas This section explains character areas in the control procedure (data area when communicating in binary code). • Character areas differ depending on command to be used and contents to be specified. This section explains the data common to the character area when the device memory to be read or written is specified directly. •...
  • Page 35 Data of data area (when communicating in binary code) ■In the case of reading Data area (corresponding to character area A) External equipment Data area (corresponding to character area B) CPU module ■In the case of writing Data area (corresponding to character area C) External equipment CPU module...
  • Page 36 When communicating data in ASCII code The value 0000H(0), or the following value, is converted to a 4 digit (hexadecimal) ASCII code and sequentially transmitted beginning from the most significant digit ("0"). When communicating data in binary code The value 0000H, or the following 2-byte value, is used for transmission. The following figure shows the specification contents of the subcommand.
  • Page 37 ■Head device No. (device No.) Data for specifying the number of the device to read data from or write data to. When specifying continuous device areas, specify the head number of the device range. The head device number is specified by the data expression (decimal or hexadecimal) shown in the "Device number" column of the table shown in Page 44 Device range according to the corresponding device.
  • Page 38 When communicating data in binary code Use numerical values in 2 bytes which indicate the number of points to be processed, and send them in order from the lower byte to the upper byte. In the case of 5 points and 20 points 5 points 20 points 05H 00H...
  • Page 39 ■Device memory extension specification (subcommand: bit7) For details, refer to Page 94 Device Memory Extension Specification. This section explains how to read or write from/to a device to/from module access device areas and how to specify a device indirectly by using index register. Message format Response messages are extended as well.
  • Page 40 Module access device specification The following shows the approach for module access device specification in programming and request data. Extension Device Head device No. specification code or device No. Extension specification Specify the module number of intelligent function modules. ASCII code Binary code Specify the start I/O number in hexadecimal (3-digit ASCII code).
  • Page 41: Chapter 4 Commands

    COMMANDS This chapter explains commands of SLMP. For parts of the transmission message other than the command part, refer to Page 15 MESSAGE FORMAT List of Commands and Functions This section describes commands and functions when accessing from the external equipment to the CPU module. Name Command Sub-...
  • Page 42 Name Command Sub- Processing content Number of points commands processed per communication Device Read 0403H 0080H This command reads data from the buffer memory in intelligent ASCII: Random function modules and SLMP-compatible devices in units of 1 word (16 (Word access points + double- word access points) 4 192 bits).
  • Page 43 Name Command Sub- Processing content Number of points commands processed per communication Device Read 0406H 0080H With n points of buffer memory in intelligent function modules and ASCII: Block SLMP-compatible devices as 1 block, this command reads data by (Number of word device blocks randomly specifying multiple blocks.
  • Page 44 Name Command Sub- Processing content Number of points commands processed per communication Device Write 1406H 0082H With n points of buffer memory in intelligent function modules and ASCII: Block SLMP-compatible devices as 1 block, this command writes data by (Number of word device blocks randomly specifying multiple blocks.
  • Page 45: Device Access

    Device Access This section explains the control procedure specification method and shows a specification example when the device memory is read and written. Commands This section explains commands when the device memory is read or written. Commands Function Command Processing content CPU module status (Subcommand) STOP RUN...
  • Page 46: Device Range

    Device range This section shows accessible CPU module device. Specify the device and device number range that exist in the module targeted for data read or write. In the case of FX5CPU Classification Device Type Device code Device No. Applicable (Device specification format: FX5CPU Long)
  • Page 47 Classification Device Type Device code Device No. Applicable (Device specification format: FX5CPU Long) device ASCII code Binary code   Internal user Long counter Contact Specify in the range of Decimal device (LCS*) (5500H) device numbers of the module to access. ...
  • Page 48: Device Read (batch)

    Device Read (Batch) Data in devices are read in a batch. Request data ■When communicating data in ASCII code 2 digit code/6 digit number specification 4 bytes 4 bytes 2 bytes 6 bytes 4 bytes When extension is Device Subcommand Head device No.
  • Page 49 ■Subcommand Specify the subcommand selected from the item. Item Subcommand Data size Device specification Device memory ASCII code Binary code specification format extension (Upper column: characters, lower column: specification character code) Bit units 2 digit code/6 digit number Not specified specification Specified 4 digit code/8 digit number...
  • Page 50 • When communicating data in binary code (Request data) Device code Subcommand Number Head of devices device No. 01H 04H 01H 00H 64H 00H 00H 90H 08H 00H (Response data) 0 = OFF 1 = ON 00H 01H 00H 11H M107 M106 M101...
  • Page 51 ■When reading data in word units (word device) Values in T100 to T102 are read. It is supposed that 4660(1234H) is stored in T100, 2(2H) is stored in T101, and 7663(1DEFH) is stored T102. • When communicating data in ASCII code (Request data) Device Subcommand...
  • Page 52: Device Write (batch)

    Device Write (Batch) Data in devices are written in a batch. Request data ■When communicating data in ASCII code 2 digit code/6 digit number specification 4 bytes 4 bytes 2 bytes 6 bytes 4 bytes When extension Number Device Write data for the Subcommand Head device No.
  • Page 53 ■Subcommand Specify the subcommand selected from the item. Item Subcommand Data size Device specification Device memory ASCII code Binary code specification format extension (Upper column: characters, lower column: specification character code) Bit units 2 digit code/6 digit number Not specified specification Specified 4 digit code/8 digit number...
  • Page 54 • When communicating data in binary code (Request data) Device Subcommand code Number Head Write data device No. of devices 0 = OFF 01H 14H 01H 00H 64H 00H 00H 90H 08H 00H 11H 00H 11H 00H 1 = ON M107 M106 M101...
  • Page 55: Device Read Random

    Device Read Random This command specifies the device No. randomly and reads the device value. Request data ■When communicating data in ASCII code Specify the devices for the specified number of points. 2 digit code/6 digit number specification 4 bytes 4 bytes 2 bytes 2 bytes When...
  • Page 56 ■When communicating data in binary code 2 digit code/6 digit number Specify the devices for the specified number of points. specification 2 bytes 2 bytes 1 byte 1 byte When Word access Double-word access Double- Word extension word access Subcommand Device Device Device...
  • Page 57 ■Device code, device No. Specify the target device of reading. Item Description Word access Specify the device points specified as word access points. The specification is not necessary when the word access points are zero. Double-word access Specify the device points specified as double-word access points. The specification is not necessary when the double-word access points are zero.
  • Page 58 • Response data Word access Word access Word access Word access read data 1 read data 2 read data 3 read data 4 39H 39H 35H 31H 32H 30H 30H 33H 30H 34H 38H 34H M115 M100 D1501 D1500 Y17F Y160 M1142 M1111...
  • Page 59 • Response data Word Word Word Word Double-word Double-word Double-word access access access access access access access read read read read read data 1 read data 2 read data 3 data 1 data 2 data 3 data 4 95H 19H 02H 12H 30H 20H 49H 48H 4EH 4FH 54H 4CH AFH B9H DEH C3H B7H BCH DDH BAH M115 D1500 D1501 Y17F...
  • Page 60: Device Write Random

    Device Write Random This command specifies the device No. randomly and writes the data. Request data ■When writing data in bit units • When communicating data in ASCII code Specify the devices for the specified number of points. 2 digit code/6 digit number specification 4 bytes 4 bytes 2 bytes...
  • Page 61 • When communicating data in binary code 2 digit code/6 digit number Specify the devices for the specified number of points. specification 2 bytes 2 bytes 1 byte When extension Device Set or Device Set or access Device No. Device No. is not code reset...
  • Page 62 ■When writing data in word units • When communicating data in ASCII code Specify the devices for the specified number of points. 2 digit code/6 digit number specification 4 bytes 4 bytes 2 bytes 2 bytes When Word access Double- Word extension word...
  • Page 63 • When communicating data in binary code 2 digit code/6 digit number Specify the devices for the specified number of points. specification 2 bytes 2 bytes 1 byte 1 byte Word access Double-word access Double- When Word word access extension is Device Write Device...
  • Page 64 Item Description Number of points ASCII code Binary code 1  (word access points  12 + 1  word access points  12 + Word access points Specify the number of points to be accessed in one- double-word access points  14)  double-word access points ...
  • Page 65 ■When writing data in word units Write the value in a device as follows. Item Target device Word access D0, D1, M100 to M115, X20 to X2F Double-word access D1500 to D1501, Y160 to Y17F, M1111 to M1142 • When communicating data in ASCII code (Request data) Word Double-word...
  • Page 66 • When communicating data in binary code (Request data) Word Double-word access access points points Subcommand 02H 14H 00H 00H Device Write Device Write Data 1 Data 2 Device No. Device No. code data code data 00H 00H 00H A8H 50H 05H 01H 00H 00H A8H 75H 05H 64H 00H 00H 90H 40H 05H 20H 00H 00H 9CH 83H 05H Data 3 Data 4 DCH 05H 00H A8H 02H 12H 39H 04H 60H 01H 00H 9DH 07H 26H 75H 23H 57H 04H 00H 90H 75H 04H 25H 04H...
  • Page 67: Device Read Block

    Device Read Block The examples shown in this section explain the control procedure for reading by randomly specifying multiple blocks, where 1 block consists of n point(s) of a bit device memory (one point is specified by 16-bit) and a word device memory (one point is specified by 1-word).
  • Page 68 Contents of the character areas during device read block This section explains what is in the character area when a device read block function is performed. ■Number of word device blocks and number of bit device blocks This data is for specifying the number of word device blocks or bit device blocks to be sent directly after this data field in the batch read to the word device or bit device, respectively.
  • Page 69 ■Device code This data is for identifying the head device memory for each block for which batch read is performed. The device code for each device is shown in Page 44 Device range. The double word device and the long index register (LZ) are not supported. •...
  • Page 70 Request data ■When communicating data in ASCII code 2 digit code/6 digit number specification Specify the devices for the specified number of points. 4 bytes 4 bytes 2 bytes 2 bytes When Number of Number of 1st word device in the nth block extension is word device bit device...
  • Page 71 ■When communicating data in binary code Specify the devices for the specified number of points. 2 digit code/6 digit number specification 2 bytes 2 bytes 1 byte 1 byte When 1st word device in the nth block Last bit device in the mth block Number of Number of extension is...
  • Page 72 Device code, device No., number of device points Specify the device points while satisfying the following conditions: Total number of points for all word device blocks + total number of points for all bit device blocks  960 Item Description Word device Specify the device points specified in "Number of word device blocks".
  • Page 73 (Response data) 1st block data of the 2nd block data of the specified word device specified word device 30H 30H 38H 32H 30H 33H 35H 34H 35H 32H 38H 30H 39H 37H 30H 30H 31H 33H W100 W107 M143 M128 M159 M144 B10F B100 B11F B110 B12F...
  • Page 74: Device Write Block

    Device Write Block The examples shown in this section explain the control procedure for writing by randomly specifying multiple blocks, where 1 block consists of n point(s) of a bit device memory (one point is specified by 16-bit) and a word device memory (one point is specified by 1-word).
  • Page 75 ■When communicating data in binary code (Request data) (Data name) - - - - - - External equipment L H L H L - H L - H Specify the target device Specify the target device to be written. (1st block) to be written.
  • Page 76 ■Word device number and bit device number This data is for specifying the head word device or bit device for each block to which batch write is performed, where continuous word or bit devices are considered one block. • When communicating data in ASCII code The head device number of each block is converted to 6-digit ASCII code and sent.
  • Page 77 The extension specification is allowed for the device memory being written to using the device write block functions. Request data ■When communicating data in ASCII code Specify the devices for the specified number of points. 2 digit code/6 digit number specification 4 bytes 4 bytes 2 bytes 2 bytes...
  • Page 78 ■When communicating data in binary code 2 digit code/6 digit number Specify the devices for the specified number of points. specification 2 bytes 2 bytes 1 byte 1 byte When 1st word device in the nth block Last bit device in the mth block Number of Number of extension...
  • Page 79 Number of word device blocks and number of bit device blocks Specify the number of blocks of the device to be write in hexadecimal. Item Description Number of points ASCII code Binary code Number of word device blocks Specify the number of blocks of the word device to (Number of word device blocks + Number of word device blocks + number of bit device blocks) 2...
  • Page 80 Communication example Write values from devices as follows. Item Write contents Word device • Block 1: D0 to D3 (4 points) • Block 2: W100 to W107 (8 points) Bit device • Block 1: M0 to M31 (2 points) • Block 2: M128 to M159 (2 points) •...
  • Page 81 ■When communicating data in binary code (Request data) Number of word device Number of bit device blocks blocks Subcommand 06H 14H 00H 00H 02H 03H Device Device Number of Device Device Number of Write data Write data code devices code devices 00H 00H 00H A8H 04H 00H 08H 00H 00H 28H 00H 01H 00H B4H 08H 00H 70H 09H...
  • Page 82: Remote Control

    Remote Control This section describes the command to set the SLMP compatible device or CPU module to the RUN status or STOP status by a message from the external device. Before the remote operation When the accessed device or module is turned from off to on or the system is reset after the remote operation The information about the remote operation will be deleted.
  • Page 83 ■Mode This mode specifies whether Remote RUN can be executed forcibly by a device other than the external device which performed Remote STOP or Remote PAUSE. If forced execution is not allowed, Remote RUN can be executed only by the external device which performed Remote STOP or Remote PAUSE.
  • Page 84: Remote Stop

    Remote STOP This command executes Remote STOP to the access destination module. Request data ■When communicating data in ASCII code 4 bytes 4 bytes 4 bytes Subcommand 30H 30H 30H ■When communicating data in binary code 2 bytes 2 bytes 2 bytes Subcommand 10H 00H 00H...
  • Page 85: Remote Latch Clear

    ■Mode This mode specifies whether Remote PAUSE can be executed forcibly by a device other than the external device which performed Remote STOP or Remote PAUSE. If forced execution is not allowed, Remote PAUSE can be executed only by the external device which performed Remote STOP or Remote PAUSE.
  • Page 86: Remote Reset

    ■When communicating data in binary code 2 bytes 2 bytes 2 bytes Subcommand 10H 00H 00H Response data There is no response data for remote latch clear command. Communication example Send request messages from the external device by using the message format shown in the request data above. Remote RESET This command executes Remote RESET to the access destination module.
  • Page 87: Processor Type Read

    Processor type read This command reads the processor module name code (processor type) of the access destination module. Request data ■When communicating data in ASCII code 4 bytes 4 bytes Subcommand 00H 00H 00H ■When communicating data in binary code 2 bytes 2 bytes Subcommand...
  • Page 88 The model of the CPU module is identified by the model code. Communication example ■When communicating data in ASCII code (Request data) 30H 31H 30H 31H 30H 30H 30H 30H (Response data) 46H 58H 35H 55H 2DH 33H 32H 4DH 52H 2FH 45H 53H 20H 20H 20H 20H 34H 41H 32H 31H ■When communicating data in binary code (Request data)
  • Page 89: Clear Error

    Clear Error This function turns off ERR LED of the FX5CPU from the external equipment and/or initializes the communication error information or error code stored in the buffer memory. This function is used to initialize the current error information due to an abnormal response for a command message and return it to the normal state or initialize the error code storage area of the buffer memory.
  • Page 90: Self-test

    Self-Test This function tests whether the communication function between the external equipment and FX5CPU operates normally or not. The control procedure when this function is used is described with examples. • At the startup of the FX5CPU or when trouble occurs, this function can check whether the connection between the external equipment and FX5CPU is correct and/or whether the data communication function operates normally.
  • Page 91 Communication example Send request messages from the external device by using the message format shown in the request data (Page 88). ■When executing the Self-Test by communicating in ASCII code (Request data) Number of Command Subcommand loopback data Loopback data 30H 36H 31H 39H 30H 30H 30H 30H 30H 30H 31H 32H...
  • Page 92: Remote Password Unlock Or Lock

    Remote Password Unlock or Lock This function prevents illegal access from a user who is not allowed to operate the SLMP compatible device. If a remote password is set to the SLMP compatible device, the remote password is checked when the SLMP compatible device is accessed.
  • Page 93: Lock

    • When the FX5CPU communicating data is set with a remote password, communication is enabled after the completion of the unlock process until the lock process. • All commands received while the remote password is in locked status will generate an error response. (Execute communication after executing the remote password unlock process.) •...
  • Page 94: Unlock

    Communication example ■When performing the lock process in communication using ASCII code Remote Command Subcommand password length Remote password 36H 33H 31H 30H 30H 30H 30H 31H 41H 61H 62H 63H 66H 67H 68H 69H 6AH 6BH 6EH 6FH 70H 71C 72H 73H 76H 77H 78H 79H 7AH...
  • Page 95 ■Remote password length Specify the remote password length. The password length is the specified characters (6 to 32 characters). Item Remote password length (when the number of remote password characters is 32) ASCII code Binary code   6 to 32 characters Characters Character code ■Remote password...
  • Page 96: Appendix

    APPENDIX Appendix 1 Device Memory Extension Specification The following accesses are available by setting the subcommand of request data to 008. • Access to module access device • Access with indirect specification of the device No. by using index register or long index register •...
  • Page 97 ■Command The following commands can be used for accessing. Item Command Type Operation Device Read 0401 Write 1401 Read Random 0403 Write Random 1402 Read Block 0406 Write Block 1406 ■Subcommand Subcommand ASCII code Binary code 80H 00H 82H 00H ■Extension specification Specify the module number of intelligent function modules.
  • Page 98 ■Head device or device No. Specify the head device or device No. in decimal, with the same format as the message when extension is not specified. Indirect specification of the access target device No. can be performed by using the CPU module index register (Z) or long index register (LZ).
  • Page 99: Access With Indirect Specification Of The Device No. By Using Index Register Or Long Index Register

    Access with indirect specification of the device No. by using index register or long index register Indirect specification of the device No. can be performed by using the index register or long index register when accessing the device. The access destination can be switched with one message, by changing the value of the index register or long index register in CPU module programs.
  • Page 100 Request data ASCII Device Head device No. When extension is Command Subcommand Number of devices code or device No. not specified Extension Extension Device Head device No. Device specification When extension is specified specification code or device No. modification modification Binary When extension is Head device No.
  • Page 101 ■Command The following commands can be used for accessing. Item Command Type Operation Device Read Random 0403 Write Random 1402 ■Subcommand Item Subcommand ASCII code Binary code When accessing in bit units 81H 00H 83H 00H When accessing in word units 80H 00H 82H 00H ■Extension specification...
  • Page 102 • The following value is specified when the access point is a module of the MELSEC Q/L Series. ASCII code Binary code Specify the number of the index register in decimal (2-digit ASCII code). Specify the number of the index register in hexadecimal. (Specification range: (Specification range: 0 to 15) 0 to F) H 40H...
  • Page 103: Access With Indirect Specification Of The Device No. By Using The Values Stored In Word Device

    ■Direct memory specification (only when communicating in binary code) Specify the device type when accessing the module access device. Item Binary code Module access device Specify F8H. Other than the above Specify 00H. Response data The same as when extension is not specified. Communication example Accessing the device of D100 + Z4.
  • Page 104 Request data ASCII Device Head device No. Command Subcommand Number of devices code or device No. Device Head device No. Device Indirect When extension is specified code or device No. modification specification Binary When extension is Head device No. Device Number of Command Subcommand...
  • Page 105 ■Indirect specification, Device modification Specify the "@" part of the indirect specification device. Indirect specification can be specified only for word devices. When communicating data in ASCII code When communicating data in binary code : Without indirect specification : With indirect specification ■Device code (Only word device codes can be specified at indirect specification) Specify the code of the device to be accessed.
  • Page 106: Appendix 2 Command Comparison Between Mc Protocol And Slmp

    Appendix 2 Command Comparison between MC Protocol and SLMP The message format of 3E frame of the SLMP is the same as that of the QnA compatible 3E frame of MC protocol. The correspondence table of MC protocol and SLMP is shown below. When connecting an external device which uses MC protocol to a SLMP compatible device, check if replacement of command is required.
  • Page 107: Appendix 3 Cpu Module Processing Time Of Slmp

    Appendix 3 CPU Module Processing Time of SLMP When accessing the CPU module from an external device using SLMP communication, the following "intervention time to the scan time" and "number of scans for processing" of the CPU module side are required. On the request from the external device using SLMP communication, the CPU module processes a specified number of points during each END processing in case the CPU module is running.
  • Page 108: Index

    INDEX 0 to 9 ......11 3E frame ......16 Application data .
  • Page 109 MEMO...
  • Page 110: Revisions

    Data code of ASCII 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 111: Warranty

    WARRANTY Please confirm the following product warranty details before using this product. Gratis Warranty Term and Gratis Warranty 2. Onerous repair term after discontinuation of production Range If any faults or defects (hereinafter "Failure") found to Mitsubishi shall accept onerous product repairs for be the responsibility of Mitsubishi occurs during use of seven (7) years after production of the product is the product within the gratis warranty term, the...
  • Page 112: Trademarks

    TRADEMARKS   Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Ethernet is a trademark of Xerox Corporation. The company name and the product name to be described in this manual are the registered trademarks or trademarks of each company.
  • Page 114 Manual number: JY997D56001B Model: FX5-U-SL-E Model code: 09R541 When exported from Japan, this manual does not require application to the Ministry of Economy, Trade and Industry for service transaction permission. HEAD OFFICE: TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN HIMEJI WORKS: 840, CHIYODA MACHI, HIMEJI, JAPAN Specifications are subject to change without notice.

Comments to this Manuals

Symbols: 0
Latest comments: