Why Some DBs Are Not Scanned or Exported | Mingcedar Scan

<div class="manual-doc-article manual-doc-article-section"><h2 id="db-scan-boundary">DB: Why Some DBs Are Not Scanned or Exported</h2>

For missing DBs, check layout, scope, read status, types, addresses, and rules.

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

<article class="doc-card">

<h3 id="db-scan-boundary-item-1">How DBs enter the result</h3>

<p>A DB must have proven standard layout, be inside the selected scope, and be readable through Openness. Members must resolve to supported scalar types and absolute addresses. Results may include unverified rows; communication-import generation additionally checks address evidence, type support, and code uniqueness.</p>

</article>

<article class="doc-card">

<h3 id="db-scan-boundary-item-2">Check scope first when a DB is missing</h3>

<p>When a DB is missing, first confirm standard layout, then check project-tree, PLC and DB-number scope, Openness read status, the HMI/OPC-access option, and exclusion rules. Optimized and unknown-layout DBs are skipped as whole blocks.</p>

</article>

<article class="doc-card">

<h3 id="db-scan-boundary-item-3">Only standard-layout DBs are accepted</h3>

<p>Optimized layouts, unknown layouts, and members without a constructed absolute address are skipped with a recorded reason. Members with an address but insufficient evidence can remain as <code>absolute_unverified</code> review rows; they are excluded from communication imports.</p>

</article>

<article class="doc-card">

<h3 id="db-scan-boundary-item-4">Structured data is organized by scalar members</h3>

<p>UDTs, structs, arrays, and nested objects in standard DBs are organized as resolvable scalar children. Arrays expand by index. Addresses derived from layout or array strides may remain unverified; successful expansion does not make them eligible for communication import.</p>

</article>

<article class="doc-card">

<h3 id="db-scan-boundary-item-5">Duplicate array members</h3>

<p>Arrays expand by index; duplicate members returned by the engineering interface are removed.</p>

</article>

<article class="doc-card">

<h3 id="db-scan-boundary-item-6">Access settings define the deliverable scope</h3>

<p>A DB or member needs engineering attributes readable through TIA Openness. The HMI/OPC-accessible option further filters those attributes; it is project-metadata filtering and does not validate a live connection or third-party import.</p>

</article>

<article class="doc-card">

<h3 id="db-scan-boundary-item-7">Investigate missing points</h3>

<p>If an expected point is missing, check the scan report, DB layout, selected scope, read status, access attributes, data type, address resolution, rules, and manual deletions.</p>

</article>

</div>

</div>