Confirm symbolic addresses, absolute addresses, data types, alarm/trend marks, address status, comments, and rule results before choosing the export format. Selection is mainly used for review and bulk actions; the final file is based on the normalized point rows that remain in the current result list.
Confirm symbolic addresses, absolute addresses, data types, alarm/trend marks, address status, comments, and rule results before choosing the export format. Selection is mainly used for review and bulk actions; the final file is based on the normalized point rows that remain in the current result list.
In offline mode, export compares the project-path field with the project path recorded in the scan result. If the paths differ, export stops and the previous result is cleared. Scan the current project again and verify the result project name and full path before exporting.
This describes the modern GUI action, Export Current Result. It saves one file in the selected Excel, CSV, or JSON format. Exported rows come from the current reviewed and normalized point result. See Export Rules for the supported source categories, data types, and fields.
The modern GUI scan first creates a reviewable current result list and does not immediately write the full compatibility bundle. When you click Export Current Result, it writes only the .xlsx, .csv, or .json file selected in the save dialog. A non-preview CLI scan writes the output folder files: normalized-tags.json, tag-import.json, alarm-import.json, trend-import.json, hqserver-create-tags.json, generic-tags.csv/json, and export-manifest.json.
Export Current Result does not include the raw TIA project, the full project tree, rule definitions, UI filter or expansion state, temporary row selection state, internal diagnostics, or automatically generated external-platform or HQControl compatibility bundles. Structured content that was not normalized into point rows, items cleared from the current result, items excluded by rules, objects outside the scan scope, and unreadable objects will not appear in the final file.
An item is usually absent because it was outside the selected scan scope, filtered by Rule Center, manually cleared from the result, unreadable, or not a supported exportable point row. The export is a reviewed deliverable, not a complete project backup.
Confirm whether the DB was selected in the project tree, whether it can be read through Openness, whether it is excluded by Rule Center, whether it is an optimized DB that should use symbolic addressing, and whether it contains complex or unsupported types. Then decide whether to scan it explicitly or split it into exportable scalar tags in the PLC project.
Use Excel for manual review. Use CSV or JSON for scripts, system import, or automated processing. Whether the target is another SCADA/HMI product, a custom system, or HQControl, compare its field structure with the export and the unsupported scope above before import.
Include the exported file, project source, selected scope, rule notes, and any assumptions used during the scan.
