Check project – Find and work through tasks
Review notices, warnings and errors, navigate to affected objects and deliberately mark tasks as completed.
1. Understand the task list
Tools → Check project scans the current project in design mode and lists findings. Opening it runs a fresh check. It assists configuration; it is not plant acceptance or a complete functional test.
Each row shows completion state, severity, task, page, object where applicable and details. [ ] NOTICE · Process variable not assigned means an open finding with no process variable in the checked assignment.
2. Notices, warnings, errors and counts
- Notice
- Requires interpretation, such as an object without a process binding. This may be intentional in a simulation.
- Warning
- A potentially problematic condition, such as an empty page, duplicate page name or object outside page boundaries.
- Error
- A detected structural problem, such as missing or duplicate object IDs or invalid object dimensions.
9 open · 0 errors · 0 completed · 9 displayed means nine open tasks, none classified as errors, none ticked off and nine visible. Zero errors does not mean zero open tasks. The error count includes open errors; marking one completed is not a technical repair.
3. Filters and search
Choose Open, All, Completed, Errors, Warnings or Notices. Severity filters display open findings of that type. Search matches task, detail, page or object, ignoring case.
If a task seems missing, clear search and choose All. Displayed reflects filtering; overall open and completed counts refer to the findings as a whole.
4. Navigate to the affected object
A single mouse click on a task row already opens its target. The check window closes and the editor displays the page and selects the object. Show object performs the same navigation after selection, for example by keyboard.
Page-level findings open the page. Project-wide findings may have no direct page target; the status explains this. Navigation does not itself fix the setting.
5. Example: unassigned process variable
- Open the finding for Anlagenübersicht · Fuellstand_Tank_01_Wert.
- Decide whether this display intentionally uses a simulation value or needs a real process signal.
- If binding is intended, assign the correct device and symbol in properties. See the PLC table.
- Apply, save the project and reopen Check project or use Check again.
- Also test the reading in its intended operating mode.
The screenshot includes navigation buttons too. A page-navigation button can intentionally work without a PLC address. Evaluate the general notice against the actual button function; do not create artificial bindings just to empty the list.
6. Mark completed or reopen
Completed / Reopen toggles the selected task's status. Because clicking a row navigates immediately, use keyboard selection to mark it: focus the list, select with arrow keys, then use the button.
Completed tasks disappear from the Open filter. Find them under Completed or All to reopen them. This marks the project changed; save afterwards.
Ticking a task does not fix its cause. It can document that an unbound simulation object was reviewed as intentional. The same finding on the same object may retain its completion mark on a later scan. Review All or Completed during acceptance as well.
7. Check again and understand the limits
Check again rebuilds findings from the current project. Corrected causes are no longer reported. It does not repair anything automatically or clear all completion marks. Close only closes the view.
Checks include page/object structure, selected process bindings, references and recipe configurations. They do not guarantee PLC connectivity, correct addresses, readings, permissions or complete process behaviour. Complement them with table validation and functional tests.
Before production use, assess findings and test intended operations. Simulation notices can be intentional in the demo; marking tasks complete does not unlock hidden drivers.