Confirm Windows x64, .NET 4.8, TIA Portal, Automation License Manager, and Openness access first.
Mingcedar / TIA
TIA / PLC DB Point Extraction
Explains how Mingcedar Scan reads scalar points offline from proven standard-layout DBs in TIA Portal projects, then applies scope, rule review, and result export.
Project-tree, PLC, DB-number, and access-attribute scope affect the result, but the address area is fixed to DB.
The GUI exports one Excel, CSV, or JSON file; the CLI creates Mingcedar-compatible JSON.
TIA
Guide
Before extracting points, review environment access, scan scope, result fields, and export requirements.
TIA TIA / PLC DB Point Extraction
Mingcedar Scan is a standalone tool that reads a local TIA project or archive without connecting to a live PLC. Standard-DB scalar results include symbolic paths, absolute addresses, and verification status. Unverified rows remain available for review; communication imports require address and type checks. Optimized/unknown layouts, I/Q/M, and members without a constructed address are excluded.
- Confirm Windows x64, .NET 4.8, TIA Portal, Automation License Manager, and Openness access first.
- Project-tree, PLC, DB-number, and access-attribute scope affect the result, but the address area is fixed to DB.
- The GUI exports one Excel, CSV, or JSON file; the CLI creates Mingcedar-compatible JSON.
Preparation
Mingcedar Scan runs on Windows x64 engineering workstations and requires .NET Framework 4.8, TIA Portal that can open the project, a running Automation License Manager service, and Openness access for the current user.
- Match the Scan build, installed TIA, and Openness API. Older projects from V14 onward can use the migration paths supported by TIA; V21 projects require the V21 build.
- Confirm Automation License Manager and Openness access.
- Keep the project or archive at a stable local path and verify the resolved full path.
Scan and review
After scanning, review the result project, standard-layout DB scope, symbolic path, absolute address and verification status, byte/BOOL bit offsets, data type, and rule matches before retaining points for export.
- Scan standard-layout global and instance DBs in local TIA projects or archives only.
- Do not scan through a PLC IP or live protocol; I/Q/M do not enter results.
- Result-table search and Rule Center use different fields and wildcard rules.
Export results
Export Current Result in the desktop UI saves one .xlsx, .csv, or .json file. Only a non-preview CLI scan creates normalized-tags, Mingcedar-compatible JSON, generic-tags, report, and export-manifest files. Other SCADA/HMI or custom systems require mapping and validation against their official specifications.
Next Open product, manual, or downloads
Guides explain the question boundary; installation, configuration, and delivery operations continue in the formal pages.