📘 Resource Overview & Documentation Details

You are viewing the technical directory listing for HMI and PLC Training Simulator: From Buttons to Touchscreen. This engineering resource is curated under our Human Machine Interface division to support automation specialists, control systems engineers, and manufacturing technicians looking for verified reference materials.

🔍 Contextual Abstract & Technical Scope

Share Summary:LinkedInEmail

A practical HMI PLC training simulator can teach more than how to write a control program. It can also show how operators issue commands, enter process values, and monitor what a machine is doing. In a ball-sorting training system, adding a touchscreen HMI to an existing PLC-controlled simulator connected these activities in one learning environment.

The change addressed a common gap in automation education: the simulator already supported PLC instruction, but operators interacted with it through mechanical push buttons and toggle switches. Adding a graphical interface made HMI design and PLC interaction part of the same exercise, while also replacing the conventional control panel.

Why combine PLC and HMI training?

A programmable logic controller (PLC) executes the control logic for a machine or process. A human-machine interface (HMI) gives an operator a way to select operating modes, enter commands, and view process information. The two have different roles, but they must exchange signals and data reliably for the operator to interact with the controlled equipment.

In the simulator, students could previously learn PLC control, but they had limited opportunity to work with an HMI. The mechanical controls were also subject to wear and unreliable electrical connections, which could make input signals unstable. Changing a sorting target presented another limitation: the setpoint had to be changed in the PLC program and the program uploaded again.

A touchscreen interface offers a different approach. An operator can enter a setpoint through a numerical input object, while read-only displays show the count and the current process stage. This makes operator interaction and process monitoring visible alongside the PLC’s control sequence.

How the ball-sorting simulator works

The simulator uses a Mitsubishi FX5U PLC, two DC motors to drive the ball and box conveyors, and two photoelectric sensors to detect balls and boxes. Its purpose is to demonstrate sorting a specified number of table-tennis balls into a box.

Operation can be manual or automatic. In manual mode, the operator controls the conveyors and other relevant actions. In automatic mode, the PLC ladder program governs the sequence. The automatic process includes standby, moving the box conveyor, running the ball conveyor, and moving the box conveyor again after the target count is reached. The box and ball sensors provide inputs used during the process.

These operating details shaped the HMI design. An interface needs to reflect the actual machine sequence and the controls available to the operator; a generic screen cannot represent every process equally well.

Designing the HMI around the process

The HMI was developed for a Mitsubishi GOT2000 touchscreen panel using GT Designer3. The design work began by identifying the simulator’s inputs and the process values that should be entered or displayed. The screen was then organized into three functional areas:

  • Header: Provides general information about the simulator using text and an image.
  • Process parameters: Presents the target ball count, the number counted into the box, and information about the current process step.
  • Control panel: Provides touchscreen controls for starting and stopping automatic operation, selecting manual or automatic mode, and running each conveyor manually.

The target count is a writable numerical input. The number of balls counted is displayed as a read-only value. The interface also displays the PLC’s step number and a text description of the active step, helping users distinguish the sequence position from its meaning.

Controls were selected to reflect how the simulator operates. Start and stop commands use momentary push buttons, while mode selection and manual conveyor controls use alternate behavior: each touch changes the signal state. The interface enables the manual conveyor controls in manual mode and uses start and stop for automatic operation.

Linking HMI objects to PLC logic

Every interactive HMI object needs a corresponding PLC address so that commands and process data can move between the panel and controller. In this design, discrete commands such as start, stop, mode selection, and manual conveyor operation use internal relay devices. Numerical values, including the setpoint and step number, use data registers. The ball count uses a counter value, while the step description is displayed as text.

The PLC ladder logic was modified to read values and commands entered through the HMI. This is an important integration task: creating a screen object alone does not make it control the machine. The PLC program must interpret the associated device states and values in the context of the control sequence.

The panel and PLC communicated over Ethernet using TCP/IP. A PC was also connected through a switch for troubleshooting. During testing, the devices were configured on the same IP network.

Testing operation and data visibility

Testing checked both control functions and displayed information. The start and stop controls were verified in automatic mode, and the mode selection was checked against the value stored in the PLC. In manual mode, the conveyor buttons were tested. The setpoint was checked to confirm that the entered value reached PLC memory.

Tests also confirmed that the displayed ball count matched the balls detected as they entered the box, and that the step number and text description reflected the active process stage. The reported test results showed that all listed HMI functions worked as intended on the simulator.

Practical lessons for automation training

The project demonstrates several useful principles for engineering teams and training programs:

  • Start with process behavior. Define operating modes, sequence stages, operator actions, and monitored values before laying out the screen.
  • Map each object to a PLC device. Clear address assignments help connect interface behavior with ladder logic and controller memory.
  • Make process status visible. Showing a step number, description, target, and actual count helps learners understand how commands relate to machine progress.
  • Test communication as well as screen behavior. Confirm that commands reach the PLC and that returned values are displayed correctly.

The HMI could be extended with user-level access, data logging, and alarms. These were identified as potential future developments, not features included in the tested system. Access levels could distinguish permissions for roles such as operator, leader, and administrator, while logging and alarms could support analysis and troubleshooting.

Conclusion

Adding a touchscreen HMI transformed the ball-sorting setup from a PLC-focused trainer into a simulator for learning both PLC control and operator-interface design. The key engineering work was not simply drawing a screen: it involved defining I/O and process parameters, assigning PLC addresses, adapting ladder logic, configuring communication, and verifying behavior. For automation educators and integrators, the example underscores the value of teaching the complete interaction between operator, HMI, PLC, and process.

Access Official Technical PDF