Redlion MPiec Modbus Configuration W Crimson2 v007

Technical Note
QuickStart Guide
Configuring a RedLion HMI to communicate with an

MPiec Controller via MODBUS/TCP using
Crimson 2
Applicable Product: MPiec, RedLion G310 HMI
Doc#: AN.MCD.08.122 Copyright Yaskawa Electric America 2008 September 23, 2013
Page 1 of 10
Subject: Tech Note and Sample Code Product: MPiec Doc#: AN.MCD.08.122
Title: Quickstart guide to configure RedLion HMI and MPiec controller communication via MODBUS
Table of Contents
1. Application Overview: ..................................................................................................... 3

2. Configuration Procedure ................................................................................................. 4
3. HMI variables .................................................................................................................. 9
4. MotionWorks IEC variable declaration .......................................................................... 13
5. Execution ...................................................................................................................... 14
September 23, 2013 Page 2 of 14

1. Application Overview:
This document is intended to guide a user through the steps of configuring a RedLion HMI as a MODBUS master
communicating with the MPiec controller as a slave. This application note was created with a G310 series HMI
with Crimson 2.0 software. The MPiec controller has firmware version 1.0.0.1 and MotionWorks IEC Express
software version 1.0.0.1.
Figure1: Overview of test set up

Products Used:
Controller Yaskawa MPiec controller
Hardware Sigma series servopack and motor, RedLion G310 HMI, Ethernet switch
Software MotionWorksIEC, Crimson 2.0
2. Configuration Procedure
I. Set the IP addresses of the devices (HMI, controller, PC with programs). In the test set up, the IP
addresses were: Controller: 192.168.1.1, HMI: 192.168.1.2, PC: 192.168.1.3
The default IP address on the MPiec controller is 192.168.1.1 unless changed by a user.
Figure 2: Set IP address of controller
II. To set the IP address of the RedLion G310: On the opening page of Crimson 2.0, double click on the
communications tab.

Fugure3: To set the HMI IP address
Double click on Ethernet and set the IP address of the HMI as shown in Figure 4.
Figure 4: HMI IP address

Click on Protocol 1. Edit the driver selection to select MODBUS as manufacturer and TCP/IP master
as driver. No special Yaskawa driver is necessary.

Figure 5: Communication Protocol

This will create the slave configuration under protocol 1. When double clicking on the slave device
created, the IP address of the slave in this communication process can be specified. (Figure 6).
Figure 6: IP address of slave specified

III. Using an HMI (Master) to communicate to the controller using Modbus TCP

Figure 7 shows the Modbus memory map, and how it relates to the Global Variables in MotionWorks IEC.
Note that function codes 01 and 03 return data that was sent to the controller from the master and do not
reflect data from the Global Variables in the application program.
The Modbus data memory is copied to the Global Variables at the task update rate.
Modbus coil 0 equates to the Global Variable at %IX24560. 128 coils are available.
Modbus register 40000 equates to the Global Variable at %IW28672. 1024 registers are available.
Modbus input 10000 equates to the Global Variable at %QX24560. 128 inputs are available.
Modbus register 30000 equates to the Global Variable at %QW28672. 1024 registers are available.
Figure 7a: MODBUS mapping
As shown in Figure 7a below, the input and output memory is in a different location even though they
have the same numerical addressing.

IV. Launch the Hardware Configuration in MotionWorks IEC. Connect to the controller through the hardware
configuration. Select the MODBUS TCP option and enable the controller as a MODBUS slave. Save this
configuration and reboot the controller. These steps will activate the MODBUS communication driver on
the MPiec controller.
Figure 7b: Enabling the MPiec controller as a MODBUS TCP slave (server)
V. The global variables worksheet in MotionWorks IEC will now have MODBUS TCP groups which will
have to be populated by the user. These memory areas are generic: no variables are automatically
created, the user can decide on the arrangement and type of data to populate within the communications
memory region
Figure 8: Variable groups created in template
A word coming from the HMI will be mapped from register 40001 in the RedLion to %IB28672. The
user should verify the data type used for data transfer. Bits written from the HMI to the controller are
mapped from 00001 to %IX24560.0. Outputs from the controller are mapped from %QB28672
->300001 and %QX24560.0 -> 10001

3. HMI variables
Create output bits/words on the HMI.
1. Servo Enable (bit)

2. Forward direction
3. Reverse direction
4. Jog Speed
5. Jog acceleration
6. Jog deceleration
Create input bits/words on the HMI.
1. ServoStatus
2. InVelocity
3. Actual Position
4. Actual Velocity
5. Actual Torque
The variable tags have been defined in the data tags tab in the RedLion project.
Figure 9: Data tags
When creating a new tag, the user can specify the data type of the tag. The user can also map the tag

