Choose a path, complete a working screen, then consult field references and advanced tutorials.
Draw in PowerPoint, add behaviors and templates, export HTML / SVG / JS, and load the package in Mingcedar. The plugin authors screens; the host supplies data and controls access. PowerPoint native animation and presentation playback are outside the exported behavior contract.
Expected result Identify the authoring environment, runtime requirements and required features before starting a project.
Create a screen with page variables, name components, bind behaviors, then export and publish. No PLC is needed; publishing and runtime checks require Mingcedar.
Expected result Two buttons switch the indicator and text; reloading restores the initial state. Then proceed to live Tag displays.
Use template placeholders for design-time differences, runtime variables for current-page state, and page parameters for navigation context. A Tag-name string is an address; reading it and writing to it are separate operations.
Scroll horizontally to view the full table
| Need | Mechanism | When it takes effect |
|---|---|---|
| Reuse the same pump for PUMP01 / PUMP02 | <PLC> / <DEVICE> template fields | Configure each template instance before export |
| Switch a target while the page stays open | Page Script variable and a supported expression field | Runtime evaluation |
| Open details for the selected device | Navigation parameters and GetPageParameter | Destination page opens |
| Show a filtered table | Page Script function returning an array | Table data evaluation |
Expected result Two instances use different targets, and a parameterized page accepts only the intended devices.
Page Script is shared within one page; Setup Script prepares one behavior’s values. Expressions must return immediately. Declare every candidate dynamic Tag name for export; host permissions and confirmation still apply.
