Map Variables to HMI

For HMIClosed"Human-machine interfaces " Also known as computer-human interfaces (CHI), and formerly known as man-machine interfaces, they are usually employed to communicate with PLCs and other computers, such as entering and monitoring temperatures or pressures for further automated control or emergency response, the variable mapping is done in two phases.

  • Phase 1 - Tag all of the variables to be exported in from the HMI project (see procedure below)
  • Phase 2 - Use this mapping file when designing the HMI

The tag operation directly takes place in the Dictionary, as follows:

  1. Open the Variable list editor available in the Dictionary toolbox

    • Double-click the Dictionary header to display the widget as a popup window in order to have more space.

  2. In the KVB column, select the variables you want to map

    Variable Mapping to HMI

  3. Figure 4-27: Variable Mapping to KVB.


    • Non-primitive data types which are not exported over Modbus generate a warning message in the Compiler Output window. See Compiler Output for more information.

  4. Compile the application to create the Modbus mapping file.

    • Generally you do not need to access this, but if you do the file used for manually importing variables into KVB (named HMI Variable Import File.txt) is located in the following location.

      • Windows 7: C:\Users\(user)\AppData\Local\Kollmorgen\KAS\Project
      • Windows XP: C:\Documents and Settings\(user)\Local Settings\Application Data\Kollmorgen\KAS\Project
  5. Open the KVBProject from the Project Tree. This will automatically transfer the tagged variables..

List of variables that you can export

The following types of variables can be exported to the HMI:

  • The fundamental data types: BOOL, SINT, INT, USINT, UINT, BYTE, WORD, DINT, UDINT, DWORD, TIME, REAL, LREAL, STRING.
  • Arrays of supported data types
  • Structures that include members of supported data types

Examples of structures that you can export

  • Arrays of BOOLs such as a structure that includes a BOOL array member and instances of UDFB members.
  • An array of structures that include INT and LREAL members
  • A structure that includes both instances of UDFB member as well as an embedded structure which includes an INT member and instances of a UDFB member. This is due to the embedded structure has an INT member and therefore the outer structure can be exported too.

Examples of structures that you cannot export

  • A structure that includes instances of UDFB or LWORD members only.

Concept Link IconSee Also