Specifications

54
Principle
Example of HMI data mapping
Two ATV61 manage two separate pumps. A Unity structured data type HMI-ATV is dened to create the
variables used for HMI exchanges.
In the example, two instances are created and link to the two ATV61 drives.
The parameters from the rst ATV61 are assgined to LS1_PMP_D1 (type HMI_ATV) mapped in %MW100 on
Unity side.
The second ATV is assigned to LS1_PMP_D2 (type HMI_ATV) mapped on %MW140. The size of an HMI_ATV
variable is 40 words, this value will be used to manage the index on the HMI side.
In Vijeo Designer, a similar HMI_ATV data type is used.
3 types of variables are used Boolean, Integer, String[10]. Therefore 3 indexes are needed:
_ Index_Bool
_ Index_Int
_ Index_String
At pump popup call, the index values are updated. An example of index usage is provided below:
Calculation of index: Index =Gap * Type variable.
Variable Integer, type = 1 => Index_Int =40 * 1 = 40
Variable Boolean, type =16 => Index_Bool = 40 * 16 = 640
Variable String[10], type = 1/5 =>Index String = 40/5= 8
Example
Vijeo Designer 4.6 can not use the data structure from Unity, therefore the following recommendation are
proposed.
5-Implementation
HMI implementation
UNITY
HMI_ATV
Type
HMI_LS1_PMP_D1 (type HMI_ATV) %MW100
Instance 1
Instance 2
HMI_LS1_PMP_D1 (type HMI_ATV) %MW140
HMI_ATV
Variables used by the popup
VIJEO DESIGNER
Popup(s) and Index
Aut_Man %MW100.0 [Index_bit]
Run_Stop %MW100.8 [Index_bit]
Clear_Flt %MW101.0 [Index_bit]
Name %MW1119[Index_String]
Speed_Setpoint %MW1102 [Index_word]
Aut_Man
Run_Stop
Clear_Flt
Speed_Setpoint
Name
Aut_Man %MW100.0
Run_Stop %MW100.8
Clear_Flt %MW101.0
Speed_Setpoint %MW102
Name %MW119
Aut_Man %MW140.0
Run_Stop %MW140.8
Clear_Flt %MW141
Speed_Setpoint %MW142
Name %MW159
Index_Int = 40 * 1 = 40
Index_Int = 40 * 16 = 640
Index_String = 40/5 = 8
Index_Int = 0 * 1 = 0
Index_Int = 0 * 16 = 0
Index_String = 0/5 = 0