Narrow the scan scope | Mingcedar Scan

<div class="manual-doc-article manual-doc-article-section"><h2 id="scope">Step 3: Narrow the scan scope</h2>

Narrow the scope before a full project scan to improve speed and review efficiency.

<div class="doc-card-list">

<article class="doc-card">

<h3 id="scope-item-1">Available scope controls</h3>

<p>Limit by PLC, DB-number range, or DB branch in the project tree. The main window can scan all proven standard-layout DB members or further retain only members marked HMI/OPC accessible.</p>

</article>

<article class="doc-card">

<h3 id="scope-item-2">Use the standard-DB scope</h3>

<p>Choose all proven standard-layout DBs or keep only members explicitly marked HMI/OPC accessible, then narrow by DB number, PLC name, project tree, or excluded-name rules. I, Q, and M are outside the current scan scope.</p>

</article>

<article class="doc-card doc-card-warn">

<h3 id="scope-item-3">What belongs in excluded names</h3>

<p>Use excluded-name rules for backup, history, temporary, simulation, retired, or non-delivery naming fragments. Keep each rule reviewable and avoid short fragments that can remove unrelated points.</p>

</article>

<article class="doc-card">

<h3 id="scope-item-4">Why narrowing matters</h3>

<p>Large projects can produce many irrelevant points. A smaller first scan makes it easier to confirm the rule and address pattern.</p>

</article>

<article class="doc-card doc-card-tip">

<h3 id="scope-item-5">Suggested approach</h3>

<p>Follow these steps, verify the result, then expand the scope.</p>

<ul>

<li>Start from one PLC</li>

<li>Select only required tables or DBs</li>

<li>Run a small initial scan first</li>

</ul>

</article>

<article class="doc-card">

<h3 id="scope-item-6">DB-number range syntax</h3>

<p>Included and excluded DB ranges accept a single number or a continuous range, such as <code>1</code>, <code>DB1</code>, <code>10-20</code>, or <code>DB10-DB20</code>. Include ranges define the main scan set; exclude ranges remove DBs that should not be delivered. A range applies only when TIA metadata supplies a recognizable DB number.</p>

</article>

<article class="doc-card">

<h3 id="scope-item-7">Project-tree scope comes before rules</h3>

<p>The project-tree selection defines what is scanned; rules operate only on the points that were scanned. An unselected PLC, table, or DB cannot be added back by a matching rule.</p>

</article>

<article class="doc-card">

<h3 id="scope-item-8">HMI/OPC-accessible scope</h3>

<p>The HMI/OPC-accessible option checks member access attributes inside standard-layout DBs. It is not an online OPC scan and does not add optimized DBs or I, Q, and M areas to the result.</p>

</article>

</div>

<div class="docs-note-grid manual-doc-image-grid">

<figure class="docs-note-card manual-doc-image-card" id="scope-image-1">

<img src="/WEB_img/HQScan/main.png" alt="Mingcedar Scan DB scan scope and project-tree entry" loading="lazy" decoding="async" />

<figcaption>

<strong>Figure 1: Choose the DB scope before opening the project tree</strong>

<p>Select all standard DBs or only HMI/OPC-accessible DBs, then use the project tree to narrow the current PLC and DB scope.</p>

</figcaption>

</figure>

</div>

</div>