Scan and review the result table

Check the symbolic address, absolute address, data type, scan period, and total count.

Step 4

Step 4: Scan and review the result table

Review the table before exporting. Confirm the scan found the DB points you actually need.

What to review

Check the symbolic address, absolute address, data type, scan period, and total count.

The result uses symbolic address as the primary field

The result table and export files use symbolic address as the point key. Review, search, rule matching, and import preparation should be based on symbolic address, data type, address metadata, and comments.

Online results usually do not show absolute addresses

Online OPC UA browse returns symbolic nodes and node attributes, but not always a stable DB number, byte offset, or bit offset. Therefore online mode weakens or hides the absolute-address column. Offline mode generates DB absolute addresses only when TIA project metadata provides stable offsets.

Data types must be HQControl-supported types

The table type is normalized to HQControl-supported types such as BOOL, BYTE, WORD, DWORD, INT, DINT, REAL, LREAL, STRING, WSTRING, and time/date types. Structured objects, array containers, and objects that cannot produce stable scalar fields are treated as engineering context.

Use table operations

Use selection, filtering, deletion of selected rows, clear selection, restore all, and selected-only view to narrow the target result.

Do not export too early

If the table contains content outside the intended delivery scope, adjust scope or rules before exporting.

HQ Scan scan result table
Figure 1: Review scan results before export

Confirm symbolic addresses, absolute addresses, data types, and counts first. Then decide whether to export or continue with Rule Center.