Page 1 Machine Controller MP3000 Series Communications USER'S MANUAL Outline of Communications Ethernet Communications MANUAL NO. SIEP C880725 12B...
Page 2 Yaskawa. No patent liabil- ity is assumed with respect to the use of the information contained herein. Moreover, because Yaskawa is constantly striving to improve its high-quality products, the informa- tion contained in this manual is subject to change without notice.
Page 3 Using this Manual  Basic Terms Unless otherwise specified, the following definitions are used: • MP3000: A Machine Controller in the MP3000 Series • MPE720: The Engineering Tool or a personal computer running the Engineering Tool • PLC: A Programmable Logic Controller ...
Page 4 Series Machine Controller System SIEP C880725 00 Machine Controller, from installation and Setup Manual connections to settings, programming, trial operation, and debugging. Machine Controller MP3000 Series Describes troubleshooting an MP3000- MP3200/MP3300 SIEP C880725 01 series Machine Controller. Basic func- Troubleshooting Manual...
Page 5 Continued from previous page. Function Manual Name Manual Number Contents MPE720 Version 7 System Integrated Engineering Engineering Tool for MP2000/MP3000 Describes how to operate MPE720 ver- SIEP C880761 03 Tool Series Machine Controller sion 7. User’s Manual Safety Precautions The following signal words and marks are used to indicate safety precautions in this manual. Information marked as shown below is important for safety.
Page 6  General Precautions WARNING • The installation must be suitable and it must be performed only by an experienced technician. There is a risk of electrical shock or injury. • Before connecting the machine and starting operation, make sure that an emergency stop pro- cedure has been provided and is working correctly.
Page 7  Installation CAUTION • Do not install the Machine Controller in any of the following locations. • Locations that are subject to direct sunlight • Locations that are subject to ambient temperatures that exceed the operating conditions • Locations that are subject to ambient humidity that exceeds the operating conditions •...
Page 8 MP3000 Series CPU Unit Instructions (Manual No.: TOBP C880725 16) MP3000 Series MP3300 CPU Module Instructions (Manual No.: TOBP C880725 23) If the power supply to the CPU Unit/CPU Module is turned ON after the external power supply, e.g., the 24-V I/O power supply, the outputs from the CPU Unit/CPU Module may momentarily turn ON when the power supply to the CPU Unit/CPU Module turns ON.
Page 9  Operation CAUTION • Follow the procedures and instructions in the user’s manuals for the relevant Machine Control- lers to perform normal operation and trial operation. Operating mistakes while the Servomotor and machine are connected may damage the machine or even cause accidents resulting in injury or death.
Page 10 • The illustrations that are presented in this manual are typical examples and may not match the product you received. • If the manual must be ordered due to loss or damage, inform your nearest Yaskawa representa- tive or one of the offices listed on the back of this manual.
Page 11 • Events for which Yaskawa is not responsible, such as natural or human-made disasters  Limitations of Liability • Yaskawa shall in no event be responsible for any damage or loss of opportunity to the customer that arises due to failure of the delivered product.
Page 12 • The customer must confirm that the Yaskawa product is suitable for the systems, machines, and equipment used by the customer. • Consult with Yaskawa to determine whether use in the following applications is acceptable. If use in the application is acceptable, use the product with extra allowance in ratings and specifications, and provide safety measures to minimize hazards in the event of failure.
Page 13: Table Of Contents
Contents About this Manual............iii Using this Manual.
Page 14 Communications with an OMRON PLC (FINS Communications Service) . 2-186 Using Automatic Reception with the MP3000 as a Slave ..... . . 2-186 Using the MSG-RCVE Function with the MP3000 as a Slave .
Page 15 Outline of Communications This chapter describes the communications of the MP3000 Con- troller. Overview ....... 1-2 System Configuration Examples .
Page 16: Overview
1.1 Overview Overview The MP3000 Controller provides engineering communications (used to connect to the MPE720) and addi- tional support for an Ethernet connection to host devices. The following table describes the communication features. Function Features Description The MP3000 Controller supports multiple •...
Page 17: System Configuration Examples
1.2 System Configuration Examples Configuration with the MP3200 System Configuration Examples Configuration with the MP3200 The following figure shows a typical system configuration. MPE720 Integrated Engineering Tool Version 7 Host PLC Ethernet Ethernet MP3200 24-VDC power supply, AC power supply, or status monitoring device 24-VDC power supply or...
Page 18: Configuration With The Mp3300
1.2 System Configuration Examples Configuration with the MP3300 Configuration with the MP3300 MPE720 Integrated Engineering Tool Version 7 Host PLC MP3300 24-VDC power supply, AC power supply, or status monitoring device 24-VDC power supply or AC power supply MECHATROLINK-III Reference-type SERVOPACK with MECHATROLINK-III Communications I/O Module with MECHATROLINK-III...
Page 19: Overview
Ethernet Communications This chapter describes the Ethernet communications of the MP3000-series Controller. Overview ....... 2-4 Ethernet Communications .
Page 20 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) 2-139 Using I/O Message Communications with the MP3000 as the Master ......2-139 Using the MSG-SNDE Function with the MP3000 as the Master .
Page 21 2.15 Using Message Functions ....2-359 Function Codes ....... . . 2-359 Using Function Codes .
Page 22: Ethernet Communications
Ethernet communications can be used for message communications and engineering communications. The MP3000-series Controller supports the following communications protocols. Protocol Description Master/Slave MEMOBUS Yaskawa’s standard MEMOBUS protocol. Master/Slave Extended MEMOBUS Yaskawa’s extended MEMOBUS protocol. Master/Slave A-compatible 1E frame A protocol for Mitsubishi PLCs.
Page 23: Communications Specifications
2.1 Overview Communications Specifications Communications Specifications The following table lists the communications specifications of the MP3000-series Controller. Item Specification Remarks − Abbreviation 218IFD − Communications Interface 10Base-T or 100Base-TX Com- Number of Communications Ports 2-port hub (Connectors) Items − Communications Protocols TCP, UDP, IP, ARP, or ICMP Maximum Number of Communications 20 + 2 (I/O message communica-...
Page 24: Detail Definition Setting Procedures
2.2 Detail Definition Setting Procedures Displaying the 218IFD Detail Definition Dialog Box Detail Definition Setting Procedures The 218IFD Detail Definition Dialog Box is used to make detailed definitions for Ethernet communica- tions. Displaying the 218IFD Detail Definition Dialog Box Follow these steps to display the 218IFD Detail Definition Dialog Box. Open the Module Configuration Definition Tab Page.
Page 25: 218Ifd Detail Definition Dialog Box Details
2.2 Detail Definition Setting Procedures 218IFD Detail Definition Dialog Box Details Items 1 and 2 display the configuration information for the 218IFD Function Module. This is the same configuration information that appears in the Module Configuration Definition Tab Page.  Circuit No. The circuit number of the Ethernet port on the 218IFD is displayed here.
Page 26 2.2 Detail Definition Setting Procedures 218IFD Detail Definition Dialog Box Details  Display Items The following table lists the items that are displayed on the Transmission Parameters Tab Page. For the valid setting ranges and setting precautions, refer to the descriptions of the items on the following pages.
Page 27 2.2 Detail Definition Setting Procedures 218IFD Detail Definition Dialog Box Details  Gateway IP Address Enter the IP address of the gateway. If a gateway is not being used, enter 0 in fields 1 to 4 for the gateway IP address. The data input range for the gateway IP address depends on the field as shown below.
Page 28 2.2 Detail Definition Setting Procedures 218IFD Detail Definition Dialog Box Details Response Time Enter the time (between 0 and 255) to wait for a response after sending a command using the MSG-SNDE function. If a response is not returned, causing a timeout, the transmission will be retried as many times as set in the Count of Retry Box.
Page 29 The following table lists the protocols. Refer to the following section for details on the protocols. 2.1 Overview (page 2-4) Protocol Description MEMOBUS Yaskawa’s standard MEMOBUS protocol. Extended MEMOBUS Yaskawa’s extended MEMOBUS protocol. A-compatible 1E frame A protocol for Mitsubishi PLCs. QnA-compatible 3E frame A protocol for Mitsubishi PLCs.
Page 30 2.2 Detail Definition Setting Procedures 218IFD Detail Definition Dialog Box Details Connections A connection is a series of operations to confirm communications and transfer data in one-to-one com- munications between a local station program and a remote station program. Terms Port Numbers A port number is used to identify the target program in the remote station.
Page 31 2.2 Detail Definition Setting Procedures 218IFD Detail Definition Dialog Box Details Detail This button displays the Detail Setting Dialog Box to set the automatic reception settings. If the FINS protocol is selected, set the local station for the FINS protocol. Item Setting Range Description...
Page 32 2.2 Detail Definition Setting Procedures 218IFD Detail Definition Dialog Box Details Continued from previous page. Item Setting Range Description Default Write-in width Sets the low end of the range for writ- MW00000 to of Coil/Hold ing hold registers (coils) that are used MW00000 MW1048576 Register, LO...
Page 33 2.2 Detail Definition Setting Procedures 218IFD Detail Definition Dialog Box Details Status Tab Page The Status Tab Page displays the communications status and detail definition settings for the 218IFD. The settings cannot be changed.       ...
Page 34 2.2 Detail Definition Setting Procedures 218IFD Detail Definition Dialog Box Details Status Display Description Remarks − No error Normal Socket Creation Error System error A socket could not be created. Binding error (port number duplication) When a MSG function was aborted, a binding error occurred during discon- Setting error in local station port nection.
Page 35 2.2 Detail Definition Setting Procedures 218IFD Detail Definition Dialog Box Details  Response Time The time (ms) that was required to receive a response for a command that was sent using the MSG-SNDE function is displayed.  Connection Type The connect type (TCP or UDP) that is set in the connection parameters on the Transmission Parameters Tab Page is displayed here.
Page 36: Communications Protocols
2.3 Communications Protocols Communications Protocols The following table lists the communications protocols according to the remote device and purpose. Communications Interface Function Communi- Remote used by cations Reference Device Master Slave Protocol MP3000 Automatic Using Automatic Reception with the reception MP3000 as a Slave (page 2-20) Other MP-series...
Page 37 2.3 Communications Protocols Continued from previous page. Communications Interface Function Communi- Remote used by cations Reference Device Master Slave Protocol MP3000 Automatic Using Automatic Reception with the reception MP3000 as a Slave (page 2-262) JTEKT PLCs MP3000 MSG- Using the MSG-RCVE Function with the RCVE JTEKT PLCs TOYOPUC MP3000 as a Slave (page 2-270)
Page 38: Communications With Mp-Series Controllers
Using Automatic Reception with the MP3000 as a Slave This section describes how to communicate with the MP2300 by using automatic reception. MP3000 MP2300 (local station) (remote station) 218IF-01 MP2300 YASKAWA STRX STOP INIT TEST CNFG TEST PORT OFF ON...
Page 39 MP2300 master are written to the MW00000 to MW00099 hold registers in the MP3000 slave. MP3000 MP2300 (local station) (remote station) IP address: 192.168.001.002 IP address: 192.168.001.001 218IF-01 MP2300 YASKAWA STRX STOP INIT TEST CNFG TEST PORT OFF ON Master...
Page 40 2.4 Communications with MP-series Controllers Using Automatic Reception with the MP3000 as a Slave MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 41 2.4 Communications with MP-series Controllers Using Automatic Reception with the MP3000 as a Slave Set the connection parameters.        Select 1 in the Connect No. Box. Enter “10001” in the Port No. Box for the MP-series Controller. Select Extended MEMOBUS in the Communications Protocol Type Box, and then click the Default Button.
Page 42 2.4 Communications with MP-series Controllers Using Automatic Reception with the MP3000 as a Slave Check the settings and double-click the Setting Button in the Detail Column. Select the Enable Option on the Automatically Reception Tab Page and then click the OK Button. Note: 1.
Page 43 2.4 Communications with MP-series Controllers Using Automatic Reception with the MP3000 as a Slave  Setting Up the Other Device (MP2300) to Connect Use the following procedure to set up the MP2300. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IF in the Module Details Area of the Module Configuration Definition Tab Page.
Page 44 2.4 Communications with MP-series Controllers Using Automatic Reception with the MP3000 as a Slave Set the connection parameters.       Enter “10001” in the Local Port Box. Enter the following address in the Node IP Address Boxes: 192.168.001.001. Enter “10001”...
Page 45 2.4 Communications with MP-series Controllers Using Automatic Reception with the MP3000 as a Slave Create a ladder program for the MSG-SND function. A ladder program example is shown below. 2-27...
Page 46 2.4 Communications with MP-series Controllers Using Automatic Reception with the MP3000 as a Slave 2-28...
Page 47 2.4 Communications with MP-series Controllers Using Automatic Reception with the MP3000 as a Slave Save the data to flash memory. This concludes the setup.  Starting Communications Turn ON the power to the MP3000 to start receiving messages. The system will automatically start the message reception operation. No further operation is required. Turn ON the Execute Bit (e.g., DB000200) for the MSG-SND function in the MP2300 to start sending messages.
Page 48: Using The Msg-Rcve Function With The Mp3000 As A Slave
You can use the MSG-RCVE function together with automatic reception by maintaining a separate con- nection. This section describes how to communicate with an MP2300-series Controller by using the MSG-RCVE function. MP3000 MP2300 (local station) (remote station) 218IF-01 MP2300 YASKAWA STRX STOP INIT TEST CNFG TEST PORT OFF ON Slave...
Page 49 MP2300 master are written to the MW00100 to MW00199 hold registers in the MP3000 slave. MP3000 MP2300 (local station) (remote station) IP address: 192.168.001.001 IP address: 192.168.001.002 218IF-01 MP2300 YASKAWA STRX STOP INIT TEST CNFG TEST PORT OFF ON Master...
Page 50 2.4 Communications with MP-series Controllers Using the MSG-RCVE Function with the MP3000 as a Slave MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 51 2.4 Communications with MP-series Controllers Using the MSG-RCVE Function with the MP3000 as a Slave Set the connection parameters.        Select 2 in the Connect No. Box. Enter “10002” in the Port No. Box for the MP-series Controller. Select Extended MEMOBUS in the Communications Protocol Type Box, and then click the Default Button.
Page 52 2.4 Communications with MP-series Controllers Using the MSG-RCVE Function with the MP3000 as a Slave Check the settings and double-click the Setting Button in the Detail Column. Select the Disable Option on the Automatically Reception Tab Page and then click the OK But- ton.
Page 53 2.4 Communications with MP-series Controllers Using the MSG-RCVE Function with the MP3000 as a Slave Create a ladder program for the MSG-RCVE function. A ladder program example is shown below. 2-35...
Page 54 2.4 Communications with MP-series Controllers Using the MSG-RCVE Function with the MP3000 as a Slave Save the data to flash memory. This concludes the settings for using the MP3000 as a slave. 2-36...
Page 55 2.4 Communications with MP-series Controllers Using the MSG-RCVE Function with the MP3000 as a Slave  Setting Up the Other Device (MP2300) to Connect Use the following procedure to set up the MP2300. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IF in the Module Details Area of the Module Configuration Definition Tab Page.
Page 56 2.4 Communications with MP-series Controllers Using the MSG-RCVE Function with the MP3000 as a Slave Set the connection parameters.       Enter “10002” in the Local Port Box. Enter the following address in the Node IP Address Boxes: 192.168.001.001. Enter “10002”...
Page 57 2.4 Communications with MP-series Controllers Using the MSG-RCVE Function with the MP3000 as a Slave Create a ladder program for the MSG-SND function. A ladder program example is shown below. 2-39...
Page 58 2.4 Communications with MP-series Controllers Using the MSG-RCVE Function with the MP3000 as a Slave Save the data to flash memory. This concludes the setup. 2-40...
Page 59 2.4 Communications with MP-series Controllers Using the MSG-RCVE Function with the MP3000 as a Slave  Starting Communications Turn ON the power to the MP3000 to start receiving messages. In the ladder program example, message reception starts immediately after the system starts. No further operation is required.
Page 60: Using I/O Message Communications With The Mp3000 As The Master
Using I/O Message Communications with the MP3000 as the Master This section describes how to communicate with an MP2300-series Controller by using I/O message com- munications. MP3000 MP2300 (local station) (remote station) 218IF-01 MP2300 YASKAWA STRX STOP INIT TEST CNFG TEST PORT OFF ON Master...
Page 61 OW0064 to OW00C7 output registers in the MP3000 master are written to the MW00300 to MW00399 hold registers in the MP2000 slave. MP3000 MP2300 (local station) (remote station) IP address: 192.168.001.001 IP address: 192.168.001.002 218IF-01 MP2300 YASKAWA STRX STOP INIT TEST CNFG TEST PORT OFF ON Master...
Page 62 2.4 Communications with MP-series Controllers Using I/O Message Communications with the MP3000 as the Master  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 63 2.4 Communications with MP-series Controllers Using I/O Message Communications with the MP3000 as the Master Click the Easy setting Button. The Message Communications Easy Setting Dialog Box will be displayed. Set the connection parameters.       ...
Page 64 2.4 Communications with MP-series Controllers Using I/O Message Communications with the MP3000 as the Master Select Low in the Data update timing Box as the timing to update input and output data between the CPU Function Module and 218IFD. Note: The data update timing is the timing at which the CPU Function Module and 218IFD exchange data. Communications with the remote device are performed asynchronously.
Page 65 2.4 Communications with MP-series Controllers Using I/O Message Communications with the MP3000 as the Master  Setting Up the Other Device (MP2300) to Connect Use the following procedure to set up the MP2300. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IF in the Module Details Area of the Module Configuration Definition Tab Page.
Page 66 2.4 Communications with MP-series Controllers Using I/O Message Communications with the MP3000 as the Master Set the connection parameters.       Enter “10005” and “10006” in the Local Port Boxes. Enter the following address in the Node IP Address Boxes: 192.168.001.001. Enter “10005”...
Page 67 2.4 Communications with MP-series Controllers Using I/O Message Communications with the MP3000 as the Master Create a ladder program for the MSG-RCV function. A ladder program example is shown below. This ladder program example is for receiving the read request. Ladder programming for receiving the write request is required separately.
Page 68 2.4 Communications with MP-series Controllers Using I/O Message Communications with the MP3000 as the Master Set DW0002 to 6 to receive the write request. Set Ch-No to 6 to receive the write request. Save the data to flash memory. This concludes the setup. ...
Page 69: Using The Msg-Snde Function With The Mp3000 As The Master
SNDE function together with I/O message communications by maintaining a separate connection. This section describes how to communicate with an MP2300-series Controller by using the MSG-SNDE function. MP3000 MP2300 (local station) (remote station) 218IF-01 MP2300 YASKAWA STRX STOP INIT TEST CNFG TEST PORT OFF ON...
Page 70 MP2300 slave are written to the MW00400 to MW00499 hold registers in the MP3000 master. MP3000 MP2300 (local station) (remote station) IP address: 192.168.001.001 IP address: 192.168.001.002 218IF-01 MP2300 YASKAWA STRX STOP INIT TEST CNFG TEST PORT OFF ON Master...
Page 71 2.4 Communications with MP-series Controllers Using the MSG-SNDE Function with the MP3000 as the Master  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 72 2.4 Communications with MP-series Controllers Using the MSG-SNDE Function with the MP3000 as the Master Set the connection parameters.        Select 3 in the Connect No. Box. Enter “10003” in the Port No. Box for the MP-series Controller. Select Extended MEMOBUS in the Communications Protocol Type Box, and then click the Default Button.
Page 73 2.4 Communications with MP-series Controllers Using the MSG-SNDE Function with the MP3000 as the Master Note: Changes made to the communications or connection parameters will become effective only after the changes have been saved to flash memory and the power supply has been cycled. Create a ladder program for the MSG-SNDE function.
Page 74 2.4 Communications with MP-series Controllers Using the MSG-SNDE Function with the MP3000 as the Master Save the data to flash memory. This concludes the settings for using the MP3000 as the master. 2-56...
Page 75 2.4 Communications with MP-series Controllers Using the MSG-SNDE Function with the MP3000 as the Master  Setting Up the Other Device (MP2300) to Connect Use the following procedure to set up the MP2300. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IF in the Module Details Area of the Module Configuration Definition Tab Page.
Page 76 2.4 Communications with MP-series Controllers Using the MSG-SNDE Function with the MP3000 as the Master Set the connection parameters.       Enter “10003” in the Local Port Box. Enter the following address in the Node IP Address Boxes: 192.168.001.001. Enter “10003”...
Page 77: Message Functions
2.4 Communications with MP-series Controllers Message Functions Message Functions The message functions are used in user communications applications for the Extended MEMOBUS proto- col. You can send and receive message data by setting the necessary input items and parameters for the message functions.
Page 78 2.4 Communications with MP-series Controllers Message Functions  Abort Specify the bit to use to abort the message transmission. When the Abort Bit turns ON, the message transmission will be stopped unconditionally. The Abort Bit takes precedence over the Execute Bit. ...
Page 79 2.4 Communications with MP-series Controllers Message Functions  Ch-No (Communications Buffer Channel Number) Specify the channel number of the communications buffer. You can specify any channel number provided it is within the valid range. When executing more than one function at the same time, do not use the same channel number for the same connection.
Page 80 2.4 Communications with MP-series Controllers Message Functions  Busy Specify the bit that shows that the message transmission is in progress. The Busy Bit is ON while a message transmission or abort is in progress. Keep the Execute Bit or Abort Bit turned ON while the Busy Bit is ON. ...
Page 81 2.4 Communications with MP-series Controllers Message Functions • Execution When an Error Occurs To send another message, turn OFF the Execute Bit for at least one scan after the error occurs. Input: Execute Input: Abort Output: Busy Output: Complete Output: Error 1 scan MSG-SNDE Function Parameters The following table describes the contents of the addresses specified by the PARAM input parameter to...
Page 82 2.4 Communications with MP-series Controllers Message Functions Continued from previous page. Meaning Description − For system use − Reserved for system. − − Reserved for system. − Reserved for system. − Reserved for system.  Processing Result (PARAM00) This parameter gives the processing result. Processing Meaning Result Value...
Page 83 2.4 Communications with MP-series Controllers Message Functions  RESULT These bits give the execution result of the MSG-SNDE function. Code Abbreviation Meaning The message send failed or connection ended with an error in Ethernet CONN_NG communications. SEND_OK The message was sent normally. REC_OK The message was received normally.
Page 84 2.4 Communications with MP-series Controllers Message Functions  Detail Error Code (PARAM02 and PARAM03) These parameters give the detail error code. Processing Detail Result Value Error Error Description Description (PARAM00) Code An unused function code was sent or received. Check 81...
Page 85 2.4 Communications with MP-series Controllers Message Functions Continued from previous page. Status 2 Value Meaning Description M-SND: The remote station rejected an attempt to Connection Error open a TCP connection. M-RCV: An error occurred while passively opening a Connection Error TCP connection.
Page 86 2.4 Communications with MP-series Controllers Message Functions Communications Connection Description Device Number Specifies the connection number of the remote station to send the 218IFD 1 to 20 message to. Note: Enter the same connection number as displayed in the 218IFD Detail Definition Dialog Box in the MPE720. ...
Page 87 2.4 Communications with MP-series Controllers Message Functions Continued from previous page. Registers When Acting as Target the Master Function Code Data Function Send Receive Type Registers Registers 4341 hex Reads the states of bits. 4345 hex Changes the state of a single bit. 4346 hex Writes to a single register.
Page 88 2.4 Communications with MP-series Controllers Message Functions Continued from previous page. Target Function Code Data Function Data Address Setting Range Type Not used for the Extended MEMOBUS − 0C hex Disabled. protocol. Reads the contents of non-consecutive hold 0D hex 0 to 65534 (0 to FFFE hex) ∗3 registers (extended).
Page 89 Specify 1 if the remote device is an MP2000-series Controller. If the remote device is a Yaskawa Controller that is not part of the MP2000 Series and it is comprised of multiple CPU Modules, specify the destination CPU Module number.
Page 90 2.4 Communications with MP-series Controllers Message Functions  Reserved for System (PARAM19) This parameter is used by the system. Do not change the value of PARAM19 from a user program or by any other means. Note  Local Station Data Address (PARAM20 and PARAM21) Set the address of the read data destination or write data source in the MP3000-series Controller.
Page 91 2.4 Communications with MP-series Controllers Message Functions  For System Use (PARAM24) This parameter is used by the system. It contains the channel number of the communications buffer that is currently in use. A user program must set PARAM24 to 0 on the first scan after startup. Thereafter, do not change the value of PARAM24 from a user program or any other means.
Page 92 2.4 Communications with MP-series Controllers Message Functions Inputs and Outputs for the MSG-RCVE Function Function MSG-RCVE Name Receives a message from a remote station on the specified circuit of the communications device Function type. This function can be used with various protocols. MSG-RCVE Execute Busy...
Page 93 2.4 Communications with MP-series Controllers Message Functions  Pro-Typ (Communications Protocol) Specify the type code of the communications protocol. Communications Type Code Remarks Protocols Select this protocol when using the Extended MEMOBUS protocol. MEMOBUS MEMOBUS is automatically converted to Extended MEMOBUS inside the 218IFD.
Page 94 2.4 Communications with MP-series Controllers Message Functions The following table gives the valid channel numbers. Communications Device Valid Channel Numbers 218IFD 1 to 10 If the communications device is the 218IFD, there are 10 channels of communications buffers available for both transmission and reception. Therefore, 10 connections may be used for sending and receiving at the same time by using channels 1 to 10.
Page 95 2.4 Communications with MP-series Controllers Message Functions  Busy Specify the bit that shows that the message reception is in progress. The Busy Bit is ON while a message reception or abort is in progress. Keep the Execute Bit or Abort Bit turned ON while the Busy Bit is ON. ...
Page 96 2.4 Communications with MP-series Controllers Message Functions • Execution When an Error Occurs To receive another message, keep the Execute Bit ON even after the error occurs. Input: Execute Input: Abort Output: Busy Output: Complete Output: Error 1 scan MSG-RCVE Function Parameters The following table describes the contents of the addresses specified by the PARAM input parameter to the MSG-RCVE function.
Page 97 2.4 Communications with MP-series Controllers Message Functions Continued from previous page. Meaning Description Sets the connection number used to determine the 10 Inputs Connection Number remote station. 11 I/O Option Not used for the Extended MEMOBUS protocol. Gives the function code requested by the remote 12 Outputs Function Code station.
Page 98 2.4 Communications with MP-series Controllers Message Functions  Processing Result (PARAM00) This parameter gives the processing result. Processing Meaning Result Value 00xx hex Busy 10xx hex Complete 8yxx hex Error Note: The lower byte is used for system analysis. Refer to the following section for details on errors. ...
Page 99 2.4 Communications with MP-series Controllers Message Functions  COMMAND These bits indicate the processing command of the MSG-RCVE function. Code (Hex) Abbreviation Meaning General-purpose message transmission (for no-protocol communi- U_SEND cations) General-purpose message reception (for no-protocol communica- U_REC tions) ABORT Forced abort MEMOBUS command transmission: Completed when response is M_SEND...
Page 100 2.4 Communications with MP-series Controllers Message Functions Continued from previous page. Processing Detail Result Value Error Error Description Description (PARAM00) Code The channel number for the communications buffer is out Channel number 85 hex of range. Check the communications buffer channel num- setting error ber (Ch-No) in the MSG-RCVE function.
Page 101 2.4 Communications with MP-series Controllers Message Functions  Status 3 (PARAM06) This parameter gives the value of the send pass counter. Status 3 Value Meaning Description 0 to 65535 Send Count Counts the number of times a message was sent. ...
Page 102 2.4 Communications with MP-series Controllers Message Functions  Option (PARAM11) This code is not used for the Extended MEMOBUS protocol.  Function Code (PARAM12) This parameter gives the function code that was received. Registers When Acting Target as the Master Function Code Data Function...
Page 103 2.4 Communications with MP-series Controllers Message Functions  Data Address (PARAM14 and PARAM15) These parameters give the data address that was requested by the remote station. For function codes 01 to 10 hex, the requested address is the word size address indicated only by PARAM14.
Page 104 This parameter gives 1 if the remote device is an MP2000-series device. This parameter indicates the remote CPU Module number if the remote device is a Yaskawa Controller that is not a part of the MP2000 Series and it is comprised of multiple CPU Modules.
Page 105 2.4 Communications with MP-series Controllers Message Functions  Input Register Offset (PARAM24 and PARAM25) These parameters set the offset for the data address in the MP3000. The MP3000 will offset the address back by the number of words specified by the offset. The data address cannot be offset in the forward direction.
Page 106 2.4 Communications with MP-series Controllers Message Functions  M Register Writing Range LO (PARAM36 and PARAM37) These parameters set the lower limit of the allowable address range for write requests from the remote sta- tion. An error will occur if the write request is outside this allowable range. Specify the writing range with word addresses.
Page 107 2.4 Communications with MP-series Controllers Message Functions  O Register Writing Range HI (PARAM46 and PARAM47) These parameters set the upper limit of the allowable address range for write requests from the remote sta- tion. An error will occur if the write request is outside this allowable range. Specify the writing range with word addresses.
Page 108: Communications With A Touch Panel
2.5 Communications with a Touch Panel Using Automatic Reception with the MP3000 as a Slave Communications with a Touch Panel When using Ethernet communications between the MP3000 and a Touch Panel from Digital Electronics Corporation, use the Extended MEMOBUS protocol as the communications protocol. The Extended MEMOBUS protocol allows the master to read and write the slave registers.
Page 109 2.5 Communications with a Touch Panel Using Automatic Reception with the MP3000 as a Slave Setting Example The following figure illustrates how the contents of the MW00100 hold register in the MP3000 slave is displayed on the Touch Panel, and written from the Touch Panel to the same register. MP3000 Touch Panel (local station)
Page 110 2.5 Communications with a Touch Panel Using Automatic Reception with the MP3000 as a Slave MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 111 2.5 Communications with a Touch Panel Using Automatic Reception with the MP3000 as a Slave Set the connection parameters.        Select 1 in the Connect No. Box. Enter “10001” in the Port No. Box for the MP-series Controller. Select Extended MEMOBUS in the Communications Protocol Type Box, and then click the Default Button.
Page 112 2.5 Communications with a Touch Panel Using Automatic Reception with the MP3000 as a Slave Check the settings and double-click the Setting Button in the Detail Column. Select the Enable Option in the Automatically Reception Tab Page and then click the OK Button. Note: 1.
Page 113 AGP33** Series Model AGP-3600T Orientation Landscape Specify the device or PLC connected. Manufacturer YASKAWA Electric Corporation Series MEMOBUS Ethernet Specify the connection method. Port Ethernet (TCP) Select Device/PLC under Peripheral Settings on the System Settings Sidebar to display the Connected Equipment Setting Tab Page.
Page 114 2.5 Communications with a Touch Panel Using Automatic Reception with the MP3000 as a Slave • Setting the MP3000 to Unpassive Open Mode If the remote station’s address is set to 000.000.000.000 and the remote station’s port number is set to 0, the connection is set to the Unpassive Open Mode.
Page 115 2.5 Communications with a Touch Panel Using Automatic Reception with the MP3000 as a Slave  Screen Creation Example Create a base screen. From the tool bar, select Data Display and place the object on the screen. GP-Pro EX Screen Place here 12345 Double-click the Data Display placed on the screen.
Page 116: Communications With A Mitsubishi Plc (A-Compatible 1E Frame Protocol)
2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Using Automatic Reception with the MP3000 as a Slave Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) When using Ethernet communications between the MP3000 and a Mitsubishi Q/A-series PLC, use the A- compatible 1E Frame protocol as the communications protocol.
Page 117 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Using Automatic Reception with the MP3000 as a Slave Setting Example The following figure illustrates how the contents of the D00201 to D00300 data registers in the Mitsubishi Q/A-series PLC master are written to the MW00000 to MW00099 hold registers in the MP3000 slave. Mitsubishi MP3000 (local station)
Page 118 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Using Automatic Reception with the MP3000 as a Slave MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 119 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Using Automatic Reception with the MP3000 as a Slave Set the connection parameters.        Select 1 in the Connect No. Box. Enter “10001” in the Port No. Box for the MP-series Controller. Select MELSEC (A-compatible 1E) in the Communication Protocol Type Box, and then click the Default Button.
Page 120 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Using Automatic Reception with the MP3000 as a Slave Check the settings and double-click the Setting Button in the Detail Column. Select the Enable Option in the Automatically Reception Tab Page and then click the OK Button. Note: 1.
Page 121 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Using Automatic Reception with the MP3000 as a Slave  Setting Up the Remote Device (Mitsubishi Q/A-series PLC) Use the following procedure to set up the Mitsubishi Q/A-series PLC (MELSEC device). MELSEC devices are manufactured by Mitsubishi Electric Corporation.
Page 122 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Using Automatic Reception with the MP3000 as a Slave Set the initial settings and router relay parameters as necessary. Information • Initial Settings These settings apply to the timers when TCP is the selected protocol. In most cases, accept the default.
Page 123: Using I/O Message Communications With The Mp3000 As The Master
2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Using I/O Message Communications with the MP3000 as the Master Using I/O Message Communications with the MP3000 as the Master This section describes how to perform inter-CPU Module communications with a Mitsubishi Q/A-series PLC by using I/O message communications.
Page 124 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Using I/O Message Communications with the MP3000 as the Master Setting Example The following figure illustrates how the contents of the D00000 to D00099 data registers in the Mitsubishi Q/A-series PLC slave can be read into the IW0000 to IW0063 input registers in the MP3000 master and how the contents of the OW0064 to OW00C7 output registers in the MP3000 master are written to the D00100 to D00199 data registers in the Mitsubishi Q/A-series PLC slave.
Page 125 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Using I/O Message Communications with the MP3000 as the Master MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 126 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Using I/O Message Communications with the MP3000 as the Master Click the Easy setting Button. Set the connection parameters.            ...
Page 127 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Using I/O Message Communications with the MP3000 as the Master Click the OK Button. Click the Yes Button in the Transmission Parameters Confirmation Dialog Box. Note: If parameters have already been set for the same connection number and you click the Yes Button in the Transmission Parameters Confirmation Dialog Box, the settings will be overwritten by the parameters that are set in the Message Communication Easy Setting Dialog Box.
Page 128 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Using I/O Message Communications with the MP3000 as the Master Specify the open settings. Parameter Setting (Connection Number 1) Setting (Connection Number 2) Protocol Open system Full passive Full passive Fixed buffer As required.
Page 129: Message Functions
2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions Message Functions The message functions are used in user communications applications for the A-compatible 1E Frame pro- tocol. You can send and receive message data by setting the necessary input items and parameters for the message functions.
Page 130 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Abort Specify the bit to use to abort the message transmission. When the Abort Bit turns ON, the message transmission will be stopped unconditionally. The Abort Bit takes precedence over the Execute Bit.
Page 131 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Ch-No (Communications Buffer Channel Number) Specify the channel number of the communications buffer. You can specify any channel number provided it is within the valid range. When executing more than one function at the same time, do not use the same channel number for the same connection.
Page 132 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Busy Specify the bit that shows that the message transmission is in progress. The Busy Bit is ON while a message transmission or abort is in progress. Keep the Execute Bit or Abort Bit turned ON while the Busy Bit is ON.
Page 133 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions • Execution When an Error Occurs To send another message, turn OFF the Execute Bit for at least one scan after the error occurs. Input: Execute Input: Abort Output: Busy Output: Complete Output: Error...
Page 134 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions Continued from previous page. Meaning Description Connection Number Sets the connection number used to determine the remote station. Option Not used for the A-compatible 1E Frame protocol. Sets the code of the function in the A-compatible 1E Frame proto- Function Code col.
Page 135 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions Bits 0 to 7: PARAMETER Bits 8 to B: COMMAND Bits C to E: RESULT Bit F: REQUEST  REQUEST This bit gives the status of the processing request for the MSG-SNDE function. Bit Status Meaning Processing is being requested.
Page 136 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  PARAMETER When RESULT is 4 (FMT_NG: parameter formatting error), these bits will indicate an error code from the following table. For any other value, the bits will contain the connection number. RESULT Code (Hex) Meaning...
Page 137 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Status 1 (PARAM04) This parameter gives status information. Status 1 Value Meaning Description IDLE The connection is idle. WAIT The connection is waiting to be made. CONNECT The connection is established.
Page 138 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Status 5 (PARAM08) This parameter gives the value of the error counter. Status 5 Value Meaning Description Counts the number of errors that occurred during message pro- 0 to 65535 Error Count cessing.
Page 139 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions Continued from previous page. Common Target Function Code Instructions for Function Data Type MELSEC ACPUs Sets/resets word devices in units of one point by 0E hex 05 hex specifying a device number.
Page 140 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions Bit Device Conversion Table Device Range for Correspond- Data Address Device ACPU Common Notation Function Code ing Register Setting Range Instructions Addresses MB001760 to CC000 to CC255 Decimal 02 hex: Input relays 2816 to 3071 MB00191F...
Page 141 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions Continued from previous page. Common Function Instructions for Function Data Size Setting Range Code MELSEC ACPUs − 08 hex 16 hex Performs a loopback test. Sets/resets word devices in units of one point by 0E hex 05 hex 1 to 40 points...
Page 142 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Local Station Register Type (PARAM22) Set the register type of the read data destination or write data source in the MP3000. Register Type Type Remarks Value Sets the target data type to MB for bits and MW for words. Sets the target data type to GB for bits and GW for words.
Page 143 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions Inputs and Outputs for the MSG-RCVE Function Function MSG-RCVE Name Receives a message from a remote station on the specified circuit of the communications device Function type. This function can be used with various protocols. MSG-RCVE Execute Busy...
Page 144 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Dev-Typ (Communications Device Type) Specify the type code of the communications device. Device Type Code 218IFD  Pro-Typ (Communications Protocol) Specify the type code of the communications protocol. Communications Type Code Remarks...
Page 145 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Ch-No (Communications Buffer Channel Number) Specify the channel number of the communications buffer. You can specify any channel number provided it is within the valid range. When executing more than one function at the same time, do not use the same channel number for the same connection.
Page 146 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Busy Specify the bit that shows that the message reception is in progress. The Busy Bit is ON while a message reception or abort is in progress. Keep the Execute Bit or Abort Bit turned ON while the Busy Bit is ON.
Page 147 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions • Execution When an Error Occurs To receive another message, keep the Execute Bit ON even after the error occurs. Input: Execute Input: Abort Output: Busy Output: Complete Output: Error 1 scan MSG-RCVE Function Parameters...
Page 148 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions Continued from previous page. Meaning Description Sets the connection number used to determine the 10 Inputs Connection Number remote station. 11 I/O Option Not used for the A-compatible 1E Frame protocol. Out- Gives the function code requested by the remote Function Code...
Page 149 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Processing Result (PARAM00) This parameter gives the processing result. Processing Meaning Result Value 00xx hex Busy 10xx hex Complete 8yxx hex Error Note: The lower byte is used for system analysis. Refer to the following section for details on errors.
Page 150 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions Continued from previous page. Code Abbreviation Meaning A data reception error (error detected in the lower-layer program) REC_NG occurred.  COMMAND These bits indicate the processing command of the MSG-RCVE function. Code (Hex) Abbreviation Meaning...
Page 151 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions Continued from previous page. Processing Detail Result Value Error Error Description Description (PARAM00) Code Circuit number setting The circuit number is out of range. Check the circuit num- 84...
Page 152 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Status 3 (PARAM06) This parameter gives the value of the send pass counter. Status 3 Value Meaning Description 0 to 65535 Send Count Counts the number of times a message was sent. ...
Page 153 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Function Code (PARAM12) This parameter gives the function code that was received. Common Target Function Code Instructions for Data Function MELSEC ACPUs Type 01 or 02 hex 00 hex Reads bit devices in units of one point.
Page 154 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Offsets (PARAM20 to PARAM27) These parameters set the offset for the data address in the MP3000. The MP3000 will offset the address by the number of words specified by the offset. Note: An offset cannot be a negative value.
Page 155 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  Output Register Offset (PARAM34 and PARAM35) This parameter is not used for the A-compatible 1E Frame protocol.  M Register Writing Range (PARAM36 to PARAM39) These parameters set the allowable address range for write requests from the remote station. An error will occur if the write request is outside this allowable range.
Page 156 2.6 Communications with a Mitsubishi PLC (A-compatible 1E Frame protocol) Message Functions  O Register Writing Range LO (PARAM44 and PARAM45) This parameter is not used for the A-compatible 1E Frame protocol.  O Register Writing Range HI (PARAM46 and PARAM47) This parameter is not used for the A-compatible 1E Frame protocol.
Page 157: Communications With A Mitsubishi Plc (Qna-Compatible 3E Frame Protocol)
2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using I/O Message Communications with the MP3000 as the Master Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) When using Ethernet communications between the MP3000 and a Mitsubishi Q/QnA-series PLC, use the QnA-compatible 3E Frame protocol as the communications protocol.
Page 158 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using I/O Message Communications with the MP3000 as the Master Device Memory and Corresponding Registers in the MP3000 The following tables show the relationship between registers in the MP3000 and device memory in the Mitsubishi Q/QnA-series PLC.
Page 159 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using I/O Message Communications with the MP3000 as the Master Setting Example The following figure illustrates how the contents of the D02000 to D02099 data (D) registers in the CPU Unit of Mitsubishi Q/QnA-series PLC slave are read into the IW0100 to IW0163 input registers in the MP3000 master.
Page 160 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using I/O Message Communications with the MP3000 as the Master  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 161 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using I/O Message Communications with the MP3000 as the Master Set the connection parameters.            Enter “5000” in the MP3000 Local Port Box. ...
Page 162 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using I/O Message Communications with the MP3000 as the Master  Setting Up the Remote Device (Mitsubishi Q/QnA-series PLC) Use the following procedure to set up the Mitsubishi Q/QnA-series PLC (MELSEC device). MELSEC devices are manufactured by Mitsubishi Electric Corporation.
Page 163 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using I/O Message Communications with the MP3000 as the Master Setting Example to Open the Built-in Ethernet Port in a MELSEC Device Parameter Description Protocol Open system MC protocol − TCP connection Local station port No.
Page 164: Using The Msg-Snde Function With The Mp3000 As The Master
2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Using the MSG-SNDE Function with the MP3000 as the Master This section describes how to communicate with a Mitsubishi Q/QnA-series PLC by using the MSG- SNDE function in the MP3000.
Page 165 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Device Memory and Corresponding Registers in the MP3000 The following tables show the relationship between registers in the MP3000 and device memory in the Mitsubishi Q/QnA-series PLC.
Page 166 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using the MSG-SNDE Function with the MP3000 as the Master The following map, based on bit and word device conversion tables, shows how M registers in the MP3000 correspond to devices in the Mitsubishi Q/QnA-series PLCs. All devices in a Mitsubishi Q/QnA- series PLC are assigned to hold registers, input registers, input relays, and coils so that the MP3000 can read and write to them by using MEMOBUS commands as an interface.
Page 167 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Transfer Size The following table lists the size of data that can be transferred using the MSG-SNDE function. Use the data size within the ranges listed in the following table according to the conditions of the Mitsubishi Q/ QnA-series PLC slave.
Page 168 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using the MSG-SNDE Function with the MP3000 as the Master  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 169 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Set the connection parameters.  Select 1 in the Connect No. Box.  Enter “5010” in the Port No. Box for the MP-series Controller. ...
Page 170 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Check the settings and double-click the Setting Button in the Detail Column. Click the Disable Option on the Automatically Reception Tab Page. Note: Changes made to the communications or connection parameters will become effective only after the changes have been saved to flash memory and the power supply has been cycled.
Page 171 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Create a ladder program for the MSG-SNDE function. A ladder program example is shown below. 2-153...
Page 172 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Save the data to flash memory. This concludes the settings for using the MP3000 as the master. 2-154...
Page 173 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using the MSG-SNDE Function with the MP3000 as the Master  Setting Up the Remote Device (Mitsubishi Q/QnA-series PLC) Use the following procedure to set up the Mitsubishi Q/QnA-series PLC (MELSEC device). MELSEC devices are manufactured by Mitsubishi Electric Corporation.
Page 174 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Using the MSG-SNDE Function with the MP3000 as the Master This concludes the setup. Set any other parameters as necessary, then transfer the data to the PLC. Set the initial settings and router relay parameters as necessary. Information •...
Page 175: Message Functions
2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions Message Functions The message functions are used in user communications applications for the QnA-compatible 3E Frame protocol. You can send and receive message data by setting the necessary input items and parameters for the message functions.
Page 176 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Abort Specify the bit to use to abort the message transmission. When the Abort Bit turns ON, the message transmission will be stopped unconditionally. The Abort Bit takes precedence over the Execute Bit.
Page 177 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Ch-No (Communications Buffer Channel Number) Specify the channel number of the communications buffer. You can specify any channel number provided it is within the valid range. When executing more than one function at the same time, do not use the same channel number for the same connection.
Page 178 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Busy Specify the bit that shows that the message transmission is in progress. The Busy Bit is ON while a message transmission or abort is in progress. Keep the Execute Bit or Abort Bit turned ON while the Busy Bit is ON.
Page 179 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions • Execution When an Error Occurs To send another message, turn OFF the Execute Bit for at least one scan after the error occurs. Input: Execute Input: Abort Output: Busy Output: Complete Output: Error...
Page 180 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions Continued from previous page. Meaning Description Connection Number Sets the connection number used to determine the remote station. Option Sets the I/O unit number for the remote station. Sets the code of the function in the QnA-compatible 3E Frame Function Code protocol.
Page 181 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Status (PARAM01) This parameter gives the status of the communications device. The following figure shows the bit assignments and it is followed by a detailed description of each assign- ment.
Page 182 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  PARAMETER When RESULT is 4 (FMT_NG: parameter formatting error), these bits will indicate an error code from the following table. For any other value, the bits will contain the connection number. RESULT Code (Hex) Meaning...
Page 183 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Status 1 (PARAM04) This parameter gives status information. Status 1 Value Meaning Description IDLE The connection is idle. WAIT The connection is waiting to be made. CONNECT The connection is established.
Page 184 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Status 5 (PARAM08) This parameter gives the value of the error counter. Status 5 Value Meaning Description Counts the number of errors that occurred during message pro- 0 to 65535 Error Count cessing.
Page 185 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Function Code (PARAM12) Set the function code to send. You can use the functions that are registered to the function codes. QnA-compatible 3E Frame Target Commands MEMOBUS Data Function Function Code...
Page 186 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions Bit Device Conversion Table QnA-compatible 3E MEMOBUS Register Device Notation First Address Device Range Command Address MB026880 to Link Special 01, 05, and 0F SM000000 to SM002047 Decimal 43008 to 45055 Relays hex: Coils...
Page 187 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Data Size (PARAM17) Set the data size for the read/write request as the number of bits or words. Be sure that the last data address that is determined by the offset, data address, and data size does not exceed the valid data address range.
Page 188 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Local Station Register Type (PARAM22) Set the register type of the read data destination or write data source in the MP3000. Register Type Type Remarks Value Sets the target data type to MB for bits and MW for words. Sets the target data type to GB for bits and GW for words.
Page 189 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions Inputs and Outputs for the MSG-RCVE Function Function MSG-RCVE Name Receives a message from a remote station on the specified circuit of the communications device Function type. This function can be used with various protocols. MSG-RCVE Execute Busy...
Page 190 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Pro-Typ (Communications Protocol) Specify the type code of the communications protocol. Communications Type Code Remarks Protocol Select this protocol when using the QnA-compatible 3E Frame proto- MEMOBUS col.
Page 191 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Param (First Address of Parameter List) Specify the first address of the parameter list. A total of 52 words starting from the specified first word are automatically used for the parameter list. The parameter list is used by inputting the connection number and relevant parameter data.
Page 192 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions • Normal Execution To receive another message, keep the Execute Bit ON even after the completion of processing. Input: Execute Input: Abort Output: Busy Output: Complete 1 scan Output: Error •...
Page 193 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions MSG-RCVE Function Parameters The following table describes the contents of the addresses specified by the PARAM input parameter to the MSG-RCVE function. Meaning Description Processing Result Gives the processing status. Status Gives the status of the current function.
Page 194 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions Continued from previous page. Meaning Description Coil Offset, Lower Word Sets the offset word address for a coil (MB). Coil Offset, Upper Word Input Relay Offset, Lower Word Sets the offset word address for an input relay (IB).
Page 195 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Processing Result (PARAM00) This parameter gives the processing result. Processing Meaning Result Value 00xx hex Busy 10xx hex Complete 8yxx hex Error Note: The lower byte is used for system analysis. Refer to the following section for details on errors.
Page 196 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  COMMAND These bits indicate the processing command of the MSG-RCVE function. Code (Hex) Abbreviation Meaning U_SEND General-purpose message transmission (for no-protocol communications) U_REC General-purpose message reception (for no-protocol communications) ABORT Forced abort M_SEND...
Page 197 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions Continued from previous page. Processing Detail Result Value Error Error Description Description (PARAM00) Code An error response was received from the communications Communications 88 hex device. Check the connections to the device. Also check to device error see if the remote device is ready to communicate.
Page 198 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Status 4 (PARAM07) This parameter gives the value of the receive pass counter. Status 4 Value Meaning Description 0 to 65535 Receive Count Counts the number of times a message was received. ...
Page 199 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Function Code (PARAM12) This parameter gives the function code that was received. QnA-compatible 3E Frame Commands MEMOBUS Target Data Function Function Code Type Subcom- Command mand 0001 hex 01 or 02 hex Reads bit devices in units of one point.
Page 200 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions Word Device Conversion Table QnA-compatible 3E MEMOBUS First Register Device Notation Frame Device Range Command Address Address 03, 06, 09, 0B, 0D, 00000 to MW00000 to Data Registers D000000 to D012287 Decimal 0E, and 10 hex:...
Page 201 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  Offsets (PARAM20 to PARAM27) These parameters set the offset for the data address in the MP3000. The MP3000 will offset the address by the number of words specified by the offset. Note: An offset cannot be a negative value.
Page 202 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  M Register Writing Range (PARAM36 to PARAM39) These parameters set the allowable address range for write requests from the remote station. An error will occur if the write request is outside this allowable range. Specify the M Register Writing Range (PARAM36 to PARAM39) with word addresses.
Page 203 2.7 Communications with a Mitsubishi PLC (QnA-compatible 3E Frame Protocol) Message Functions  For System Use (PARAM48) This parameter is used by the system. It contains the channel number of the communications buffer that is currently in use. A user program must set PARAM48 to 0 on the first scan after startup. Thereafter, do not change the value of PARAM48 from a user program or by any other means.
Page 204: Communications With An Omron Plc (Fins Communications Service)
2.8 Communications with an OMRON PLC (FINS Communications Service) Using Automatic Reception with the MP3000 as a Slave Communications with an OMRON PLC (FINS Communications Service) When using Ethernet communications between the MP3000 and an OMRON PLC, use the FINS protocol as the communications protocol.
Page 205 2.8 Communications with an OMRON PLC (FINS Communications Service) Using Automatic Reception with the MP3000 as a Slave FINS Commands The FINS commands that can be used with automatic reception in the MP3000 are listed below. When executing FINS commands on an OMRON PLC that is acting as the master, use the command codes and I/ O memory types that are given in the following table.
Page 206 2.8 Communications with an OMRON PLC (FINS Communications Service) Using Automatic Reception with the MP3000 as a Slave Data Range Data OMRON CPU Unit Data Area Name Type MP3000 I/O Memory Addresses Addresses Word notation: MW00000 to MW02047 CIO Area Word 0000 to 2047 000000 to 07FF00...
Page 207 2.8 Communications with an OMRON PLC (FINS Communications Service) Using Automatic Reception with the MP3000 as a Slave Setting Example The following figure illustrates how the contents of the D00000 to D00099 in the DM Area in the CPU Unit of the OMRON master are written to the MW00000 to MW00099 hold registers in the MP3000 slave.
Page 208 2.8 Communications with an OMRON PLC (FINS Communications Service) Using Automatic Reception with the MP3000 as a Slave  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 209 2.8 Communications with an OMRON PLC (FINS Communications Service) Using Automatic Reception with the MP3000 as a Slave Set the connection parameters. Select 1 in the Connect No. Box. Enter “9600” in the Port No. Box for the MP-series Machine Controller. Select OMRON (FINS) in the Communication Protocol Type Box.
Page 210 2.8 Communications with an OMRON PLC (FINS Communications Service) Using Automatic Reception with the MP3000 as a Slave Select the Enable Option in the Automatically Reception Tab Page and then click the OK Button. Note: Refer to the following section for details on automatic reception. 2.2 Detail Definition Setting Procedures (page 2-6) The setting in the Node Address Box on the Other Tab Page will contain the value that is set in the Mes- sage Communication Easy Setting Dialog Box.
Page 211 2.8 Communications with an OMRON PLC (FINS Communications Service) Using Automatic Reception with the MP3000 as a Slave Save the data to flash memory. Note: Changes made to the communications or connection parameters will become effective only after the changes have been saved to flash memory and the power supply has been cycled.
Page 212 2.8 Communications with an OMRON PLC (FINS Communications Service) Using Automatic Reception with the MP3000 as a Slave Create ladder programming for network transmissions. To write data to a node on the network, use the SEND instruction. The following is an example of the set- tings for a SEND instruction.
Page 213: Using The Msg-Rcve Function With The Mp3000 As A Slave
2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-RCVE Function with the MP3000 as a Slave Using the MSG-RCVE Function with the MP3000 as a Slave This section describes how to communicate with an OMRON PLC by using the MSG-RCVE function. When an OMRON PLC is used as the master to execute FINS commands, it will need a ladder application that uses the SEND and RECV instructions.
Page 214 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-RCVE Function with the MP3000 as a Slave Transfer Size The following table lists the data sizes that can be received in a single FINS command when using the MSG-RCVE function.
Page 215 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-RCVE Function with the MP3000 as a Slave  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 216 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-RCVE Function with the MP3000 as a Slave Set the connection parameters. Select 1 in the Connect No. Box. Enter “9600” in the Port No. Box for the MP-series Machine Controller. Select OMRON (FINS) in the Communication Protocol Type Box.
Page 217 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-RCVE Function with the MP3000 as a Slave Check the settings and double-click the Setting Button in the Detail Column. Click the Disable Option on the Automatically Reception Tab Page. Click the Other Tab and enter “1”...
Page 218 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-RCVE Function with the MP3000 as a Slave Create a ladder program for the MSG-RCVE function. A ladder program example is shown below. 2-200...
Page 219 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-RCVE Function with the MP3000 as a Slave Save the data to flash memory. This concludes the settings for using the MP3000 as a slave. 2-201...
Page 220 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-RCVE Function with the MP3000 as a Slave  Setting the Remote Device (OMRON PLC) Use the following procedure to set up the OMRON CJ-series PLC. The CJ Series is manufactured by OMRON Corporation. Contact OMRON Corporation for further information.
Page 221 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-RCVE Function with the MP3000 as a Slave Create ladder programming for network transmissions. To read data from a node on the network, use the RECV instruction. The following is an example of the set- tings for a RECV instruction.
Page 222: Using I/O Message Communications With The Mp3000 As The Master
2.8 Communications with an OMRON PLC (FINS Communications Service) Using I/O Message Communications with the MP3000 as the Master Using I/O Message Communications with the MP3000 as the Master This section describes how to communicate with an OMRON PLC by using I/O message communications. MP3000 OMRON CS/CJ/CP-series PLC (local station)
Page 223 2.8 Communications with an OMRON PLC (FINS Communications Service) Using I/O Message Communications with the MP3000 as the Master I/O Memory Data Areas and Corresponding Registers in the MP3000 The following table shows the relationship between registers in the MP3000 and the I/O memory data areas.
Page 224 2.8 Communications with an OMRON PLC (FINS Communications Service) Using I/O Message Communications with the MP3000 as the Master Setting Example The following figure illustrates how the contents of the D02000 to D02199 in the DM Area in the CPU Unit of the OMRON PLC slave are read into the IW0100 to IW01C7 input registers in the MP3000 master.
Page 225 2.8 Communications with an OMRON PLC (FINS Communications Service) Using I/O Message Communications with the MP3000 as the Master  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 226 2.8 Communications with an OMRON PLC (FINS Communications Service) Using I/O Message Communications with the MP3000 as the Master Set the connection parameters. Enter “9600” in the MP3000 Local Port Box. Enter the following address for the remote device in the Node IP Address Box: 192.168.001.002. Enter “9600”...
Page 227 2.8 Communications with an OMRON PLC (FINS Communications Service) Using I/O Message Communications with the MP3000 as the Master Click the Other Tab and enter “1” in the Node Address Box. Note: 1. The unit address and network address of the MP3000 are always 00 hex. 2.
Page 228 2.8 Communications with an OMRON PLC (FINS Communications Service) Using I/O Message Communications with the MP3000 as the Master  Setting the Remote Device (OMRON PLC) Use the following procedure to set up the OMRON CJ-series PLC. The CJ Series is manufactured by OMRON Corporation. Contact OMRON Corporation for further information.
Page 229: Using The Msg-Snde Function With The Mp3000 As The Master
2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-SNDE Function with the MP3000 as the Master Using the MSG-SNDE Function with the MP3000 as the Master This section describes how to communicate with an OMRON PLC by using the MSG-SNDE function. OMRON CS/CJ/CP-series PLC MP3000 (remote station)
Page 230 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-SNDE Function with the MP3000 as the Master I/O Memory Data Areas and Corresponding Registers in the MP3000 The following table shows the relationship between registers in the MP3000 and the I/O memory data areas.
Page 231 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-SNDE Function with the MP3000 as the Master Transfer Size The following table lists the size of data that can be transferred using the MSG-SNDE function. Use the data size within the ranges that are listed in the following table according to the conditions of the OMRON PLC slave.
Page 232 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-SNDE Function with the MP3000 as the Master  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 233 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-SNDE Function with the MP3000 as the Master Set the connection parameters. Select 1 in the Connect No. Box. MPEnter “9600” in the Port No. Box for the MP-series Machine Controller. Select OMRON (FINS) in the Communication Protocol Type Box.
Page 234 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-SNDE Function with the MP3000 as the Master Check the settings and double-click the Setting Button in the Detail Column. Click the Disable Option on the Automatically Reception Tab Page. Click the Other Tab and enter “1”...
Page 235 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-SNDE Function with the MP3000 as the Master Create a ladder program for the MSG-SNDE function. A ladder program example is shown below. 2-217...
Page 236 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-SNDE Function with the MP3000 as the Master Save the data to flash memory. This concludes the settings for using the MP3000 as the master. 2-218...
Page 237 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-SNDE Function with the MP3000 as the Master  Setting the Remote Device (OMRON PLC) Use the following procedure to set up the OMRON CJ-series PLC. The CJ Series is manufactured by OMRON Corporation. Contact OMRON Corporation for further information.
Page 238 2.8 Communications with an OMRON PLC (FINS Communications Service) Using the MSG-SNDE Function with the MP3000 as the Master  Starting Communications Use the following procedure to write the data in the hold registers in the MP3000 to the I/O bits in the CPU Unit of the OMRON PLC.
Page 239: Routing
2.8 Communications with an OMRON PLC (FINS Communications Service) Routing Routing This section describes the restrictions that apply when sending and receiving I/O messages, and when using the MSG-SNDE and MSG-RCVE functions between the MP3000 and OMRON PLCs connected across different networks. Using the MP3000 as the Master When the MP3000 master sends messages using I/O message communications or the MSG-SNDE func- tion, the destination node must be connected to the local network.
Page 240 2.8 Communications with an OMRON PLC (FINS Communications Service) Routing Using the MP3000 as a Router The MP3000 cannot route messages between different networks. OMRON MP3000-series Machine Controller OMRON CS/CJ/CP-series PLC (relay node) CS/CJ/CP-series PLC (source) (destination) Ethernet Ethernet × Message sent to a node on another network.
Page 241: Message Functions
2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions Message Functions The message functions are used in user communications applications for the FINS protocol. You can send and receive message data by setting the necessary input items and parameters for the message functions. Message communications using the FINS protocol can be performed with the same settings as those used for MEMOBUS messages.
Page 242 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Abort Specify the bit to use to abort the message transmission. When the Abort Bit turns ON, the message transmission will be stopped unconditionally. The Abort Bit takes precedence over the Execute Bit. ...
Page 243 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Ch-No (Communications Buffer Channel Number) Specify the channel number of the communications buffer. You can specify any channel number provided it is within the valid range. When executing more than one function at the same time, do not use the same channel number for the same connection.
Page 244 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Busy Specify the bit that shows that the message transmission is in progress. The Busy Bit is ON while a message transmission or abort is in progress. Keep the Execute Bit or Abort Bit turned ON while the Busy Bit is ON. ...
Page 245 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions • Execution When an Error Occurs To send another message, turn OFF the Execute Bit for at least one scan after the error occurs. Input: Execute Input: Abort Output: Busy Output: Complete Output: Error 1 scan...
Page 246 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions Continued from previous page. Meaning Description − For system use − Reserved for system. − − Reserved for system. − Reserved for system. − Reserved for system.  Processing Result (PARAM00) This parameter gives the processing result.
Page 247 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  RESULT These bits give the execution results of the MSG-SNDE function. Code Abbreviation Meaning The message send failed or connection ended with an error in Ethernet CONN_NG communications. SEND_OK The message was sent normally.
Page 248 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Detail Error Code (PARAM02 and PARAM03) These parameters give the detail error code. Processing Detail Result Value Error Error Description Description (PARAM00) Code An unused function code was sent or received. 81...
Page 249 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Status 2 (PARAM05) This parameter gives information on the most recent error. Status 2 Value Meaning Description No error Normal Socket Creation Error A socket could not be created. Local Port Number Error Setting error in local station port number A system error occurred while setting the socket attri-...
Page 250 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Connection Number (PARAM10) Specify the remote station. If the communications device is the 218IFD, enter the connection number. The valid setting range is given in the following table. Communications Connection Description...
Page 251 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions Continued from previous page. FINS Command Code Target MEMOBUS Data Function I/O Memory Function Code Type Type B0 hex Writes to CIO Area words. B1 hex Writes to Work Area words. 0F hex 01 hex 02 hex B2 hex...
Page 252 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Remote Station Register Type (PARAM16) This parameter is not used for the FINS protocol.  Data Size (PARAM17) Set the data size for the read/write request as the number of bits or words. Be sure that the last data address that is determined by the offset, data address, and data size does not exceed the valid data address range.
Page 253 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Local Station Register Type (PARAM22) Set the register type of the read data destination or write data source in the MP3000. Register Type Type Remarks Value Sets the target data type to MB for bits and MW for words. Sets the target data type to GB for bits and GW for words.
Page 254 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions Inputs and Outputs for the MSG-RCVE Function Function MSG-RCVE Name Receives a message from a remote station on the specified circuit of the communications device Function type. This function can be used with various protocols. MSG-RCVE Execute Busy...
Page 255 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Pro-Typ (Communications Protocol) Specify the type code of the communications protocol. Communications Type Code Remarks Protocol Select this protocol when using the FINS protocol. MEMOBUS is MEMOBUS automatically converted to the FINS protocol inside the 218IFD. No-protocol communica- This code is not used for the FINS protocol.
Page 256 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Param (First Address of Parameter List) Specify the first address of the parameter list. A total of 52 words starting from the specified first word are automatically used for the parameter list. The parameter list is used by inputting the connection number and relevant parameter data.
Page 257 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Error Specify the bit that shows if an error occurred while receiving the message. When an error occurs, the Error Bit will turn ON only for one scan. The following diagrams show timing charts for the bit I/O items in the MSG-RCVE function.
Page 258 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions MSG-RCVE Function Parameters The following table describes the contents of the addresses specified by the PARAM input parameter to the MSG-RCVE function. Meaning Description Processing Result Gives the processing status. Status Gives the status of the current function.
Page 259 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions Continued from previous page. Meaning Description G Register Writing Range LO, Lower Word Sets the first address of the writing range for data register data relays. G Register Writing Range LO, Upper Word G Register Writing Range HI, Lower Word Sets the last address of the writing range for data register data relays.
Page 260 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  RESULT These bits give the execution results of the MSG-RCVE function. Code Abbreviation Meaning The message send failed or connection ended with an error in CONN_NG Ethernet communications. SEND_OK The message was sent normally.
Page 261 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Detail Error Code (PARAM02 and PARAM03) These parameters give the detail error code. Processing Detail Result Value Error Error Description Description (PARAM00) Code An unused function code was received. 81...
Page 262 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions Continued from previous page. Status 2 Value Meaning Description The data send request command was sent to a socket UDP Data Send Error that does not exist. A disconnection request was received from the remote TCP Data Receive Error station.
Page 263 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Options (PARAM11) This parameter is not used for the FINS protocol.  Function Code (PARAM12) This parameter gives the function code that was received. FINS Command Code Target MEMOBUS Data Function...
Page 264 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Data Address (PARAM14 and PARAM15) These parameters give the data address that was requested by the remote station. The type of device and device range determine the data area. Bit Conversion Table Corresponding Data Address...
Page 265 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  Offsets (PARAM20 to PARAM27) These parameters set the offset for the data address in the MP3000. The MP3000 will offset the address by the number of words specified by the offset. Note: An offset cannot be a negative value.
Page 266 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  M Register Writing Range (PARAM36 to PARAM39) These parameters set the allowable address range for write requests from the remote station. An error will occur if the write request is outside this allowable range. Specify the M Register Writing Range (PARAM36 to PARAM39) with word addresses.
Page 267 2.8 Communications with an OMRON PLC (FINS Communications Service) Message Functions  For System Use (PARAM48) This parameter is used by the system. It contains the channel number of the communications buffer that is currently in use. A user program must set PARAM48 to 0 on the first scan after startup. Thereafter, do not change the value of PARAM48 from a user program or by any other means.
Page 268: Communications With A Koyo Plc (Modbus/Tcp Protocol)
2.9 Communications with a KOYO PLC (MODBUS/TCP Protocol) Using Automatic Reception with the MP3000 as a Slave Communications with a KOYO PLC (MODBUS/TCP Protocol) When using Ethernet communications between the MP3000 and a KOYO PLC, use the MODBUS/TCP protocol as the communications protocol. The MODBUS/TCP protocol allows the master to read and write to the slave registers.
Page 269 2.9 Communications with a KOYO PLC (MODBUS/TCP Protocol) Using Automatic Reception with the MP3000 as a Slave Setting Example The following figure illustrates how the contents of the R1200 to R1261 hold registers in the KOYO PLC master are written to the MW00000 to MW00049 hold registers in the MP3000 slave. KOYO DL-series PLC MP3000 (remote station)
Page 270 2.9 Communications with a KOYO PLC (MODBUS/TCP Protocol) Using Automatic Reception with the MP3000 as a Slave  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 271 2.9 Communications with a KOYO PLC (MODBUS/TCP Protocol) Using Automatic Reception with the MP3000 as a Slave Set the connection parameters.        Select 1 in the Connect No. Box. Enter “10001” in the Port No. Box for the MP-series Controller. Select MODBUS/TCP protocol in the Communications Protocol Type Box, and then click the Default Button.
Page 272 2.9 Communications with a KOYO PLC (MODBUS/TCP Protocol) Using Automatic Reception with the MP3000 as a Slave Check the settings and double-click the Setting Button in the Detail Column. Select the Enable Option in the Automatically Reception Tab Page and then click the OK Button. Note: 1.
Page 273 2.9 Communications with a KOYO PLC (MODBUS/TCP Protocol) Using Automatic Reception with the MP3000 as a Slave  Setting the Remote Device (KOYO PLC) Use the following procedure to set the KOYO DL-series PLC. The DL-series PLCs are manufactured by KOYO Electronics Industries. Contact KOYO Electronics Industries for further information.
Page 274 2.9 Communications with a KOYO PLC (MODBUS/TCP Protocol) Using Automatic Reception with the MP3000 as a Slave Create a ladder program for communications.  Use the Load (LDS) instruction to specify the base number, ECOM slot number, and server node num- ber.
Page 275: Using I/O Message Communications With The Mp3000 As The Master
2.9 Communications with a KOYO PLC (MODBUS/TCP Protocol) Using I/O Message Communications with the MP3000 as the Master Using I/O Message Communications with the MP3000 as the Master This section describes how to communicate with a KOYO PLC by using I/O message communications. MP3000 KOYO DL-series PLC (local station)
Page 276 2.9 Communications with a KOYO PLC (MODBUS/TCP Protocol) Using I/O Message Communications with the MP3000 as the Master Setting Example The following figure illustrates how the contents of the OW00064 to OW00095 output registers in the MP3000 master are written to the R1300 to R1361 holding registers in the KOYO PLC slave. MP3000 KOYO DL-series PLC (local station)
Page 277 2.9 Communications with a KOYO PLC (MODBUS/TCP Protocol) Using I/O Message Communications with the MP3000 as the Master  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 278 2.9 Communications with a KOYO PLC (MODBUS/TCP Protocol) Using I/O Message Communications with the MP3000 as the Master Select the Enable Option in the I/O Message Communication Area of the Connection Parame- ter settings. Set the connection parameters.   ...
Page 279 2.9 Communications with a KOYO PLC (MODBUS/TCP Protocol) Using I/O Message Communications with the MP3000 as the Master  Setting the Remote Device (KOYO PLC) Use the following procedure to set the KOYO DL-series PLC. The DL-series PLCs are manufactured by KOYO Electronics Industries. Contact KOYO Electronics Industries for further information.
Page 280: Communications With A Jtekt Plc (Toyopuc Protocol)
2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using Automatic Reception with the MP3000 as a Slave 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) When using Ethernet communications between the MP3000 and a JTEKT PLC, use the TOYOPUC proto- col as the communications protocol.
Page 281 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using Automatic Reception with the MP3000 as a Slave Communications Format The MP3000 acts as a slave and receives data and returns a response to the master by using the communi- cations formats for file memory commands that are shown below. Execution of the MSG-RCVE function in the MP3000 ends when a response is returned.
Page 282 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using Automatic Reception with the MP3000 as a Slave Setting Example The following figure illustrates how the contents of the 1002 to 10C9 file memory addresses in the JTEKT PLC master are written to the MW00000 to MW00099 hold registers in the MP3000 slave. MP3000 JTEKT PLC TOYOPUC (local station)
Page 283 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using Automatic Reception with the MP3000 as a Slave  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 284 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using Automatic Reception with the MP3000 as a Slave Set the connection parameters.        Select 1 in the Connect No. Box. Enter “1025” in the Port No. Box for the MP-series Controller. Select TOYOPUC in the Communication Protocol Type Box.
Page 285 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using Automatic Reception with the MP3000 as a Slave Check the settings and double-click the Setting Button in the Detail Column. Select the Enable Option in the Automatically Reception Tab Page and then click the OK Button. Note: 1.
Page 286 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using Automatic Reception with the MP3000 as a Slave  Setting the Remote Device (JTEKT PLC) Use the following procedure to set up the JTEKT TOYOPUC PLC. TOYOPUC PLCs are manufactured by JTEKT Corporation. Refer to the following manual for details.
Page 287 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using Automatic Reception with the MP3000 as a Slave  Starting Communications Use the following procedure to write the data in the file memory in the JTEKT PLC to the hold registers in the MP3000.
Page 288: Using The Msg-Rcve Function With The Mp3000 As A Slave
2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-RCVE Function with the MP3000 as a Slave Using the MSG-RCVE Function with the MP3000 as a Slave This section describes how to communicate with a JTEKT PLC by using the MSG-RCVE function. When a JTEKT PLC is used as the master to write data to the file memory in the 2PORT-EFR, you will need to create a ladder application that uses the SPW instruction.
Page 289 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-RCVE Function with the MP3000 as a Slave Communications Format The MP3000 acts as a slave and receives data and returns a response to the master by using the communi- cations formats for file memory commands that are shown below.
Page 290 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-RCVE Function with the MP3000 as a Slave Setting Example The following figure illustrates how the contents of 200 words from the 3002 to 3191 file memory addresses in the JTEKT PLC master are written to the MW05000 to MW05199 hold registers in the MP3000 slave.
Page 291 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-RCVE Function with the MP3000 as a Slave  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 292 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-RCVE Function with the MP3000 as a Slave Set the connection parameters.        Select 1 in the Connect No. Box. Enter “1025” in the Port No. Box for the MP-series Controller. Select TOYOPUC in the Communication Protocol Type Box.
Page 293 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-RCVE Function with the MP3000 as a Slave Check the settings and double-click the Setting Button in the Detail Column. Click the Disable Option on the Automatically Reception Tab Page. Note: Changes made to the communications or connection parameters will become effective only after the changes have been saved to flash memory and the power supply has been cycled.
Page 294 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-RCVE Function with the MP3000 as a Slave Create a ladder program for the MSG-RCVE function. A ladder program example is shown below. 2-276...
Page 295 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-RCVE Function with the MP3000 as a Slave Save the data to flash memory. This concludes the settings for using the MP3000 as a slave. 2-277...
Page 296 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-RCVE Function with the MP3000 as a Slave  Setting the Remote Device (JTEKT PLC) Use the following procedure to set up the JTEKT TOYOPUC PLC. TOYOPUC PLCs are manufactured by JTEKT Corporation. Refer to the following manual for details.
Page 297 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-RCVE Function with the MP3000 as a Slave Create a ladder program for send data to the send data area in the file memory on network connection 1. Note: Refer to the following manual for information on ladder programming using the SPW instruction. Manual for the 2PORT-EFR Module from JTEKT Corporation This concludes the setup.
Page 298: Using The Msg-Snde Function With The Mp3000 As The Master
2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Using the MSG-SNDE Function with the MP3000 as the Master This section describes how to communicate with a JTEKT PLC by using the MSG-SNDE function. When a JTEKT PLC is used as the master to read data from the file memory in the 2PORT-EFR, you will need to create a ladder application that uses the SPR instruction.
Page 299 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-SNDE Function with the MP3000 as the Master File Memory and Corresponding Registers in the MP3000 The following table shows the relationship between registers in the MP3000 and the receive data area of file memory in the 2PORT-EFR.
Page 300 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Setting Example The following figure illustrates how the contents of the 300 words from the MW30000 to MW30299 hold registers in the MP3000 master are written to the 5802 to 5A59 file memory addresses in the JTEKT PLC slave.
Page 301 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-SNDE Function with the MP3000 as the Master  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 302 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Set the connection parameters.        Select 1 in the Connect No. Box. Enter “1025” in the Port No. Box for the MP-series Controller. Select TOYOPUC in the Communication Protocol Type Box.
Page 303 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Check the settings and double-click the Setting Button in the Detail Column. Click the Disable Option on the Automatically Reception Tab Page. Note: Changes made to the communications or connection parameters will become effective only after the changes have been saved to flash memory and the power supply has been cycled.
Page 304 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Create a ladder program for the MSG-SNDE function. A ladder program example is shown below. 2-286...
Page 305 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-SNDE Function with the MP3000 as the Master 2-287...
Page 306 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Save the data to flash memory. This concludes the settings for using the MP3000 as the master. 2-288...
Page 307 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-SNDE Function with the MP3000 as the Master  Setting the Remote Device (JTEKT PLC) Use the following procedure to set up the JTEKT TOYOPUC PLC. TOYOPUC PLCs are manufactured by JTEKT Corporation. Refer to the following manual for details.
Page 308 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Using the MSG-SNDE Function with the MP3000 as the Master Create a ladder program for receive data from the receive data area in the file memory on net- work connection 5. Note: Refer to the following manual for information on ladder programming using the SPR instruction. Manual for the 2PORT-EFR Module from JTEKT Corporation This concludes the setup.
Page 309: Message Functions
2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions Message Functions The message functions are used in user communications applications for the TOYOPUC protocol. You can send and receive message data by setting the necessary input items and parameters for the message functions.
Page 310 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Abort Specify the bit to use to abort the message transmission. When the Abort Bit turns ON, the message transmission will be stopped unconditionally. The Abort Bit takes precedence over the Execute Bit. ...
Page 311 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Ch-No (Communications Buffer Channel Number) Specify the channel number of the communications buffer. You can specify any channel number provided it is within the valid range. When executing more than one function at the same time, do not use the same channel number for the same connection.
Page 312 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Busy Specify the bit that shows that the message transmission is in progress. The Busy Bit is ON while a message transmission or abort is in progress. Keep the Execute Bit or Abort Bit turned ON while the Busy Bit is ON. ...
Page 313 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions • Execution When an Error Occurs To send another message, turn OFF the Execute Bit for at least one scan after the error occurs. Input: Execute Input: Abort Output: Busy Output: Complete Output: Error 1 scan...
Page 314 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions Continued from previous page. Meaning Description − For system use − Reserved for system. − − Reserved for system. − Reserved for system. − Reserved for system.  Processing Result (PARAM00) This parameter gives the processing result.
Page 315 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  RESULT These bits give the execution result of the MSG-SNDE function. Code Abbreviation Meaning The message send failed or connection ended with an error in Ethernet communi- CONN_NG cations. SEND_OK The message was sent normally.
Page 316 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Detail Error Code (PARAM02 and PARAM03) These parameters give the detail error code. Processing Detail Result Value Error Error Description Description (PARAM00) Code An unused function code was sent or received. 81...
Page 317 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Status 2 (PARAM05) This parameter gives information on the most recent error. Status 2 Value Meaning Description No error Normal Socket Creation Error A socket could not be created. Local Port Number Error Setting error in local station port number.
Page 318 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Connection Number (PARAM10) Specify the remote station. If the communications device is the 218IFD, enter the connection number. The valid setting range is given in the following table. Communications Device Connection Number Description Specifies the connection number of the remote station to...
Page 319 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Remote Station Data Address (PARAM14 and PARAM15) Set the first address for data in the remote station. Enter the first address as a decimal or hexadecimal number. If the first address is MW01000, enter “1000” (decimal) or “3E8” (hexadecimal). Example MP3000 2PORT-EFR...
Page 320 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Local Station Register Type (PARAM22) Set the register type of the read data destination or write data source in the MP3000. Register Type Value Type Remarks Sets the target data type to MB for bits and MW for words. Sets the target data type to GB for bits and GW for words.
Page 321 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions Inputs and Outputs for the MSG-RCVE Function Function MSG-RCVE Name Receives a message from a remote station on the specified circuit of the communications device Function type. This function can be used with various protocols. MSG-RCVE Execute Busy...
Page 322 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Dev-Typ (Communications Device Type) Specify the type code of the communications device. Device Type Code 218IFD  Pro-Typ (Communications Protocol) Specify the type code of the communications protocol. Type Code Communications Protocol Remarks Select this protocol when using the TOYOPUC protocol.
Page 323 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Ch-No (Communications Buffer Channel Number) Specify the channel number of the communications buffer. You can specify any channel number provided it is within the valid range. When executing more than one function at the same time, do not use the same channel number for the same connection.
Page 324 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Busy Specify the bit that shows that the message reception is in progress. The Busy Bit is ON while a message reception or abort is in progress. Keep the Execute Bit or Abort Bit turned ON while the Busy Bit is ON. ...
Page 325 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions • Execution When an Error Occurs To receive another message, keep the Execute Bit ON even after the error occurs. Input: Execute Input: Abort Output: Busy Output: Complete Output: Error 1 scan MSG-RCVE Function Parameters The following table describes the contents of the addresses specified by the PARAM input parameter to...
Page 326 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions Continued from previous page. Meaning Description Sets the connection number used to determine the 10 Inputs Connection Number remote station. 11 I/O Option Not used for the TOYOPUC protocol. Gives the function code requested by the remote 12 Outputs Function Code station.
Page 327 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Processing Result (PARAM00) This parameter gives the processing result. Processing Result Value Meaning 00xx hex Busy 10xx hex Complete 8yxx hex Error Note: The lower byte is used for system analysis. Refer to the following section for details on errors.
Page 328 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  COMMAND These bits indicate the processing command of the MSG-RCVE function. Code (Hex) Abbreviation Meaning General-purpose message transmission (for no-protocol communi- U_SEND cations) General-purpose message reception (for no-protocol communica- U_REC tions) ABORT...
Page 329 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions Continued from previous page. Processing Detail Result Value Error Error Description Description (PARAM00) Code Connection number The connection number is out of range. Check PARAM10 86 hex error (Connection Number). An error response was received from the communications Communications 88...
Page 330 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Status 4 (PARAM07) This parameter gives the value of the receive pass counter. Status 4 Value Meaning Description 0 to 65535 Receive Count Counts the number of times a message was received. ...
Page 331 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Function Code (PARAM12) This parameter gives the function code that was received. When the MP3000 receives the file memory data sent from the 2PORT-EFR, the data is converted to the format specified in MEMOBUS command 31 hex and sent to the CPU Module.
Page 332 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  Offsets (PARAM20 to PARAM27) These parameters set the offset for the data address in the MP3000. The MP3000 will offset the address by the number of words specified by the offset. Note: An offset cannot be a negative value.
Page 333 2.10 Communications with a JTEKT PLC (TOYOPUC Protocol) Message Functions  G Register Writing Range LO (PARAM40 and PARAM41) These parameters are not used for the TOYOPUC protocol.  G Register Writing Range HI (PARAM42 and PARAM43) These parameters are not used for the TOYOPUC protocol. ...
Page 334: Communications With A Windows Pc (Fa-Server)
2.11 Communications with a Windows PC (FA-Server) Using Automatic Reception with the MP3000 as a Slave 2.11 Communications with a Windows PC (FA-Server) The MP3000 can communicate with a Windows PC running FA-Server over an Ethernet connection by using automatic reception. This section describes communications when the MP3000 acts as a slave.
Page 335 2.11 Communications with a Windows PC (FA-Server) Using Automatic Reception with the MP3000 as a Slave Setting Example The following figure illustrates how the contents of the MW00000 to MW00003 hold registers in the MP3000 slave are displayed on a form created in Microsoft Visual Basic 6.0 via FA-Server, and how to write values to the same registers by pressing the corresponding Write Button on the same form.
Page 336 2.11 Communications with a Windows PC (FA-Server) Using Automatic Reception with the MP3000 as a Slave  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 337 2.11 Communications with a Windows PC (FA-Server) Using Automatic Reception with the MP3000 as a Slave Set the connection parameters.        Select 1 in the Connect No. Box. Enter “10001” in the Port No. Box for the MP-series Controller. Select Extended MEMOBUS in the Communications Protocol Type Box, and then click the Default Button.
Page 338 2.11 Communications with a Windows PC (FA-Server) Using Automatic Reception with the MP3000 as a Slave Check the settings and double-click the Setting Button in the Detail Column. Select the Enable Option in the Automatically Reception Tab Page and then click the OK Button. Note: 1.
Page 339 From the tree view on the left side, right-click Driver just below Tag, and select Add unit. From the list of drivers, select Yaskawa Electric Corporation − Ethernet - CP9200SH/MP920*** 218IF. Right-click the Unit added by clicking Add unit, in this example U01, and select Property.
Page 340 2.11 Communications with a Windows PC (FA-Server) Using Automatic Reception with the MP3000 as a Slave In addition to the connection method, set up the DDE* or OPC properties just below Interface in the tree view on the left side. * For DDE, make sure that the Topic Name check box is selected on the Basic Setting Tab Page of the Property Dialog Box.
Page 341 2.11 Communications with a Windows PC (FA-Server) Using Automatic Reception with the MP3000 as a Slave • Using OPC in Visual Basic Turn ON the power to the MP3000 that you set up. Place the FA-Server that you set up in online status. ...
Page 342: Communications With A Windows Pc (Visual Basic Application)
2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave 2.12 Communications with a Windows PC (Visual Basic Application) The MP3000 can communicate with a Windows PC running a Visual Basic application over an Ethernet connection by using automatic reception.
Page 343 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave Setting Example The following figure illustrates how the contents of the MW00000 to MW00009 hold registers in the MP3000 slave are displayed on an application form created in Microsoft Visual Basic.NET 2003. MP3000 PC (Visual Basic) (local station)
Page 344 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 345 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave Set the connection parameters.        Select 1 in the Connect No. Box. Enter “10001” in the Port No. Box for the MP-series Controller. Select Extended MEMOBUS in the Communications Protocol Type Box, and then click the Default Button.
Page 346 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave Check the settings and double-click the Setting Button in the Detail Column. Select the Enable Option in the Automatically Reception Tab Page and then click the OK Button. Note: 1.
Page 347 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave  Setting the Other Device (Windows PC Running a Visual Basic Applica- tion) The following section outlines a Visual Basic application for connecting the MP3000 and a PC, and describes a sample program.
Page 348 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave  Visual Basic Application Example A program example is shown below. The Winsock socket library is required to run this program. Note •...
Page 349 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave '---- Get the MP3000’s IP address. ---- DstPort = Val(TextBox10.Text) '---- Get the connection type ---- TransPort = ComboBox1. SelectedIndex ' 0:TCP 1:UDP '---- Open a TCP/UDP port ---- rc = MemobusMasterMain(TransPort, MyIP, MyPort, DstIP, DstPort) If rc = 0 Then...
Page 350 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave • Programming Example for Extended MEMOBUS Protocol Message Communications The programming example that is given below demonstrates how to manage sockets and perform mes- sage communications using the Extended MEMOBUS protocol.
Page 351 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave If (sock < 0) Then MsgBox("Socket error " & WSAGetLastError()) Return -1 End If '---- Bind the local port number and socket ---- rc = bind(sock, PC_addr, Len(PC_addr)) If (rc <>...
Page 352 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave rc = 0 '---- Send command data ---- slen = send(sock, Ssbuf, DATAi ∗ 2, 0) If (slen <> DATAi ∗ 2) Then MsgBox("send error "...
Page 353 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave '---- Receive response data ---- Srbuf = Space(4096) from_len = Len(PC_addr) rlen = recvfrom(sock, Srbuf, 4096, 0, PC_addr, from_len) If (rlen <= 0) Then MsgBox("receive error "...
Page 354 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave '---- Clear buffers to zero ---- For i = 0 To 4095 sbuf(i) = 0 Next '---- Create the 218 header part ---- '---- Set the register type.
Page 355 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave '---- Set the reference number ---- sbuf(18) = CByte(Adr And &HFF) 'Adr(L) sbuf(19) = CByte((Adr And &HFF00)\256) 'Adr(H) '---- Set the number of registers ---- sbuf(20) = CByte(DataNum And &HFF) 'DataNum(L) sbuf(21) = CByte((DataNum And &HFF00) \256) 'DataNum(H)
Page 356 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave '---- Check the serial number ---- If (sbuf(1) <> rbuf(1)) Then rc = -3 Return (rc) End If '---- Check the total data length of the message ---- Select Case sbuf(15) Case &H9 rcvDATAi = Val(Str(sbuf(21)) &...
Page 357 2.12 Communications with a Windows PC (Visual Basic Application) Using Automatic Reception with the MP3000 as a Slave  Starting Communications Use the following procedure to communicate between the Visual Basic application on the PC and the MP3000. Turn ON the power to the MP3000 to start receiving messages. The system will automatically start the message reception operation.
Page 358: Communications With A Windows Pc (Visual C++ Application)
2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave 2.13 Communications with a Windows PC (Visual C++ Application) The MP3000 can communicate with a Windows PC running a Visual C++ application over an Ethernet connection by using automatic reception.
Page 359 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave Setting Example The following figure illustrates how the contents of the MW00000 to MW00009 hold registers in the MP3000 slave are displayed on a form created in Microsoft Visual C++. MP3000 PC (Visual C++) (local station)
Page 360 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave  MP3000 Setup Use the following procedure to set up the MP3000. If the communications parameters (IP address and subnet mask) have already been set, skip to step 3. Note Double-click the cell for 218IFD in the Module Configuration Definition Tab Page.
Page 361 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave Set the connection parameters.        Select 1 in the Connect No. Box. Enter “10001” in the Port No. Box for the MP-series Controller. Select Extended MEMOBUS in the Communications Protocol Type Box, and then click the Default Button.
Page 362 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave Check the settings and double-click the Setting Button in the Detail Column. Select the Enable Option in the Automatically Reception Tab Page and then click the OK Button. Note: 1.
Page 363 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave  Setting the Other Device (Windows PC Running a Visual C++ Application) The following section outlines a Visual C++ application for connecting the MP3000 and a PC, and describes a sample program.
Page 364 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave  Visual C++ Application Example A program example is shown below. The Winsock socket library is required to run this program. Note •...
Page 365 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave namespace VC_SAMPLE // Functions and variables referenced from external files extern "C"{ extern int memobus_master_main( unsigned short trans_prt, unsigned long myip, unsigned short myport, unsigned long dstip, unsigned short dstport );...
Page 366 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave // Get the PC’s port number. // Add code to get the port number from TextBox5. Example: MyPort: 10001 // Get the MP3000’s IP address // Add code to get the IP address from TextBox6, TextBox7, TextBox8, and TextBox9.
Page 367 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave • Programming Example for Extended MEMOBUS Protocol Message Communications The programming example that is given below demonstrates how to manage sockets and perform mes- sage communications using the Extended MEMOBUS protocol.
Page 368 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave // Initialize serial number setting iSerial = 0x00; // Clear the sockaddr structure (IP address, port number, etc.) with zeros. memset( (char ∗)&my, 0, sizeof(struct sockaddr)); memset( (char ∗)&dst, 0, sizeof(struct sockaddr));...
Page 369 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave rc = -3; return( rc ); return(rc); /∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗/ /∗ Send command data, receive response data ∗/ /∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗/ int memobus_msg( unsigned short trans_prt, char∗ sbuf, char∗ rbuf ) int rc;...
Page 370 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave rc = -2; return ( rc ); // Check response data rc = chk_rsp_data( rlen, sbuf, rbuf ); if ( rc != 0 ) //Error in received data closesocket(sd);...
Page 371 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave return ( rc ); iSerial++; // Increment the serial number of the 218 header return ( rc ); /∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗/ /∗ Create Extended MEMOBUS protocol command ∗/ /∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗/ void mk_cmd_data( unsigned char SFC, unsigned char CPUNum,...
Page 372 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave // Set the total number of data items from the start of the 218 header to the end of MEMOBUS data sbuf[6] = (unsigned char)(DATAi & 0x00FF); // Data length (L) sbuf[7] = (unsigned char)((DATAi &...
Page 373 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave rcvDATAi = 20 + ( (sbuf[21] << 8) | sbuf[20] ) ∗ 2; if ( rlen != rcvDATAi ) rc = -3; return( rc );...
Page 374 2.13 Communications with a Windows PC (Visual C++ Application) Using Automatic Reception with the MP3000 as a Slave // Check the number of registers switch ( sbuf[15] ) case 0x09: if (( rbuf[18] != sbuf[20] ) || (rbuf[19] != sbuf[21] )) rc = -9;...
Page 375: Communications Buffer Channels
2.14 Communications Buffer Channels 2.14 Communications Buffer Channels A communications buffer channel is a data buffer that interfaces the MSG-SNDE or MSG-RCVE function with the communications device. This data buffer consists of one or more channels. Each channel is iden- tified by a communications buffer channel number.
Page 376 2.14 Communications Buffer Channels Remote device #1 Remote device #2 MP3000 Ethernet Ethernet Ethernet Local station IP address Node IP Address Node IP Address 192.168.1.y 192.168.1.x 192.168.1.z Ethernet Network Configuration The connection is set in the Transmission Parameters Tab Page of the MPE720 Module Configuration Definition Dialog Box.
Page 377: Using Message Functions
2.15 Using Message Functions Function Codes 2.15 Using Message Functions You can use any registered function by specifying the corresponding function code in the message func- tion. This section describes the function codes and how to use them. Function Codes The following tables list the function codes for each protocol.
Page 378: Using Function Codes
2.15 Using Message Functions Using Function Codes Function Codes for the QnA-compatible 3E Frame Protocol Function Code Function 01 or 02 hex Reads bit devices in units of one point. 03, 04, 09, or 0A hex Reads word devices in units of one point. 05 or 0F hex Writes bit devices in units of one point.
Page 379 2.15 Using Message Functions Using Function Codes Continued from previous page. MSG-SNDE Function Parameter Description Remote CPU Module This parameter is used with the Extended MEMOBUS protocol. Set the PARAM18 Number CPU number at the remote station. Local Station Data PARAM20 Set the first register address to store the read data in the local station.
Page 380 2.15 Using Message Functions Using Function Codes Function Codes: 05, 06, 0B, 0F, and 10 Hex Function: Writes data. The specified size of data is read from registers in the local station and written to specified registers in the remote station. The following parameters need to be set in the MSG-SNDE function.
Page 381 2.15 Using Message Functions Using Function Codes The following example illustrates how the states of multiple coils are changed by using function code 0F hex. In this example, 400 bits of data starting from register OB120000 in the local station are written to registers starting at MB00010000 in the remote station.
Page 382 2.15 Using Message Functions Using Function Codes Function Code: 0D Hex Function: Reads data from multiple specified registers, one point at a time. Data is read one word at a time from registers in the remote station as specified in the remote station address table that is stored in registers in the local station.
Page 383 2.15 Using Message Functions Using Function Codes MP3000-series Controller (Send: master) MP3000-series Controller (Receive: slave) MSG-RCVE Function MSG-SNDE Function Parameter List Use connection number 1. Parameter List M registers 0001 hex MW0000000 0001 hex Use connection number 1. FC = 0D hex: Reads 0000 hex 0000 hex the contents of...
Page 384 2.15 Using Message Functions Using Function Codes Continued from previous page. MSG-SNDE Function Parameter Description Local Station Data These parameters are used to offset the address for reading data from PARAM20 Address, Lower Word registers in the local station for writing in the remote station. Data will be read from the addresses that are the sum of each address specified in Local Station Data PARAM21...
Page 385 2.15 Using Message Functions Using Function Codes Function Codes: 4341 and 4349 Hex Function: Reads data from a data address in the remote station specified with a 32-bit address. The specified size of data is read from specified registers in the remote station and stored in regis- ters in the local station.
Page 386 2.15 Using Message Functions Using Function Codes If the output register offset parameters in the MSG-RCVE function are set to a non-zero value, the actual addresses that are read in the remote station will be the sum of the remote station data addresses and the value in the output register offset parameters.
Page 387 2.15 Using Message Functions Using Function Codes MP3000-series Controller (Send: master) MP3000-series Controller (Receive: slave) MSG-RCVE Function MSG-SNDE Function Parameter List Use connection number 1. Parameter List Use connection number 1. 0001 hex 0001 hex 0000 hex FC = 434F hex: G registers 0000 hex I registers...
Page 388 2.15 Using Message Functions Using Function Codes Continued from previous page. MSG-SNDE Function Parameter Description Local Station Register Set the register type (M or G) where the read data is to be stored in the PARAM22 Type local station. Set this parameter to 0 from a user program or by other means in the PARAM24 For system use first scan after the power is turned ON.
Page 389 2.15 Using Message Functions Using Function Codes Function Code: 434E Hex Function: Writes data to multiple registers specified by a 32-bit address, one point at a time. Data is written one or two words at a time in registers in the remote station as specified in the remote station address table that is stored in registers in the local station.
Page 390 2.15 Using Message Functions Using Function Codes Remote Station Address Table Register type Data type 4 words per data item Address low setting Address high setting +4n-4 Register type Register type: 0 = M registers +4n-3 Data type 1 = G registers 2 = I registers Address low setting +4n-2...
Page 391 2.15 Using Message Functions Using Function Codes Function Code: 31 Hex Function: Writes to the fixed buffer in a Mitsubishi PLC, or to the file memory in a TEKT PLC. The specified size of data is read from registers in the local station and written to registers in the remote station.
Page 392 2.15 Using Message Functions Using Function Codes 1. If the data is being received by an MP3000 slave, the data will be written to the addresses that are specified by the hold register offset parameters in the MSG-RCVE function. 2. Set the address of the register to write to within the range specified by the M Register Writing Note Range Low and M Register Writing Range High parameters in the MSG-RCVE function.
Page 393 2.15 Using Message Functions Using Function Codes MP3000-series Controller (Send: master) Mitsubishi PLC (Receive: slave) MSG-SNDE Function Parameter List Use connection number 1. 0001 hex Random FC=32 access buffer M registers 0000 hex MW0000000 00000 0032 hex 0000 hex 000A hex Local station 00010 0000 hex...
Page 394 2.15 Using Message Functions Using Function Codes The following example illustrates how to write to the random access buffer by using function code 33 hex. In this example, 600 words of data starting from register IW05000 in the local station are written to regis- ters starting at 00016 in the remote station.
Page 395 2.15 Using Message Functions Using Function Codes Continued from previous page. MSG-SNDE Function Parameter Description Local Station Register Set the register type (M, G, I, O, or S) of the data to be written that is PARAM22 Type stored in the local station. Set this parameter to 0 from a user program or by other means in the PARAM24 For system use...
Page 396: Details On Protocols
2.16 Details on Protocols Extended MEMOBUS Protocol 2.16 Details on Protocols This section provides details on the Extended MEMOBUS protocol, MEMOBUS protocol, and no-proto- col communications. Extended MEMOBUS Protocol Message Structure The following message structure is used in Ethernet communications. Use this as reference when develop- ing a PC-based application.
Page 397 2.16 Details on Protocols Extended MEMOBUS Protocol  218 Header When communicating with the Extended MEMOBUS protocol, a 12-byte header called the 218 header is appended before the application data. The following figure describes the elements of the 218 header. 11 hex: MEMOBUS command 7 •...
Page 398 2.16 Details on Protocols Extended MEMOBUS Protocol  Register Types When the major function code is 43 hex and the function specified by the sub function code references the contents of a register, such as a read, write, or change of state, specify the target register type in the slave. The codes for register types are given below.
Page 399 2.16 Details on Protocols Extended MEMOBUS Protocol MEMOBUS Binary Mode The following formats are used for MEMOBUS message communications in Binary Mode.  Reading the States of Coils Command 7 • • • • • • • • • 0 Set the length of the command.
Page 400 2.16 Details on Protocols Extended MEMOBUS Protocol  Reading the States of Input Relays Command 7 • • • • • • • • • 0 Set the length of the command. Length: 07 hex MFC: 20 hex Always 20 hex. SFC: 02 hex The sub function code to read the states of relays is 02 hex.
Page 401 2.16 Details on Protocols Extended MEMOBUS Protocol  Reading the Contents of Input Registers Command 7 • • • • • • • • • 0 Set the length of the command. Length: 07 hex MFC: 20 hex Always 20 hex. SFC: 04 hex The sub function code to read the contents of input registers is 04 hex.
Page 402 2.16 Details on Protocols Extended MEMOBUS Protocol  Writing to a Single Hold Register Command 7 • • • • • • • • • 0 Set the length of the command. Length: 07 hex Always 20 hex. MFC: 20 hex The sub function code to change the contents of a single hold register is 06 hex.
Page 403 2.16 Details on Protocols Extended MEMOBUS Protocol  Reading the Contents of Hold Registers (Extended) Command 7 • • • • • • • • • 0 Set the length of the command. Length: 08 hex Always 20 hex. MFC: 20 hex The sub function code to read the contents of hold registers is 09 hex.
Page 404 2.16 Details on Protocols Extended MEMOBUS Protocol Response 7 • • • • • • • • • 0 Length: 06 hex + Set the length of the response. Number of registers x 2 MFC: 20 hex Always 20 hex. SFC: 0A hex The response will contain the sub function code that was set in the command.
Page 405 2.16 Details on Protocols Extended MEMOBUS Protocol  Reading the Contents of Non-consecutive Hold Registers (Extended) Command 7 • • • • • • • • • 0 Set the length of the command. Length: 06 hex + Number of registers x 2 Always 20 hex.
Page 406 2.16 Details on Protocols Extended MEMOBUS Protocol  Writing to Non-consecutive Hold Registers (Extended) Command 7 • • • • • • • • • 0 Set the length of the command. Length: 06 hex + Number of registers x 4 MFC: 20 hex Always 20 hex.
Page 407 2.16 Details on Protocols Extended MEMOBUS Protocol Response 7 • • • • • • • • • 0 Set the length of the response. Length: 07 hex Always 20 hex. MFC: 20 hex SFC: 0F hex The response will contain the sub function code that was set in the command. Specify 4 bits each for the destination CPU number and the source CPU number.
Page 408 2.16 Details on Protocols Extended MEMOBUS Protocol  Reading the States of Bits Using 32-bit Addressing Command 7• • • • • • • • • • 0 Set the length of the command. Length: 0C hex MFC: 43 hex Always 43 hex.
Page 409 2.16 Details on Protocols Extended MEMOBUS Protocol  Changing the State of a Single Bit Using 32-bit Addressing Command 7• • • • • • • • • • 0 Set the length of the command. Length: 0C hex MFC: 43 hex Always 43 hex.
Page 410 2.16 Details on Protocols Extended MEMOBUS Protocol  Writing to a Single Register Using 32-bit Addressing Command 7• • • • • • • • • • 0 Set the length of the command. Length: 0C hex MFC: 43 hex Always 43 hex.
Page 411 2.16 Details on Protocols Extended MEMOBUS Protocol  Reading the Contents of Registers Using 32-bit Addressing Command 7• • • • • • • • • • 0 Set the length of the command. Length: 0C hex MFC: 43 hex Always 43 hex.
Page 412 2.16 Details on Protocols Extended MEMOBUS Protocol  Writing to Multiple Registers Using 32-bit Addressing Command 7• • • • • • • • • • 0 Set the length of the command. Length: 0C hex + Number of registers x 2 MFC: 43 hex Always 43 hex.
Page 413 2.16 Details on Protocols Extended MEMOBUS Protocol  Reading the Contents of Non-consecutive Registers Using 32-bit Address- Command 7• • • • • • • • • • 0 Set the length of the command. Length: 06 hex + Number of registers x 6 MFC: 43 hex Always 43 hex.
Page 414 2.16 Details on Protocols Extended MEMOBUS Protocol  Writing to Non-consecutive Registers Using 32-bit Addressing Command 7• • • • • • • • • • 0 Length: 06 hex + Number of Set the length of the command. word registers x 8 + Number of long word registers x 10 Always 43 hex.
Page 415 2.16 Details on Protocols Extended MEMOBUS Protocol  Changing the States of Multiple Bits Using 32-bit Addressing Command 7• • • • • • • • • • 0 Set the length of the command. Length: 0E hex + ((number of bits + 7)/8) Always 43 hex.
Page 416 2.16 Details on Protocols Extended MEMOBUS Protocol  Error Responses  Major Function Code of 20 Hex The following message is returned. • The sub function code in the command message is illegal. • The reference address is illegal. • The number of data items is incorrect. Command 7 •...
Page 417 2.16 Details on Protocols Extended MEMOBUS Protocol  Major Function Code of 43 Hex The following message is returned. • The register type is incorrect. • The command is incorrect for the data type to be accessed. • The local register type is incorrect. Command 7•...
Page 418 2.16 Details on Protocols Extended MEMOBUS Protocol MEMOBUS ASCII Mode In ASCII Mode, binary data is converted to ASCII before being sent or received. The following diagram illustrates the conversion from binary to ASCII. As shown in the example, 8-bit data is converted into two 7-bit ASCII characters.
Page 419 2.16 Details on Protocols Extended MEMOBUS Protocol General-purpose Message ASCII Mode In ASCII Mode, binary data is converted to ASCII before being sent or received. The following diagram illustrates the conversion from binary to ASCII. As shown in the example, 8-bit data is converted into two 7-bit ASCII characters.
Page 420: Memobus Protocol
2.16 Details on Protocols MEMOBUS Protocol MEMOBUS Protocol Message Structure The following message structure is used in communications with 217IF and 218IF Modules. Refer to the following manual for details. MEMOBUS Descriptive Information Industrial Communication System (Manual No. SIE-C815-13.60) When the MEMOBUS protocol is used to send and receive data, each message consists of two fields: a header field and the application data field.
Page 421 2.16 Details on Protocols MEMOBUS Protocol  MEMOBUS Command The commands that make up the MEMOBUS messages are identified by function codes and provide the func- tions given in the following table. Sub Function Function Code Function Code − 01 hex Reads the states of coils.
Page 422 2.16 Details on Protocols MEMOBUS Protocol MEMOBUS RTU Mode When a message is received on a 218IFD Module using the MEMOBUS protocol, the CRC-16 is not checked. Note  Reading the States of Coils Command 7 • • • • • • • • • 0 Slave address The function code to read the states of coils is 01 hex.
Page 423 2.16 Details on Protocols MEMOBUS Protocol  Reading the Contents of Hold Registers Command 7 • • • • • • • • • 0 Slave address The function code to read the contents of hold registers is 03 hex. Function code: 03 hex Set the first address of the hold registers to read.
Page 424 2.16 Details on Protocols MEMOBUS Protocol  Changing the State of a Single Coil Command 7 • • • • • • • • • 0 Slave address The function code to change the state of a single coil is 05 hex. Function code: 05 hex Set the address of the coil to change the state of.
Page 425 2.16 Details on Protocols MEMOBUS Protocol  Performing a Loopback Test Command 7 • • • • • • • • • 0 Slave address Function code: 08 hex The function code to perform a loopback test is 08 hex. Set the test code.
Page 426 2.16 Details on Protocols MEMOBUS Protocol  Writing to Multiple Hold Registers Command 7 • • • • • • • • • 0 Slave address The function code to write to hold registers is 10 hex. Function code: 10 hex Set the first address of the hold registers to change.
Page 427 2.16 Details on Protocols MEMOBUS Protocol MEMOBUS ASCII Mode In ASCII Mode, RTU data is converted to ASCII before being sent or received. The following diagram illustrates the conversion from RTU to ASCII. As shown in the example, 8-bit data in the application data field is converted into two 7-bit ASCII characters.
Page 428: No-Protocol Communications
2.16 Details on Protocols No-protocol Communications No-protocol Communications Message Structure When no-protocol communications is set as the communications protocol, application data is handled as a general-purpose message. When sending and receiving data, each message consists of two fields: a header and the application data field.
Page 429 2.16 Details on Protocols No-protocol Communications General-purpose ASCII Mode In ASCII Mode, binary data is converted to ASCII before being sent or received. The following diagram illustrates the conversion from binary to ASCII. As shown in the example, 8-bit data is converted into two 7-bit ASCII characters. Command Command 12 hex...
Page 430 Index Index using the MSG-SNDE function with the MP3000 as the master - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-280 communications format - - - - - - - - - - - - - - - - - - - - - - - 2-280 file memory and corresponding registers...
Page 431 Index QnA-compatible 3E Frame commands using the MP3000 as a router - - - - - - - - - - - 2-139 - - - - - - - - - - - - - - - - - - 2-222 setting example using the MP3000 as a slave - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-141...
Page 432 Index using I/O message communications with the MP3000 Abort - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-60 as the master - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-42 Busy...
Page 433 Index no-protocol - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-411 general-purpose ASCII mode - - - - - - - - - - - - - - - - - - 2-412 general-purpose binary mode - - - - - - - - - - - - - - - - - - 2-411...
Page 434: Revision History
Revision History The revision dates and numbers of the revised manuals are given on the bottom of the back cover. MANUAL NO. SIEP C880725 12B <1>-0 WEB revision number Revision number Published in Japan July 2014 Date of publication Date of Rev.
Page 435 Phone: +81-4-2962-5151 Fax: +81-4-2962-6138 http://www.yaskawa.co.jp YASKAWA AMERICA, INC. 2121, Norman Drive South, Waukegan, IL 60085, U.S.A. Phone: +1-800-YASKAWA (927-5292) or +1-847-887-7000 Fax: +1-847-887-7310 http://www.yaskawa.com YASKAWA ELÉTRICO DO BRASIL LTDA. 777, Avenida Piraporinha, Diadema, São Paulo, 09950-000, Brasil Phone: +55-11-3585-1100 Fax: +55-11-3585-1187 http://www.yaskawa.com.br...

This manual is also suitable for:

Mp2000 series

YASKAWA MP3000 Series User Manual

Quick Links

Related Manuals for YASKAWA MP3000 Series

Summary of Contents for YASKAWA MP3000 Series

This manual is also suitable for:

Table of Contents