One engineering environment
Screens, alarms, trends, recipes and operator controls are engineered within the CODESYS toolchain.
CODESYS · HMI and operator interface
CODESYS Visualization
Integrated HMI Engineering for Local, Web and Independent Displays
CODESYS Visualization provides a common engineering environment for operator, commissioning and maintenance interfaces. Visualization objects can reference CODESYS application variables directly, while the finished interface can be deployed as TargetVisu, WebVisu or CODESYS HMI depending on where the display must run.
TargetVisuWebVisuCODESYS HMIHTML5 browser clientsAlarms and trends
EngineeringDevelopment System
Controller displayTargetVisu
Browser displayWebVisu
Independent HMICODESYS HMI
Product role
One HMI engineering environment, three deployment paths
CODESYS Visualization provides a common engineering environment for operator, commissioning and maintenance interfaces. Visualization objects can reference CODESYS application variables directly, while the finished interface can be deployed as TargetVisu, WebVisu or CODESYS HMI depending on where the display must run.
One engineering environmentScreens, alarms, trends, recipes and operator controls are engineered within the CODESYS toolchain.
Three deployment architecturesTargetVisu runs with the controller display, WebVisu serves browser clients, and CODESYS HMI runs as a separate HMI system.
Direct and external data accessVisualization can use application variables directly; CODESYS HMI can also access controller data through OPC UA where required.
Architecture role
HMI runtime location and controller data access
Define the interfaces and ownership boundaries first; version, licence and target selection should follow the architecture rather than lead it.
01Application variables
02Visualization engineering
03TargetVisu / WebVisu / HMI
04Operator / service
05Alarms / trends / recipes
Confirm the exact target, product version, device package, protocol role, licence and—where applicable—certified safety scope before release to production.
Engineering scope
Operator-interface engineering capabilities
These capabilities define what the CODESYS component contributes to the architecture and what must still be provided by the controller, host platform, network or machine design.
Three deployment architectures
TargetVisu runs with the controller display, WebVisu serves browser clients, and CODESYS HMI runs as a separate HMI system.
Direct and external data access
Visualization can use application variables directly; CODESYS HMI can also access controller data through OPC UA where required.
Technical selection
Display, client, network and licence selection
Use this table as a requirement-capture guide. The final implementation should be checked against current CODESYS product documentation, Store data, target documentation and—where relevant—certificates and safety manuals.
| TargetVisu | Displays the visualization on a screen connected to or integrated with the controller. Controller resources and target support must be qualified. |
|---|---|
| WebVisu | Serves the visualization to HTML5-capable browsers. Browser access, TLS, user roles and network exposure should be included in the cybersecurity design. |
| CODESYS HMI | Runs as a separate HMI client on a PC or panel and can access controller data through OPC UA, allowing the HMI layer to be decoupled from the PLC. |
| Engineering functions | Prefabricated elements, user controls, trends, alarms, recipes, responsive layouts and importable HTML5 elements are available according to the selected product scope. |
| Commercial scope | Available variables/data points, clients and optional functions depend on the selected runtime and current CODESYS licence model. |
Project workflow
HMI design, integration and validation workflow
Move from architecture qualification to engineering, commissioning and lifecycle evidence in a controlled sequence.
Decide where each interface runs
Choose TargetVisu, WebVisu or CODESYS HMI for each display location and its service requirement.
Engineer the interface
Build navigation, operating modes, alarms, trends and maintenance functions around the operator task.
Connect the data
Bind controller variables and any external sources permitted by the selected deployment.
Validate use and access
Test roles, sessions, alarm acknowledgement, responsiveness, remote access and recovery.
Platform context
TargetVisu, WebVisu or CODESYS HMI?
Select the deployment variant by display location, controller resources, remote-access model and whether the HMI must be independent of the PLC.
Current page
CODESYS Visualization
CODESYS Visualization provides a common engineering environment for operator, commissioning and maintenance interfaces. Visualization objects can reference CODESYS application variables directly, while the finished interface can be deployed as TargetVisu, WebVisu or CODESYS HMI depending on where the display must run.
View role in the platform →EngineeringCODESYS Development System
CODESYS Development System is the core engineering environment for creating industrial control applications. It combines IEC 61131-3 programming, device and I/O configuration, libraries, compilation, debugging and online commissioning in one project. The application is engineered here and executed later by a compatible CODESYS runtime.
View role in the platform →Control executionCODESYS Runtime
CODESYS Runtime is the execution layer that turns a compatible target into a programmable controller. The application is created in the Development System, compiled for the selected target, and executed by CODESYS Control—either already integrated by an OEM or installed as a ready-to-use Control SL SoftPLC on a supported platform.
View role in the platform →Documentation & requirement capture
Official CODESYS documentation and project inputs
Use the official product page for current product information, then provide the project-specific details below so the architecture can be reviewed against the actual machine or system.
Official CODESYS Visualization informationOpen CODESYS ↗Complete CODESYS platform architecturePlatform overview →
Application scopeMachine/process functions, operating modes, cycle-time expectations and whether the project is new design, retrofit or migration.
Target & software baselineController/IPC, CPU architecture, operating system, CODESYS runtime, device package, compiler profile and existing project version.
I/O & communicationLocal/remote I/O, fieldbuses, Industrial Ethernet, OPC UA, MQTT, controller-to-controller links and required protocol roles.
HMI & user accessDisplay hardware, browser clients, independent HMI requirements, alarms, trends, recipes, user roles and remote-service policy.
Motion & functional safetyAxis count, drives, kinematics, CNC/robotics requirements, safe I/O, safe communication and required PL/SIL where relevant.
Deployment & lifecycleController quantity, sites, licensing, backups, certificates, update process, rollback expectations and maintenance ownership.