Product: Mingcedar Scan SCAN

Mingcedar Scan Manual | Prepare reviewable standard-DB points from a TIA project

Mingcedar Scan independently reads scalar members, symbolic paths, absolute addresses, and data types from proven standard-layout DBs in a TIA project. Results can be mapped into a later workflow without deploying Mingcedar.

Published 2026-10-25T12:48:42.53666864Z Updated 2026-10-25T12:48:42.536667618Z

<div class="manual-doc-article"><h1 id="prepare-reviewable-standard-db-points-from-a-tia-project">Prepare reviewable standard-DB points from a TIA project</h1>

<p>After confirming TIA Portal, Automation License Manager, and Openness access, scan scalar members of standard-layout DBs and review symbolic paths, absolute addresses, address verification status, and data types.</p>

<p>Mingcedar Scan guide for free standalone extraction of standard-layout DB points, environment checks, scan boundaries, rule review, and result export.</p>

</blockquote>

<h2 id="manual-snapshot">Manual Snapshot</h2>

<ul>

<li>TIA / Openness environment check</li>

<li>Free standalone tool</li>

<li>Standard DB / address evidence</li>

</ul>

<h2 id="key-facts">Key Facts</h2>

<ul>

<li><strong>Prerequisites:</strong> TIA Portal / .NET 4.8 / Openness</li>

<li><strong>Scan mode:</strong> Offline project scan only</li>

<li><strong>Export formats:</strong> Excel / CSV / JSON</li>

</ul>

<h2 id="choose-by-goal">Choose by Goal</h2>

<p>Choose a goal to find its settings.</p>

<h3>Process only specified PLCs or DBs in a large project</h3>

<div><dt>Recommended feature</dt><dd>Scope</dd></div>

<div><dt>Why</dt><dd>A smaller scope reduces scanning and review time.</dd></div>

<div><dt>How</dt><dd>Select the required PLCs or DBs in the project tree; enter DB10-DB20 for a continuous DB range.</dd></div>

</dl>

</article>

<h3>Exclude backup, history, and other non-delivery points</h3>

<div><dt>Recommended feature</dt><dd>Rule Center</dd></div>

<div><dt>Why</dt><dd>Apply consistent filters to rows in bulk.</dd></div>

<div><dt>How</dt><dd>Use keep-name rules to define the target set, then exclude unrelated points with verified naming fragments from the project.</dd></div>

</dl>

</article>

<h3>Set alarm and trend classifications before export</h3>

<span class="doc-goal-cat">Rules</span>

<div><dt>Recommended feature</dt><dd>Export Rules</dd></div>

<div><dt>Why</dt><dd>Alarm and trend classification fields are included with the exported point.</dd></div>

<div><dt>How</dt><dd>Match display-name or normalized-code fragments in Rule Center, then set the alarm or trend flag.</dd></div>

</dl>

</article>

<h3>Determine why a DB is absent from the result</h3>

<div><dt>Recommended feature</dt><dd>DB Boundaries</dd></div>

<div><dt>Why</dt><dd>Standard-layout proof, scan scope, read access, data type, address resolution, and rules all affect the result.</dd></div>

<div><dt>How</dt><dd>Check DB layout first, then project-tree scope, read status, data type, address status, and exclusion rules.</dd></div>

</dl>

</article>

<h3>Send points to another SCADA, HMI, or custom system</h3>

<span class="doc-goal-cat">General</span>

<div><dt>Recommended feature</dt><dd>Reusable Result Export</dd></div>

<div><dt>Why</dt><dd>Mingcedar Scan does not require Mingcedar. Excel, CSV, and JSON can continue into other engineering workflows.</dd></div>

<div><dt>How</dt><dd>Review the result, choose Excel, CSV, or JSON, then map fields for the target system.</dd></div>

</dl>

</article>

<h3>Prepare import data for Mingcedar</h3>

<div><dt>Recommended feature</dt><dd>CLI batch output</dd></div>

<div><dt>Why</dt><dd>A non-preview CLI scan creates Mingcedar-compatible import files.</dd></div>

<div><dt>How</dt><dd>Review the project, scan scope, and rules, then run the CLI without preview mode and check the import files in its output folder.</dd></div>

</dl>

</article>

</div>

<h2 id="before-you-start">Before You Start</h2>

<p>Mingcedar Scan independently reads scalar members, symbolic paths, absolute addresses, and data types from proven standard-layout DBs in a TIA project. Results can be mapped into a later workflow without deploying Mingcedar.</p>

<p>Extract scalar points, symbolic paths, absolute addresses, and types from standard-layout DBs. Map and validate fields before using them in a third-party system.</p>

</article>

<h3 id="preface-item-2">Supported scope</h3>

<p>The desktop app scans proven standard-layout global and instance DBs only. Optimized or unknown-layout DBs, plus I, Q, and M address areas, do not enter the result.</p>

</article>

<h3 id="preface-item-3">Prerequisites</h3>

<p>Use Windows x64 with .NET Framework 4.8, TIA Portal that can open the target project, a running Automation License Manager service, and a Windows user with Openness access. Permission repair needs administrator elevation and usually a Windows sign-out/sign-in.</p>

</article>

</div>

<h2 id="tutorial">Recommended Scan Workflow</h2>

Check the environment, select the project, narrow the scan scope, review results, apply rules, and export.

<h3>Check TIA Portal and permissions</h3>

<p>Confirm .NET Framework 4.8, TIA Portal, Automation License Manager, and the current user's Openness access. Sign out and back in after permission repair.</p>

</article>

<h3>Select the TIA project</h3>

<p>Choose the TIA project and verify its full path. Save a result session for later review, or choose the file location when exporting the current result.</p>

</article>

<h3>Limit the scan scope</h3>

<p>Select the required PLC, standard-layout DBs, or project-tree branches, then choose all standard DB points or only members marked HMI/OPC accessible.</p>

</article>

<h3>Scan and review the result table</h3>

<p>Check symbolic addresses, absolute addresses, data types, scan periods, and result count before exporting.</p>

</article>

<h3>Filter and review rules</h3>

<p>Use selection, filtering, and Rule Center to keep the reviewed delivery set focused.</p>

</article>

<h3>Export the final result</h3>

<p>Export to Excel for manual review, or CSV / JSON for program processing and system import.</p>

</article>

</div></div>