Mingcedar

Connect Siemens S7, S7Plus, OPC UA, Modbus TCP, configurable-frame TCP/IP, and internal values. Import Tags in CSV, JSON, or NDJSON with a preview; supported points allow controlled writes.

Publish Mingcedar Studio screen packages or custom HTML pages, with menus, popups, video channels, and multilingual text. Runtime pages use a separate origin and read data within their declared scope.

View device connection, collection progress, Tag freshness, and quality separately. Calculated tags build read-only numeric or Boolean results from collected local values and can feed screens, alarms, and trends once published.

Detect exceptions with threshold, quality, deviation, rate-of-change, deadband, and delay rules; acknowledge, shelve, review history, and configure alert sounds. Set category number, name, color, and execution priority separately. Non-GOOD readings do not clear existing value alarms.

Record Tags on change, on a cycle, or both. Align historical periods by elapsed time, or compare samples received in the current session within the last 15 minutes. Use lines, steps, or data tables, with horizontal or vertical comparison layouts. Export CSV or chart PNG; invalid samples remain gaps.

Select remote screens, collection, alarms and trends independently, and choose a device scope for remote collection. Tags retain their source identity. Remote alarms over ordinary LAN connections are read-only; sign in to the source to acknowledge or shelve.

Inspect configuration application, PLC connectivity, collection status and the responsible node in Device details. Verify quality, timestamps and values after recovery. One runtime unit coordinates ownership of its PLC definitions; independent Sites do not automatically exclude each other.

Organize scripts and shared functions under scripts/ and common/, and distribute reusable code as a Wheel across projects. Projects include common bundled modules and accept offline Wheels or Wheel ZIP bundles, with dependency versions, updates, and removals managed per project.

IO State API V2 lets external applications read collected state and receive snapshots and incremental updates over WebSocket. Profiles organize shared signals; Access Keys authorize IO domains, devices, or Tags. Data retains quality and timestamps. The API provides reads and subscriptions only.

Combine live Tags, historical trends, and alarm queries in HTML, JavaScript, or built Vue pages. The SDK provides typed reads and writes, navigation, device popups, and language resources, within page declarations and current user permissions.

Assign roles with separate screen-access and operation permissions. Tag writes also require page scope, Tag control permission, and runtime checks, with confirmation according to policy.

System Status brings together services, device connections, continuously collected Tags, and CPU, memory, and disk use. Filter and export event records by time, source, and type. Script Status adds an overview and worker details, with execution results available in Records.