Product: Mingcedar Studio DESIGNER

What Mingcedar Studio Is: Product Positioning and End-to-End Flow | Mingcedar Studio

Use Mingcedar Studio in PowerPoint to create industrial screens, configure data and interactions, and export packages for Mingcedar.

Published 2026-10-25T12:48:42.675294003Z Updated 2026-10-25T12:48:42.675293271Z

<div class="manual-doc-article manual-doc-article-section"><h2 id="overview-what-is-hqvisu-plugin">Overview: What Mingcedar Studio Is: Product Positioning and End-to-End Flow</h2>

Use Mingcedar Studio in PowerPoint to create industrial screens, configure data and interactions, and export packages for Mingcedar.

<h3 id="overview-what-is-hqvisu-plugin-item-1">What it is and what it gives you</h3>

<p>Use MX Design to draw pages, Behavior Browser to configure components, and templates to reuse device designs. Export HTML, SVG, JavaScript and images as a screen package. Mingcedar runs the package and manages data, navigation, permissions and deployment; Mingcedar Scan prepares TIA / PLC point lists.</p>

</article>

<h3 id="overview-what-is-hqvisu-plugin-item-2">Author and publish a screen</h3>

<p>1) Draw the page and set Page Ratio.

2) Drag behaviors onto components in Behavior Browser, configure fields, and add Page Script as needed.

3) Use Export HTML to export the presentation.

4) Publish to Mingcedar and verify runtime behavior.</p>

<p>Behavior fields are grouped by purpose:</p>

<ul>

<li>Setup Script: read Tags, define variables, or calculate intermediate values (for example, var running = ReadTagInteger(...)).</li>

<li>Condition / Value / Display Text: provide the condition, write value, or displayed text used by the behavior.</li>

<li>Fill / Border / Visibility: fill color, stroke color, show/hide (visual behaviors such as Script Color)</li>

<li>Tag Expression / Default / Invert: read-only fields for displaying tags and text; write behaviors use Target Tag, Value, Bit Index, and Action.</li>

<li>Variable / Value: write a runtime variable on click (Set Variable on Click; do not quote the variable name)</li>

<li>Targets: Keypad requires an Input template on the current page; Open Diagnosis requires a diagnosis target.</li>

</ul>

<div class="manual-code" data-code-language="javascript"><div class="manual-code-toolbar"><span>JavaScript</span><span class="manual-code-tools"><small>JavaScript</small><button type="button" data-copy-code data-copied="Copied" data-failed="Select and copy the code" aria-label="Copy code: JavaScript">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 style="color:#6A737D">// Setup Script (prep)</span></span>

<span class="line"><span style="color:#D73A49">var</span><span style="color:#24292E"> running </span><span style="color:#D73A49">=</span><span style="color:#6F42C1"> ReadTagInteger</span><span style="color:#24292E">(</span><span style="color:#032F62">"PLC_LINE01.PUMP01.RUN"</span><span style="color:#24292E">, </span><span style="color:#005CC5">0</span><span style="color:#24292E">);</span></span>

<span class="line"><span style="color:#D73A49">var</span><span style="color:#24292E"> alarm </span><span style="color:#D73A49">=</span><span style="color:#6F42C1"> ReadTagBoolean</span><span style="color:#24292E">(</span><span style="color:#032F62">"PLC_LINE01.PUMP01.ALARM"</span><span style="color:#24292E">, </span><span style="color:#005CC5">false</span><span style="color:#24292E">);</span></span>

<span class="line"><span style="color:#6A737D">// Condition (output; State Color etc. use it for true/false)</span></span>

<span class="line"><span style="color:#24292E">running </span><span style="color:#D73A49">===</span><span style="color:#005CC5"> 1</span><span style="color:#D73A49"> &&</span><span style="color:#D73A49"> !</span><span style="color:#24292E">alarm</span></span></code></pre></div>

</article>

<p>Use it for industrial monitoring screens driven by PLC data, for example:</p>

<ul>

<li>Device-status screen: draw pump or valve shapes, bind State Color or Blink Color, read run and alarm Tags, and verify live status in Mingcedar.</li>

<li>Operator area: bind an Input template to a runtime variable or PLC Tag, then connect a Keypad template to that Input. Verify permissions and results for device writes.</li>

</ul>

</article>

<h3 id="overview-what-is-hqvisu-plugin-item-4">Before you begin</h3>

<p>Check these configuration and publishing requirements:</p>

<ul>

<li>You can only bind a behavior by dragging it onto a component node on the left; double-clicking an item in the right-hand catalog does not bind; it only shows: Drag a behavior onto a component node to bind it.</li>

<li>One presentation exports as one screen package. Re-export the full package when shared resources, page structure, or navigation change. Use This Page only for page-level changes.</li>

<li>Tag writes may require authorization, confirmation, or an audit reason. Check the actual result in Mingcedar after submitting a write.</li>

<li>For cross-package navigation use screen-code (hqVisuDesigner.openScreen(...)) and for same-package use hqVisuDesigner.openPage(...); do not use relative disk paths like ../../other-screen/index.html as the official jump rule.</li>

</ul>

</article>

</div>

<strong>Figure 1: MX Design workspace</strong>

<p>The MX Design ribbon exposes Browse Behaviors, Page Ratio, Page Script, Templates, Batch Replace, and Export HTML beside the Templates and Behavior Browser panes.</p>

</figcaption>

</figure>

</div>