and specify what register location that tag should be associated with. For example, the tag
ServoEnable is mapped to a location in PLC1, which is the slave IEC controller. On clicking the edit
button, the register and data type can be seen as shown in Figure 10. It can be seen that a bit was
chosen as the data type. The register to which that tag is mapped is 00001 and it is a coil. This bit will
be mapped to the first bit mapped under Function Code (FC) 5. The access to this tag is set as Write
Only as this variable is used for writing to the controller. FWD and REV are similar bit tags. The Jog
speed tag mapping is shown in Figure 11. A word swap transformation is carried out for words. The
register used for the word is 40001. Figure 12 illustrates the mapping of a tag that is a read access
variable that reads the servo status from the controller to display at the HMI panel. Figure 13 illustrates
a controller output real variable displayed at the HMI.
Figure 10: Mapping bit (FC: 5)

Figure 11: Mapping word (FC: 16)
Figure 12: Bit Mapping (FC: 2)

Figure 13: Word mapping (FC: 4)

The user interface on the HMI screen is as shown in Figure 14.
Figure 14: HMI user interface screen shot

4. MotionWorks IEC variable declaration
Figure 14: Variables in the MPiec controller (Slave)
The global variable list with the MODBUS variables being used is shown in detail in Figure 14. The first two
groups corresponding to function codes 05 and 16 are the input variables written from the HMI to the controller.
The groups under function codes 02 and 04 are used to transfer variables from the controller to the HMI. They
are denoted by %QX and %QB. Table 1 shows the variable mapping in this sample project.
Table 1: variable mapping

FC#05: From master to slave (coils)
EnableServo %IX24560.0 00001 ServoEnable
GoForward %IX24560.1 00002 FWD
GoReverse %IX24560.2 00003 REV
FC#06: From master to slave (registers)
Speed %ID28672 400001 JogSpeed
Accel %ID28676 400003 JogAccel
Decel %ID28680 400005 JogDecel
FC#02: From slave to master (Inputs)
ServoPowerStatus %QX24560.0 100001 ServoStatus
AxisInVelocity %QX24560.1 100002 InVelocity

FC#04: From slave to master (Registers)

ActualPosition %QD28672 300001 AxisPosition
ActualVelocity %QD28676 300003 AxisVelocity
ActualTorque %QD28680 300005 AxisTorque
5. Execution
Communication between the Red Lion HMI and the MPiec controller should commence as soon as the
two projects start running on the two devices.

Redlion MPiec Modbus Configuration W Crimson2 v007

Uploaded by

Copyright:

Available Formats

Redlion MPiec Modbus Configuration W Crimson2 v007

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Redlion MPiec Modbus Configuration W Crimson2 v007

Uploaded by

Copyright:

Available Formats

What is the purpose of this document?

What is the purpose of this document?

How is communication established between the RedLion HMI and MPiec controller?

How is communication established between the RedLion HMI and MPiec controller?

Technical Note

Configuring a RedLion HMI to communicate with an

Applicable Product: MPiec, RedLion G310 HMI

1. Application Overview: ..................................................................................................... 3

September 23, 2013 Page 2 of 14

Figure1: Overview of test set up

September 23, 2013 Page 3 of 14

Controller Yaskawa MPiec controller

Software MotionWorksIEC, Crimson 2.0

Figure 2: Set IP address of controller

September 23, 2013 Page 4 of 14

Fugure3: To set the HMI IP address

Figure 4: HMI IP address

September 23, 2013 Page 5 of 14

Figure 5: Communication Protocol

Figure 6: IP address of slave specified

September 23, 2013 Page 6 of 14

Figure 7a: MODBUS mapping

September 23, 2013 Page 7 of 14

Figure 8: Variable groups created in template

September 23, 2013 Page 8 of 14

1. Servo Enable (bit)

Create input bits/words on the HMI.

Figure 9: Data tags

September 23, 2013 Page 9 of 14

Figure 10: Mapping bit (FC: 5)

September 23, 2013 Page 10 of 14

Figure 11: Mapping word (FC: 16)

Figure 12: Bit Mapping (FC: 2)

September 23, 2013 Page 11 of 14

Figure 13: Word mapping (FC: 4)

Figure 14: HMI user interface screen shot

September 23, 2013 Page 12 of 14

4. MotionWorks IEC variable declaration

Figure 14: Variables in the MPiec controller (Slave)

Table 1: variable mapping

September 23, 2013 Page 13 of 14

FC#04: From slave to master (Registers)

September 23, 2013 Page 14 of 14

You might also like