Mingcedar Scan
A free, standalone offline TIA project point-preparation tool. Read standard-layout DBs from a local project or archive, turn scalar points, symbolic paths, absolute addresses, and types into reviewable lists, then export Excel, CSV, or JSON.
Useful for early project inventory, system migration, brownfield upgrades, and delivery-list preparation.
Use it before Mingcedar. For another SCADA/HMI or custom system, map and validate against that target's own specification.
Extract, filter, and review rules in batches to reduce copying mistakes and import rework.
Mingcedar Scan prepares standard-DB points and neutral exports; it does not promise import compatibility with third-party software.
When to use Mingcedar Scan
Use Mingcedar Scan independently whenever a TIA project needs point preparation—during early inventory, migration, modernization, or delivery review. The UI exports Excel, CSV, or JSON; the CLI creates Mingcedar-compatible JSON, while third-party formats require separate transformation.
Prepare scalar points, absolute addresses, and verification status from standard-layout DBs in a TIA project or archive.
Mingcedar is not required. Use Mingcedar Scan independently once the engineering project can be read.
Export Excel, CSV, and JSON in the UI; the CLI also produces Mingcedar-compatible JSON and reports.
From engineering project to usable point list
Move point copying, address review, and classification into one free tool, then map the neutral result to the requirements of the downstream workflow.
Read scalar members, addresses, and data types from standard-layout global and instance DBs in batches.
Use project-tree scope, DB ranges, PLC names, keep rules, and exclusion rules before handing data to another tool or engineer.
Export Excel, CSV, or JSON from the desktop UI. Use the CLI for Mingcedar-compatible Tag, alarm, and trend JSON.
The current scan workspace and Rule Center
See the current public interface for project selection, DB scope, point results, and rule configuration without decorative overlays.
Select the TIA project, standard-DB scope, and project-tree scope, then review points, addresses, types, and export state in one workspace.
Use keep, exclude, alarm, and trend rules to prepare results in batches instead of editing rows one by one.
Product Usage Path
Start with the task at hand, then review installation, configuration, usage, and acceptance details for this product.
Prepare a TIA project or archive that opens correctly on the engineering machine.
Scan DB points and narrow results through rules and filters.
Choose Excel, CSV, or JSON in the UI. Use the CLI for Mingcedar-compatible JSON; map other systems separately.
Platform and dependencies
The current public UI scans local TIA projects or archives only and does not connect to a live PLC. It depends on the local engineering environment, service state, and access permissions.
Platform
Mingcedar Scan targets Windows x64 desktop environments and requires .NET Framework 4.8.
Dependency
TIA Portal must open the target project, Automation License Manager must be running, and the Windows user needs Openness access. Permission repair requires administrator elevation and usually a Windows sign-out/sign-in.
Version records
Only proven standard-layout DBs are scanned; optimized or unknown layouts are skipped. Match the Scan build, TIA, and Openness API. Older projects from V14 onward use migration paths supported by TIA; migrate pre-V14 projects first, and use the V21 build for V21 projects.
Use cases without downstream lock-in
Use Mingcedar Scan for free whenever a TIA project needs a reviewable point list.
Prepare data for another SCADA or HMI
Export Excel, CSV, or JSON, then map the fields required by the target. Mingcedar Scan does not validate third-party import compatibility.
Prepare Mingcedar imports
When Mingcedar is the target, review Tag, alarm, and trend candidates before generating compatible JSON through the CLI.
Create an engineering handover list
Turn PLC points, addresses, and types into a reviewable list for design review, handover, or project records.
Continue
Continue with environment checks, scanning, rule review, and reusable result export.