Built-In HMI — Operator Interface From the Runtime
A demo of the built-in HMI: three independent tasks with different scan rates, counters, and start/stop controls, served straight from the runtime.
This video was recorded while the product was called GOPLC. The on-screen branding differs from the current name; the runtime is the same one.
A simple demo of the built-in HMI. No separate HMI software — the operator interface is served directly from the PLC runtime to a browser.
What’s in the Demo
Three PLC tasks running simultaneously, each with:
- Different scan rates — every task executes at its own cycle time
- Independent counters — each keeps its own count
- Start/stop controls — each can be started and stopped on its own
- Reset — counters reset individually
That is the point being made: multi-task execution. Unlike simple PLCs running a single program loop, ControlForge runs multiple concurrent tasks at different priorities and scan rates — from 100 microseconds up to hours.
Why Built-In HMI Matters
A traditional setup needs three things:
- PLC programming software to write the logic
- Separate HMI/SCADA software for the operator interface
- A communication driver to link them
Steps 2 and 3 disappear. The HMI is part of the runtime and served over the web — open a browser, point it at the PLC, and the operator interface is there. No extra licences, no driver configuration, no second engineering tool.
Useful for:
- Quick commissioning — a working interface in minutes
- Remote monitoring — any device with a browser
- Small systems — where a full SCADA package is overkill
- Prototyping — build interfaces alongside the control logic