Check addresses, verification status, types, classifications, comments, and rules. Export includes all retained rows, regardless of selection, search, or selected-only view. Apply rules or delete rows to reduce export scope.
Check addresses, verification status, types, classifications, comments, and rules. Export includes all retained rows, regardless of selection, search, or selected-only view. Apply rules or delete rows to reduce export scope.
Before export, the application compares project paths; a mismatch stops export and clears the old result. For verified addresses, it also checks project content, scan configuration, and the TIA runtime against the scan identity. Changes block export and require a fresh scan. Restored sessions can export unverified review lists.
Select Export Current Result, then choose Excel, CSV, or JSON and a save location. The file contains normalized point rows retained after review.
The desktop app saves only the selected .xlsx, .csv, or .json file. To generate Mingcedar-compatible files and batch reports, run the CLI without preview mode. See Export Rules for the output files and their purposes.
Use the CLI and a configuration file for repeat scans and archived outputs. Preview runs a quick scan without generating the complete output set.
HQScan.Openness.Cli.exe scan --config scan-config.json
HQScan.Openness.Cli.exe scan --config scan-config.json --project "<project-file>" --out "<output-dir>" --previewMain fields include projectPath, outputDir, includePlcNames, deviceCodeOverrides, defaults, filters, naming, and classification. The scanner fixes the address area to DB; the remaining fields narrow PLC/DB/project-tree scope and define naming or alarm/trend classification.
Before use, replace the example project path, output folder, PLC name, device code, and naming rules with real values. Validate import fields against the target system.
{
"projectPath": "<project-file>",
"outputDir": "<output-dir>",
"includePlcNames": ["<PLC name>"],
"deviceCodeOverrides": { "<PLC name>": "<device code>" },
"defaults": { "scanRateMs": 1000, "sourceKind": "plc" },
"filters": {
"includeAddressAreas": ["DB"],
"includeDBs": ["DB1-DB50"],
"excludeNames": ["%EXCLUDE_TOKEN%"]
},
"classification": {
"alarmRules": [{ "namePatterns": ["%ALARM_TOKEN%"], "setAlarmEnabled": true }],
"trendRules": [{ "namePatterns": ["%TREND_TOKEN%"], "setArchiveEnabled": true }]
}
}--preview uses default classifications without full per-point name filters or alarm/trend rules; its counts and flags cannot validate formal output. With an output directory, it writes only preview-report.json, not communication-import files. Omit --preview to apply rules and export data and reports. Import counts also depend on address evidence and types.
Export Current Result does not include the raw TIA project, full project tree, rule configuration, UI state, or runtime logs. It does not create import bundles for Mingcedar or other platforms. Out-of-scope, unreadable, excluded, or deleted items do not appear in the exported 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 standard layout first, then check project-tree, PLC and DB scope, Openness access, the HMI/OPC-access option, rules, supported types, and absolute-address resolution. If the TIA project layout must change, assess its effect on existing addresses before rescanning and validating the result.
Use Excel for manual review and CSV or JSON for scripts or transformation. For another SCADA/HMI or custom system, map and validate the export against that product's official field rules; only the CLI's named compatibility JSON files target Mingcedar.
Include the exported file, project source, selected scope, rule notes, and any assumptions used during the scan.