Mingcedar

Product: Mingcedar Studio DESIGNER

Mingcedar Studio Manual

This manual covers industrial screen authoring in PowerPoint, data and interaction configuration, export and publishing. Start with Create your first screen.

Published Updated

<div class="manual-doc-article"><h1 id="author-industrial-screens-inside-powerpoint">Author industrial screens inside PowerPoint</h1>

<p>Create screens, reusable templates, live-data bindings, and interaction behavior in PowerPoint, then export HTML / SVG / JS screen packages for Mingcedar.</p>

<blockquote>

<p>Mingcedar Studio manual for authoring industrial screens in PowerPoint, configuring runtime behavior, exporting pages, and publishing assets to Mingcedar.</p>

</blockquote>

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

<ul>

<li>PowerPoint plugin</li>

<li>Screen authoring</li>

<li>Runtime export</li>

<li>Templates / Scripts</li>

</ul>

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

<ul>

<li><strong>Color · geometry · interaction · text:</strong> One behavior set</li>

<li><strong>Package format:</strong> HTML / SVG / JS</li>

<li><strong>Data source:</strong> Mingcedar live tags</li>

</ul>

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

<p>Choose the current goal to find the matching behavior and key fields.</p>

<div class="doc-goal-grid">

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

<span class="doc-goal-icon"><svg viewBox="0 0 24 24" aria-hidden="true" focusable="false"><path d="M12 5a7 7 0 1 0 7 7h-3a4 4 0 1 1-4-4V5Z"></path><path d="M12 2v10h10"></path></svg></span>

<h3>Turn a pump green when running, gray when stopped</h3>

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

<dl class="doc-goal-lines">

<div><dt>Recommended feature</dt><dd>State Color</dd></div>

<div><dt>Why</dt><dd>For two states, on and off, State Color is the direct option.</dd></div>

<div><dt>How</dt><dd>Enter ReadTagBoolean("PLC_LINE01.PUMP01.RUN", false) in Condition and configure running and stopped colors.</dd></div>

</dl>

</article>

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

<span class="doc-goal-icon"><svg viewBox="0 0 24 24" aria-hidden="true" focusable="false"><path d="M4 7h16v10H4z"></path><path d="M8 7V4h8v3M8 20h8"></path></svg></span>

<h3>Make it blink on alarm</h3>

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

<dl class="doc-goal-lines">

<div><dt>Recommended feature</dt><dd>Blink Color</dd></div>

<div><dt>Why</dt><dd>Blinking is suitable for alarm states that need a clear visual cue.</dd></div>

<div><dt>How</dt><dd>Enter a Boolean condition and configure Blink ON and Blink OFF. Enable FALSE for a static Condition FALSE appearance. Blink Color has no blink-interval setting.</dd></div>

</dl>

</article>

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

<span class="doc-goal-icon"><svg viewBox="0 0 24 24" aria-hidden="true" focusable="false"><path d="M5 18V7l7-4 7 4v11l-7 4-7-4Z"></path><path d="M9 12h6M12 9v6"></path></svg></span>

<h3>Display colors by numeric range</h3>

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

<dl class="doc-goal-lines">

<div><dt>Recommended feature</dt><dd>Range Color</dd></div>

<div><dt>Why</dt><dd>Range Color maps each interval to a configured color.</dd></div>

<div><dt>How</dt><dd>Define a few value ranges, one color per band.</dd></div>

</dl>

</article>

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

<span class="doc-goal-icon"><svg viewBox="0 0 24 24" aria-hidden="true" focusable="false"><path d="M4 17h16"></path><path d="m6 14 4-4 3 3 5-7"></path></svg></span>

<h3>Show a live value or text</h3>

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

<dl class="doc-goal-lines">

<div><dt>Recommended feature</dt><dd>Tag Text</dd></div>

<div><dt>Why</dt><dd>Displays one Tag's current value with an optional prefix or suffix.</dd></div>

<div><dt>How</dt><dd>Enter the full Tag name in Target tag. See Variables, Tags, and template parameters for dynamic names and = syntax.</dd></div>

</dl>

</article>

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

<span class="doc-goal-icon"><svg viewBox="0 0 24 24" aria-hidden="true" focusable="false"><path d="M4 5h16v12H4z"></path><path d="M9 21h6M12 17v4"></path></svg></span>

<h3>Write a value to the PLC on click</h3>

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

<dl class="doc-goal-lines">

<div><dt>Recommended feature</dt><dd>Write Tag</dd></div>

<div><dt>Why</dt><dd>A click action can write the configured value back to the PLC.</dd></div>

<div><dt>How</dt><dd>Pick the target tag and value; use Write Tag Bit for a single bit.</dd></div>

</dl>

</article>

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

<span class="doc-goal-icon"><svg viewBox="0 0 24 24" aria-hidden="true" focusable="false"><path d="M8 12h8M12 8v8"></path><path d="M4 12a4 4 0 0 1 4-4h1M20 12a4 4 0 0 1-4 4h-1"></path></svg></span>

<h3>Build a popup or numeric keypad</h3>

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

<dl class="doc-goal-lines">

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

<div><dt>Why</dt><dd>Popups, keypads, and tables are reusable template sets.</dd></div>

<div><dt>How</dt><dd>Author a template with placeholders, then set the template parameters for each instance.</dd></div>

</dl>

</article>

</div>

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

<p>This manual covers industrial screen authoring in PowerPoint, data and interaction configuration, export and publishing. Start with Create your first screen.</p>

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

<article class="doc-card">

<h3 id="preface-item-1">Scope</h3>

<p>For screen authors, implementation engineers and developers. Authoring requires Windows PowerPoint; runtime verification requires Mingcedar. Advanced scripting chapters assume basic JavaScript knowledge.</p>

</article>

<article class="doc-card">

<h3 id="preface-item-2">Example conventions</h3>

<p>Menu and field names match the English interface; → indicates a navigation path. Code blocks identify their destination. Preserve straight quotes, brackets and identifier case. Replace example Tag names with configured project names. Click interface images to enlarge them.</p>

</article>

</div>

<h2 id="tutorial">Getting started and progressing</h2>

Complete authoring and publishing before connecting live data and reusing components. Follow the linked tutorial for each stage.

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

<article class="doc-card">

<h3>1. Install and activate</h3>

<p>Install the add-in, verify MX Design and licensing, and prepare the Mingcedar runtime.</p>

<ul class="doc-related-links">

<li><a href="/en/ppt/manual/windows-install/">Installation</a></li>

</ul>

</article>

<article class="doc-card">

<h3>2. Create and publish a first screen</h3>

<p>Connect buttons, an indicator and text with a page variable, then export, publish, configure a menu and verify. No PLC is required.</p>

<ul class="doc-related-links">

<li><a href="/en/ppt/manual/first-screen/">First-screen tutorial</a></li>

</ul>

</article>

<article class="doc-card">

<h3>3. Connect live data</h3>

<p>Verify Tag names, types, read access and quality, then compare the display with platform data.</p>

<ul class="doc-related-links">

<li><a href="/en/ppt/manual/text-tag-text/">Tag Text</a></li>

</ul>

</article>

<article class="doc-card">

<h3>4. Reuse components and pass parameters</h3>

<p>Distinguish template parameters, page variables and page parameters, then continue with Input, Table, bit writes and popups.</p>

<ul class="doc-related-links">

<li><a href="/en/ppt/manual/design-reuse-guide/">Reuse methods and parameters</a></li>

</ul>

</article>

</div></div>