Product: Mingcedar CONTROL

Tag Test: monitoring, quality, and writes | Mingcedar

Location: Configuration Center → Tag Test (io:diagnose permission). Select a Device on the left, browse Tags in the center, and monitor values or initiate writes on the right.

Published 2026-10-25T12:48:42.64190309Z Updated 2026-10-25T12:48:42.641902339Z

<div class="manual-doc-article manual-doc-article-section"><h2 id="tag-diagnostics">Operating guide: Tag Test: monitoring, quality, and writes</h2>

Add Tags to the monitor and inspect collected values, quality, time and write results.

<h3 id="tag-monitor">1. Select a Device and monitor a Tag</h3>

<p>Location: Configuration Center → Tag Test (io:diagnose permission). Select a Device on the left, browse Tags in the center, and monitor values or initiate writes on the right.</p>

<ol>

<li>Find and select the Device, checking code and protocol.</li>

<li>Filter the enabled-Tag list by name or address and verify code, address, and type.</li>

<li>Click Monitor tag or drag the row into the monitor.</li>

<li>After connecting, check value, quality and time. Add other Tags individually; remove those no longer needed.</li>

</ol>

<p class="doc-step-result"><strong>Expected result</strong> The monitor shows the target Tag’s connection and data state. An empty monitor may mean no Tags were added.</p>

</article>

<h3 id="tag-quality">2. Separate connection state from data quality</h3>

<p>Live connected describes the workspace connection, not the validity of every Tag.</p>

<ol>

<li>Inspect the connection first, then the Tag row’s quality and timestamp.</li>

<li>Compare good values with field values; zero can also be valid.</li>

<li>The row shows GOOD or BAD. Use Details for Waiting for data, No data, and source diagnostics. Check Tag and Device enablement, monitoring selection, and collection state.</li>

<li>If quality is BAD or the timestamp has not advanced, inspect Device connection, collection state, and the diagnostic detail; an older value is not proof of current validity.</li>

<li>Open Details for diagnostics; use Inspect full value for structured values.</li>

</ol>

<p class="doc-step-result"><strong>Expected result</strong> Distinguish unsubscribed, waiting, invalid and valid measurements.</p>

</article>

<h3 id="tag-write">3. Enter and confirm one write</h3>

<p>Writing requires a signed-in account with tag:write permission. The button is disabled when Tag control is off, live connection is unavailable, or quality is not GOOD; insufficient permission returns a denied result.</p>

<ol>

<li>Record the previous value and time and verify the target.</li>

<li>Click Write and enter a type-correct value within the displayed range.</li>

<li>Enter a reason when the field is marked required, compare the previous and target values, then click Confirm write once.</li>

<li>Read the result: Accepted is still pending confirmation, while Write completed and Readback confirmed mean different things. Then observe the collected value.</li>

<li>For uncertain results or readback mismatches, retain details and search Event Records by time, actor and Tag. Verify before repeating the command.</li>

</ol>

<p class="doc-step-result"><strong>Expected result</strong> Check command and readback results separately. Cancellation submits nothing; denial or uncertainty is not success.</p>

<div class="doc-step-troubleshooting"><p><strong>If the result differs</strong></p><ul>

<li>Write unavailable: check account permission, Allow Runtime Writes, live connection, and GOOD quality. For an unconfirmed result or readback mismatch, inspect the field value and Event Records first.</li>

</ul></div>

</article>

</div>

<strong>Figure 1: Tag Test monitor</strong>

<p>The monitor shows each Tag value, quality and sample time. Check both quality and time before relying on a value.</p>

</figcaption>

</figure>

</div>