and IP320: Configuring HMI Variable Mapping

Karen Mitchell1 min read
HMI ProgrammingOther ManufacturerTutorial / How-to
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

The available evidence does not provide register numbers, data types, or communication settings, so do not guess them; define and verify them in both projects.

Required Hardware and Project Information

Before configuring the panel, prepare the complete controller and panel projects plus a short functional specification covering the pulse input, counter behavior, time setpoints, and program-start commands.

Define the HMI Variables

Required function Controller variable Panel access Unresolved detail
Display accumulated pulses Counter output or a numeric variable containing that output Read Address and data type
Set a target of 1000 pulses Counter preset or target variable Read/write Address, range, and data type
Start a stored program Program-selection and start-command variables Write Command behavior and addresses

Expose the counter result—not merely the physical pulse input—to the panel. Keep the displayed count, editable target, timer setpoints, and start command as distinct variables unless the completed functional specification requires different behavior.

Configure the Address Mapping

  1. Create matching IP320 tags for the counter value, pulse target, timer setpoints, program selection, and start command.
  2. Match each panel tag to the corresponding controller address and configure its access direction: read for display-only data and read/write for operator-entered setpoints.
  3. Confirm the data representation and engineering unit on both sides before downloading either project. The evidence does not specify the address format, numeric types, or time-base conversion.

Commission and Verify

Test one function at a time. Finally, enter the 1000-pulse target and confirm that the programmed action occurs at the controller's target condition.

If a value does not update, compare the complete projects for missing network addresses, mismatched read/write permissions, incompatible data representations, or an undefined time unit. Do not troubleshoot the process sequence until direct variable transfer works in both directions.

FAQ

Map the counter output, or a numeric variable that stores that output, as a read-only panel tag.

Create separate writable controller variables for the timer setpoints and counter target, then bind matching read/write panel tags to their assigned network addresses. Verify the controller's time unit before interpreting entered values as seconds.

Back to blog