Manual

Mingcedar Scan Manual | Prepare reviewable standard-DB points from a TIA project

Mingcedar Scan independently reads scalar members, symbolic paths, absolute addresses, and data types from proven standard-layout DBs in a TIA project. Results can be mapped into a later workflow without deploying Mingcedar.

Prepare reviewable standard-DB points from a TIA project

After confirming TIA Portal, Automation License Manager, and Openness access, scan scalar members of standard-layout DBs and review symbolic paths, absolute addresses, address verification status, and data types.

Mingcedar Scan guide for free standalone extraction of standard-layout DB points, environment checks, scan boundaries, rule review, and result export.

Manual Snapshot

TIA / Openness environment check
Free standalone tool
Standard DB / address evidence

Key Facts

Prerequisites: TIA Portal / .NET 4.8 / Openness
Scan mode: Offline project scan only
Export formats: Excel / CSV / JSON

Choose by Goal

Choose a goal to find its settings.

Process only specified PLCs or DBs in a large project

Step 3

Recommended feature: Scope
Why: A smaller scope reduces scanning and review time.
How: Select the required PLCs or DBs in the project tree; enter DB10-DB20 for a continuous DB range.

Exclude backup, history, and other non-delivery points

Step 5

Recommended feature: Rule Center
Why: Apply consistent filters to rows in bulk.
How: Use keep-name rules to define the target set, then exclude unrelated points with verified naming fragments from the project.

Set alarm and trend classifications before export

Rules

Recommended feature: Export Rules
Why: Alarm and trend classification fields are included with the exported point.
How: Match display-name or normalized-code fragments in Rule Center, then set the alarm or trend flag.

Determine why a DB is absent from the result

Recommended feature: DB Boundaries
Why: Standard-layout proof, scan scope, read access, data type, address resolution, and rules all affect the result.
How: Check DB layout first, then project-tree scope, read status, data type, address status, and exclusion rules.

Send points to another SCADA, HMI, or custom system

General

Recommended feature: Reusable Result Export
Why: Mingcedar Scan does not require Mingcedar. Excel, CSV, and JSON can continue into other engineering workflows.
How: Review the result, choose Excel, CSV, or JSON, then map fields for the target system.

Prepare import data for Mingcedar

Step 6

Recommended feature: CLI batch output
Why: A non-preview CLI scan creates Mingcedar-compatible import files.
How: Review the project, scan scope, and rules, then run the CLI without preview mode and check the import files in its output folder.

Before You Start

When to use it

Extract scalar points, symbolic paths, absolute addresses, and types from standard-layout DBs. Map and validate fields before using them in a third-party system.

Supported scope

The desktop app scans proven standard-layout global and instance DBs only. Optimized or unknown-layout DBs, plus I, Q, and M address areas, do not enter the result.

Prerequisites

Use Windows x64 with .NET Framework 4.8, TIA Portal that can open the target project, a running Automation License Manager service, and a Windows user with Openness access. Permission repair needs administrator elevation and usually a Windows sign-out/sign-in.

Recommended Scan Workflow

Check the environment, select the project, narrow the scan scope, review results, apply rules, and export.

Check TIA Portal and permissions

Confirm .NET Framework 4.8, TIA Portal, Automation License Manager, and the current user's Openness access. Sign out and back in after permission repair.

Select the TIA project

Choose the TIA project and verify its full path. Save a result session for later review, or choose the file location when exporting the current result.

Limit the scan scope

Select the required PLC, standard-layout DBs, or project-tree branches, then choose all standard DB points or only members marked HMI/OPC accessible.

Scan and review the result table

Check symbolic addresses, absolute addresses, data types, scan periods, and result count before exporting.

Filter and review rules

Use selection, filtering, and Rule Center to keep the reviewed delivery set focused.

Export the final result

Export to Excel for manual review, or CSV / JSON for program processing and system import.