Make sure the plugin version, PowerPoint version, and license state are readable. Fix licensing first if it is unavailable.
Manual
Mingcedar Studio Troubleshooting
Check installation, licensing, export, scripts, Tags, variables, template parameters, and video by symptom. When the ribbon is available, start with version and license details in Status.
Three checks before troubleshooting
When the ribbon is available, open Status on the Mingcedar Studio ribbon. If the ribbon is missing, run Doctor in the installer and repair the installation according to its diagnostics.
Choose the section for installation, licensing, export, scripts, data bindings, or media.
Change one setting, retest in PowerPoint, and record the result.
The license is abnormal or unavailable after activation
Confirm the license mode, then check the service address, account state, offline certificate, and machine match.
If Status shows unlicensed or unavailable, handle licensing first. For online licensing, also check whether the license service is reachable.
Confirm the license service URL, account state, and network access. If the server revokes a license, the plugin disables related windows.
The offline certificate must match the current machine and user environment. If it does not match, export a new offline request and issue a new certificate.
- Generate a new offline request after changing computers
- After import, check Status again and confirm the license is available
- Use the production license service configuration in production
The exported page differs, replacement is wrong, or images are stale
Confirm the export mode, then check page objects, template instances, image assets, and shared runtime assets.
Full export is for release or large changes. Current-page export is for local replacement. Use full export when shared structure, navigation, or shared assets change.
Decide whether the change belongs to page objects, template instances, or image assets. Re-export the current page for object changes; use full export for shared assets or structure changes.
Verify the screen package in the target Mingcedar environment. Static preview can check layout; live data, write permissions, alarms, trends, and media services require the host runtime.
- Confirm package structure and assets after full export
- For current-page updates, check both the changed and preserved pages
- Verify data, permissions, and interactions in the target Mingcedar before replacing production screens
A script fails or a saved configuration does not take effect
Confirm where the script is written, then check whether the field expects full JavaScript, a synchronous expression, or pure JSON.
Page Script, Click Script, Press/Release Script, and Hover Script can contain full JavaScript. Animation, color, and condition expressions return synchronous results. Tag writes are allowed only during real user click, press, or release actions.
Use fetch and other asynchronous logic in page or interaction scripts. Expression fields in Move, Rotate, Scale, Script Color, and Condition return synchronous results. await must be inside an async function.
Check the syntax diagnostics first, then confirm whether the editor expects a full script or one expression. alarm.js is also a page JavaScript document.
Put same-page helpers in Page Script. Use built-in button behaviors, adding scripts when needed.
- Initialize in hqVisuDesignerPageReady
- Keep asynchronous logic in script fields and expression results synchronous
- Call WriteTag only during real user click, press, or release actions; not in Page Script, Definition, or Hover Script
A name is treated as a value, a parameter is unresolved, or a calculated Tag cannot be read
Confirm whether the field expects a name or a value, then check the return type, variable scope, and substituted template parameters.
Name fields such as Target tag accept full fixed names, for example PLC_LINE01.TANK01.LEVEL. Dynamic names must return a name string using the syntax supported by the field. Value fields such as Condition and Source value require a boolean or number; use the appropriate ReadTag method to read a Tag value.
A leading = marks an expression only in configuration fields that support it. It is not JavaScript API argument syntax. <PLC> and <TAG> are substitution parameters, not runtime variables. Confirm the instance parameters were substituted, then inspect the resulting field content.
Use ReadCalculatedTag("Line01TotalFlow", null) with the host calculated Tag name and no PLC prefix. Confirm the Tag exists, is enabled, and has produced a result in Mingcedar. Handle null according to the chosen fallback policy. Calculated Tags cannot be write targets for Write Tag or a PLC Tag input template.
Reading a Tag once at the top level of Page Script captures the initialization value. Live behaviors should call a read method or same-page read function on each evaluation. When a runtime variable drives a behavior, check how that variable is updated and where it is in scope.
Video plays on the design computer but fails after publishing
Check the media URL, deployed files, media channel, permissions, encoding, and browser support from the runtime device.
A local video file is not copied into the screen package and blocks export. Deploy the media to a location accessible from the runtime, replace the local file with a direct HTTP(S) media URL, then export. An ordinary web page URL is not a media URL.
For a Mingcedar media channel, confirm that the channel is enabled and accessible. Browsers cannot play a raw RTSP URL directly. Select the connection method described in the video template guide and check HTTPS, cross-origin access, playback permissions, and media encoding.