Motion control systems consist of three main components: a controller, an amplifier and the motor itself. These three components must work together in harmony to ensure high performance and ease-of-use. This article will examine the latest Yaskawa product offerings in these three areas. It will show how these products work individually, and how they work together in an integrated motion control system.
This document explains how to configure AB ControlLogix 5555 PLC using RSLogix 5000 Software as an EtherNet/IP scanner with an MPiec Series Controller as an adapter. A simple example showing how to verify communication is also provided in the document. Sample code for both devices is provided
This document highlights the steps involved in configuring the AB MicroLogix 1100 PLC as a scanner to communicate with an MPiec controller as an adapter. A simple test to verify communication is explained in this document. Attached are example files for the MicroLogix 1100 (YASK_final.RSS) and MPiec (SlaveCode.zwe).
This application note describes how to configure an AB CompactLogix PLC as a scanner and an MPiec controller as an adapter to facilitate EtherNet/IP communication. A step by step procedure is provided. An example of data transfer is also shown in this document.
This document describes in detail the various steps to configure a Phoenix MODBUS bus coupler to communicate with the MPiec. The bus coupler can be configured through its web interface. The data block addresses and function codes that can be used on the MPiec are also listed in this document.
This document highlights the various steps to configure and use the Phoenix PWM module with the MPiec controller over MECHATROLINK II to get pulse or step and direction output. A sample program that explains how the control word can be used to obtain motion on a step and direction drive is also provided.
This application note describes the configurations required to set up a Pro-face AGP HMI to communicate with an MPiec motion controller. The HMI is a client and the MPiec controller is a server in this MODBUS protocol
This application note describes how to create an Ethernet connection between the MPiec series machine controllers and PanelView Plus HMIs from Rockwell. The document describes example code that has been created for MotionWorks IEC Express, KEPServer Enterprise and RSView Studio 4.0. Users can find the example files and also an eLearning Video describing the same technique at eLV.MP2000iec.01.IECtoPVPlusHMI.
This document describes the configuration required on an MPiec controller (if used as a scanner), configuration required on the scanner device (if the MPiec controller is used as an adapter) and the configuration of ports on an 1800 series Cisco router to enable EtherNet/IP communication between an MPiec controller and a third party device on a different sub network.
This document explains the steps required to configure a TP series HMI using Visu+ to communicate to an MPiec series controller over MODBUS TCP. The HMI is the client and the MPiec controller is the server in this protocol.
This document explains the steps required to configure a Maple HMI using EZ Ware to communicate to an MPiec series controller over MODBUS TCP. The HMI is the client and the MPiec controller is the server in this protocol.