Mingcedar and the Mingcedar Runtime Platform

Mingcedar is an industrial HMI / SCADA runtime platform integrating device acquisition, screen publication, alarms and trends, Python, read-only data APIs, and directional Site federation. Review capabilities, site deployment limits, and deployment preparation.

• Device connectivity and Tags
• Screens, navigation, and media
• Alarms, trends, and sound
• Calculated Tags
• Python projects and read-only APIs
• Site federation and configuration governance

A runtime unit contains five independently supervised services: Web/App, HQControlIO, HQControlAlarm, HQControlTrend, and HQControlScript. They share the unit’s database, Redis, configuration, and permissions. Restarting Web/App alone preserves the four runtime services; whole-unit maintenance coordinates shutdown and recovery.

Mingcedar is an industrial HMI / SCADA runtime platform integrating device acquisition, screen publication, alarms and trends, Python, read-only data APIs, and directional Site federation.

• Device connectivity and Tags: Connect Siemens S7, OPC UA, Modbus TCP, and internal values, with an optional separate S7Plus driver. Configure protocols, import Tags, diagnose quality, and authorize writes.
• Screens, navigation, and media: Publish Mingcedar Studio packages and custom HTML with version history, menus, popups, and video channels. A separate Screen Origin isolates pages from administration.
• Alarms, trends, and sound: Configure alarm conditions, severity, acknowledgement, recovery, and sound outputs. Record trends on change, on a cycle, or both. Choose Tags and time ranges separately for historical comparison, or pause realtime comparison to inspect changes. Use charts, data tables, and CSV / PNG exports, with quality gaps preserved.
• Calculated Tags: Combine local inputs into independent read-only numeric or Boolean results, with expression validation, publication, enablement, and ReadCalculatedTag access.
• Python projects and read-only APIs: Standard CPython 3.13 supports scheduled, HTTP inbound, and IO-event tasks with offline project dependencies. IO State API V2 provides scoped reads and subscriptions through Profiles and Access Keys.
• Site federation and configuration governance: Select remote IO, Alarm, Trend, and Screens directionally using stable TagRefs. Configuration releases, audit events, roles, and retention support engineering maintenance.

Collection ownership is coordinated per PLC definition within one runtime unit; independent sites do not automatically coordinate the same physical PLC. Ordinary federation shares remote capabilities. The current dedicated-node mode requires same-machine data services and does not provide an installable cross-PC primary/standby setup.

Before deployment, check the platforms, protocols, and installation modes in the release notes, then verify collection, screens, alarms, trends, and recovery in the target environment.

Guides explain the question boundary; installation, configuration, and delivery operations continue in the formal pages.