Use it when the project needs PowerPoint-based HMI source files and screen package export.
Mingcedar Studio
Mingcedar Studio runs inside PowerPoint, using .pptx for industrial screens while configuring animation, interaction, JavaScript, templates, charts, video, and data bindings before exporting Mingcedar-ready screen packages.
Keeps pages, templates, behaviors, scripts, and export output in one workflow.
Runtime data, permissions, alarms, trends, and deployment are handled in Mingcedar.
Main capability overview
Review the scope of animation, scripting, templates, charts, video, and export here, then open the user guide for detailed configuration and complete options.
Configure state color, blinking, range color, move, rotate, scale, visibility, and quality overrides so tag values directly drive screen behavior.
Maintain reusable screen structures and chart templates with data series, tags, units, precision, JSON field mapping, titles, legends, and grid options.
Configure an on-demand media URL or live connection. Cameras can use Mingcedar media channels. Media must be accessible from the runtime; video files are not copied with the screen package automatically.
Maintain shared logic for the current page in Page Script and configure click, hover, press, and release behaviors. Use the dedicated actions for Tag writes, links, and popups.
Use full-package export, current-page export, export history, and batch replacement for either a formal release or a focused field update.
Industrial screen configuration and publishing
The interactions and images below illustrate product features. Configure data, permissions, and media services in the target Mingcedar environment and verify operation using the manual.
Product Usage Path
Start with the task at hand, then review installation, configuration, usage, and acceptance details for this product.
Build pages, templates, popups, and behavior in PowerPoint.
Choose chart templates, then bind tag series or JSON field mapping.
Generate the screen package for later runtime loading.
Deliver the package to Mingcedar for tags, permissions, and runtime.
Platforms and boundaries
Mingcedar Studio is an independent add-in. Microsoft PowerPoint must be installed and licensed separately. Third-party product names identify runtime requirements and do not imply certification, endorsement, or partnership.
Windows and Office versions
The plugin runs in Microsoft PowerPoint 2016 or later for Windows desktop, including Microsoft 365 desktop PowerPoint. PowerPoint for Mac, the web, and mobile devices are outside the installation scope.
Install and bitness
The plugin installs for the current Windows user and supports 32-bit (x86) and 64-bit (x64) PowerPoint. Bitness refers to the PowerPoint application. After installation, confirm that the ribbon, Behavior Browser, and editors open correctly.
Licensing
Supports online activation and verification, plus offline request export and certificate import. Production credentials and keys should be managed securely.
Pre-delivery check
Use a sample project to verify behavior saving, script validation, preview, full export, and current-page export against the target Mingcedar version.
Continue
Continue to the complete user guide, installer, and version information.