Product: Mingcedar Scan SCAN

Export the final result | Mingcedar Scan

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.

Published 2026-10-25T12:48:42.621613383Z Updated 2026-10-25T12:48:42.621612601Z

<div class="manual-doc-article manual-doc-article-section"><h2 id="export">Step 6: Export the final result</h2>

Check export scope, fields, and project before saving.

<h3 id="export-item-1">What to check before export</h3>

<p>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.</p>

</article>

<h3 id="export-item-2">Confirm the result project before export</h3>

<p>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.</p>

</article>

<h3 id="export-item-3">Export the current result</h3>

<p>Select Export Current Result, then choose Excel, CSV, or JSON and a save location. The file contains normalized point rows retained after review.</p>

</article>

<h3 id="export-item-4">Desktop export and CLI output</h3>

<p>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.</p>

</article>

<h3 id="export-item-5">Run a repeatable CLI scan</h3>

<p>Use the CLI and a configuration file for repeat scans and archived outputs. Preview runs a quick scan without generating the complete output set.</p>

<div class="manual-code" data-code-language="text"><div class="manual-code-toolbar"><span>Text</span><span class="manual-code-tools"><small>Text</small><button type="button" data-copy-code data-copied="Copied" data-failed="Select and copy the code" aria-label="Copy code: Text">Copy code</button><span class="manual-code-status" role="status"></span></span></div><pre tabindex="0" class="docs-code-block shiki github-light" style="background-color:#fff;color:#24292e" tabindex="0"><code><span class="line"><span>HQScan.Openness.Cli.exe scan --config scan-config.json</span></span>

<span class="line"><span>HQScan.Openness.Cli.exe scan --config scan-config.json --project "<project-file>" --out "<output-dir>" --preview</span></span></code></pre></div>

</article>

<h3 id="export-item-6">CLI configuration fields</h3>

<p>Main fields include <code>projectPath</code>, <code>outputDir</code>, <code>includePlcNames</code>, <code>deviceCodeOverrides</code>, <code>defaults</code>, <code>filters</code>, <code>naming</code>, and <code>classification</code>. The scanner fixes the address area to DB; the remaining fields narrow PLC/DB/project-tree scope and define naming or alarm/trend classification.</p>

</article>

<h3 id="export-item-7">CLI configuration example</h3>

<p>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.</p>

<span class="line"><span style="color:#005CC5"> "projectPath"</span><span style="color:#24292E">: </span><span style="color:#032F62">"<project-file>"</span><span style="color:#24292E">,</span></span>

<span class="line"><span style="color:#005CC5"> "outputDir"</span><span style="color:#24292E">: </span><span style="color:#032F62">"<output-dir>"</span><span style="color:#24292E">,</span></span>

<span class="line"><span style="color:#005CC5"> "includePlcNames"</span><span style="color:#24292E">: [</span><span style="color:#032F62">"<PLC name>"</span><span style="color:#24292E">],</span></span>

<span class="line"><span style="color:#005CC5"> "deviceCodeOverrides"</span><span style="color:#24292E">: { </span><span style="color:#005CC5">"<PLC name>"</span><span style="color:#24292E">: </span><span style="color:#032F62">"<device code>"</span><span style="color:#24292E"> },</span></span>

<span class="line"><span style="color:#005CC5"> "defaults"</span><span style="color:#24292E">: { </span><span style="color:#005CC5">"scanRateMs"</span><span style="color:#24292E">: </span><span style="color:#005CC5">1000</span><span style="color:#24292E">, </span><span style="color:#005CC5">"sourceKind"</span><span style="color:#24292E">: </span><span style="color:#032F62">"plc"</span><span style="color:#24292E"> },</span></span>

<span class="line"><span style="color:#005CC5"> "filters"</span><span style="color:#24292E">: {</span></span>

<span class="line"><span style="color:#005CC5"> "includeAddressAreas"</span><span style="color:#24292E">: [</span><span style="color:#032F62">"DB"</span><span style="color:#24292E">],</span></span>

<span class="line"><span style="color:#005CC5"> "includeDBs"</span><span style="color:#24292E">: [</span><span style="color:#032F62">"DB1-DB50"</span><span style="color:#24292E">],</span></span>

<span class="line"><span style="color:#005CC5"> "excludeNames"</span><span style="color:#24292E">: [</span><span style="color:#032F62">"%EXCLUDE_TOKEN%"</span><span style="color:#24292E">]</span></span>

<span class="line"><span style="color:#005CC5"> "classification"</span><span style="color:#24292E">: {</span></span>

<span class="line"><span style="color:#005CC5"> "alarmRules"</span><span style="color:#24292E">: [{ </span><span style="color:#005CC5">"namePatterns"</span><span style="color:#24292E">: [</span><span style="color:#032F62">"%ALARM_TOKEN%"</span><span style="color:#24292E">], </span><span style="color:#005CC5">"setAlarmEnabled"</span><span style="color:#24292E">: </span><span style="color:#005CC5">true</span><span style="color:#24292E"> }],</span></span>

<span class="line"><span style="color:#005CC5"> "trendRules"</span><span style="color:#24292E">: [{ </span><span style="color:#005CC5">"namePatterns"</span><span style="color:#24292E">: [</span><span style="color:#032F62">"%TREND_TOKEN%"</span><span style="color:#24292E">], </span><span style="color:#005CC5">"setArchiveEnabled"</span><span style="color:#24292E">: </span><span style="color:#005CC5">true</span><span style="color:#24292E"> }]</span></span>

</article>

<h3 id="export-item-8">Preview versus formal output</h3>

<p><code>--preview</code> 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 <code>preview-report.json</code>, not communication-import files. Omit <code>--preview</code> to apply rules and export data and reports. Import counts also depend on address evidence and types.</p>

</article>

<h3 id="export-item-9">What is not exported</h3>

<p>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.</p>

</article>

<h3 id="export-item-10">Why something may be missing</h3>

<p>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.</p>

</article>

<h3 id="export-item-11">What to check when a DB is missing</h3>

<p>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.</p>

</article>

<h3 id="export-item-12">Choose the right format</h3>

<p>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.</p>

</article>

<p>Include the exported file, project source, selected scope, rule notes, and any assumptions used during the scan.</p>

</article>

</div></div>