Overview
Engineers who maintained a WinCC V6.2 supervisory station and an MP377 operator panel on the same plant frequently ask whether the same screens, tags, and extras that exist in the SCADA project can be reused inside a WinCC flexible 2008 HMI project. The short answer is no: WinCC V6.2 and WinCC flexible 2008 are not the same product family, do not share a runtime, and do not expose a project-level import path. Graphics, tag databases, archives, scripts, and alarm logs must be recreated in WinCC flexible 2008. Only a small set of raster assets (BMPs, ICOs) can be copied across as files. This reference explains the architectural reason the direct import is not supported, lists what can be salvaged, gives a reproducible manual recreation procedure, and closes with the official forward migration path from WinCC flexible 2008 into the TIA Portal.
Why Direct Migration Is Not Supported
Siemens documents the migration paths between its visualization products explicitly. The legacy entry Siemens Support entry 18796902 and the current TIA Portal documentation Migrating WinCC flexible 2008 projects (TIA Portal V20) cover the supported transitions. Neither WinCC V6.2 → WinCC flexible 2008 nor WinCC V7.x → WinCC flexible 2008 is on that list. The supported WinCC flexible 2008 inbound path is only from older WinCC flexible versions (2005, 2007) and from ProTool. The supported outbound path is into TIA Portal (WinCC Comfort/Advanced), not into WinCC flexible 2008.
Three technical reasons explain the gap:
-
Different picture engine. WinCC V6.2 uses the Designer/Graphics Designer with
.pdlpicture files, vector primitives, and the C-/VBS-Action interface. WinCC flexible 2008 uses its own picture editor that stores screens as.fwdproject data with a smaller, panel-specific object set. -
Different tag model. WinCC tags are stored in the SQL Server-backed project database; WinCC flexible tags live in the
.hmiproject file. Address, conversion, and limits differ per target panel. - Different runtime target. WinCC V6.2 runs on a Windows PC (Win32 runtime). WinCC flexible 2008 produces a CE/Win32 image for SIMATIC HMI panels such as the MP377 (15" or 19" Multi Panel).
Architectural Differences
| Attribute | WinCC V6.2 | WinCC flexible 2008 |
|---|---|---|
| Product class | PC SCADA | HMI configuration suite |
| Project file |
*.mcp (main project) plus *.pdl pictures |
*.hmi project, *.fwd project workspace, compiled runtime |
| Tag database | SQL Server (WinCC project DB) | Internal, embedded in .hmi
|
| Runtime OS | Windows XP/Server (PC) | Windows CE / Windows embedded on panel |
| Target devices | Server, Client, Web Navigator | OP 77/73, TP 170/177/270/277, OP 170/270, MP 270/277/370/377, Mobile Panel 170/177, KTP, Comfort Panels (from SP3) |
| Scripting | C-Script, VBScript (Global Script) | VBScript, limited C-like syntax (project-dependent) |
| Tag limit | Up to 150,000 (Power Tags) on licensed server | Limited by target panel (e.g. MP377: 4,096 external tags) |
| Archive / logging | Tag Logging, Alarm Logging, central DB | Logs and alarms on panel, CSV/binary export |
Because the two products target different hardware classes and store project data in incompatible containers, there is no File → Import menu item in WinCC flexible 2008 that opens a WinCC V6.2 .mcp file. The only import paths exposed in WinCC flexible 2008 are:
- Import of legacy ProTool projects (
*.pdb). - Import of older WinCC flexible projects (2004, 2005, 2007) via Project → Migrate.
- Import of graphic objects (BMP, JPG, PNG, ICO, EMF/WMF as static) through the Graphics library.
Reusable Assets from a WinCC V6.2 Project
Although a direct import is not possible, the following assets can be salvaged from the WinCC V6.2 source and reused inside the new WinCC flexible 2008 HMI project with little or no rework.
| Asset type | Source location (WinCC V6.2) | Reuse path (WinCC flexible 2008) |
|---|---|---|
| Raster graphics (BMP, JPG, PNG) | Graphics Designer → GraCS\ directory of the runtime project |
Copy to disk, then Graphics → Add to Graphics Library in WinCC flexible 2008 |
| Icon libraries (ICO) |
GraCS\ or custom path |
Add to Graphics Library |
| Custom symbol libraries | Symbol library folder of project | Recompile as WinCC flexible 2008 libraries (re-author required) |
| Tag address list (CSV) | Tag export to CSV/Excel | Map by hand or by script into WinCC flexible tag table |
| Alarm texts and classes | Alarm Logging → export | Re-enter manually; the WinCC flexible alarm editor is the single source of truth |
| Recipe / user archives structure | User Archive editor (SQL) | Recreate as Recipes in WinCC flexible 2008 (different data layout) |
| Project documentation | WinCC Documentation Viewer export | Keep as PDF reference for cross-checking IO addresses and naming |
Use the WinCC V6.2 Tag Management export to CSV as the canonical list of tag name, address, data type, and conversion. That spreadsheet becomes the single source of truth when the WinCC flexible tag table is rebuilt.
Manual Recreation Procedure
The recommended workflow is a structured rebuild. The following procedure is field-proven on projects with up to ~250 screens and 1,500 tags.
- Inventory the WinCC V6.2 project. Export the tag list (CSV), alarm list (CSV), picture list (Excel), script list, and archive configuration. Note the PLC(s) involved (S7-300/400, S7-200, OPC, Modbus) and the panel target (e.g. MP377 15" Touch).
-
Confirm the target runtime. The MP377 ships with two firmware generations (Windows CE 5.x and CE 6.x). Match the Image in WinCC flexible 2008 to the panel's actual OS, otherwise the download fails with
230006 / 230008-class transfer errors. -
Create the WinCC flexible 2008 project. Launch WinCC flexible 2008 SP5 (last release in the line, recommended for TIA Portal migration) and select the correct device, e.g.
MP 377 15" TouchorMP 377 19" Touch. - Configure the HMI connections. Re-enter the MPI/PROFIBUS or Ethernet connection to the S7 controller. Verify the slot, rack, and partner IP / MPI address match the WinCC V6.2 settings.
- Rebuild the tag table. From the exported CSV, create each tag in WinCC flexible. Mind the per-panel limits: e.g. MP377 supports 4,096 external tags, 2,048 internal tags, 4,096 alarm messages (configuration-dependent).
-
Rebuild the screens. Open the WinCC V6.2
.pdlas a visual reference. Recreate each screen in WinCC flexible using its own object set. Reuse the BMPs copied fromGraCS\. - Re-enter alarms. Use the WinCC flexible alarm editor. The message classes (Error, Warning, System) map 1:1 to the WinCC V6.2 classes when the same PLC message bit assignments are preserved.
- Convert scripts. Translate VBScript directly (syntax is largely compatible). C-Scripts in WinCC must be rewritten as VBScript functions inside WinCC flexible; the function libraries and event model differ.
- Recompile and download. Project → Compiler → All, then Transfer → HMI. Use Ethernet or PROFIBUS depending on the panel's installed interface.
Tag and Variable Mapping
WinCC V6.2 tags use the standard S7 address notation DBx.DBBy, Ix.y, Qx.y, MWx. WinCC flexible 2008 accepts the same syntax in the Address column. The following table summarizes the recommended mapping for a typical S7-300/400 migration.
| WinCC V6.2 tag property | WinCC flexible 2008 equivalent | Notes |
|---|---|---|
Name (e.g. Motor_01_Speed) |
Name (max 128 chars) | Preserve to keep script references intact |
| PLC connection | Connection (assigned to a configured HMI connection) | Re-create the connection once, then assign to many tags |
| Data type (BOOL, INT, REAL, STRING) | Identical data types | STRING length must be set per tag in WinCC flexible |
| Acquisition cycle (WinCC tag) | Acquisition cycle on the tag | Mind the panel-side cycle granularity (1 s minimum on MP377) |
| Limits / scaling | Linear scaling on the tag | Identical formula; check decimal separator (locale) |
| Substitute value use | Substitute value flag on the tag | Behavior is equivalent |
| PowerTag license | Tag limit by panel license | WinCC flexible has no PowerTag concept; the panel firmware enforces the tag count |
A useful technique is to import the CSV into a temporary Excel sheet, then use the WinCC flexible 2008 Tag import/export functionality (the *.csv importer available from Project → Import/Export in the tag editor) to bulk-create tags. The importer expects a header row with the column names Name,PLC,Address,DataType,Length,AcquisitionCycle,SubstituteValue,Scaling; the order is not strict but the names must match.
Graphics and Screen Layout
Screen geometry on the MP377 15" is 1024 × 768 pixels; the 19" is 1280 × 1024. WinCC flexible 2008 stores screen coordinates in pixels. If the original WinCC V6.2 screens were designed for a 1280 × 1024 monitor, the operator layouts cannot be scaled automatically into the MP377 15" canvas; objects need to be repositioned.
| WinCC V6.2 graphic primitive | WinCC flexible 2008 equivalent | Conversion effort |
|---|---|---|
| Static text | Text field / Symbolic IO field | None |
| I/O field | I/O field | Re-enter format, limits, event scripts |
| Button | Button | Re-enter events; VBScript carries over |
| Status/force display | Status display / Animated graphic | Re-enter states, copy BMPs |
| Bar graph | Bar | None (properties identical) |
| Trend view (WinCC Online Trend Control) | Trend view (WinCC flexible) | Rebuild the trend buffer mapping (one buffer per logged tag) |
| Alarm view (WinCC Alarm Control) | Alarm view / Alarm line / Alarm window | Re-enter message classes and filters |
| User-defined vector (PDL vector graphic) | Polyline / Polygon / Rectangle / Circle / Ellipse | One-time manual rebuild |
| OCX / ActiveX wrapper | Not supported on WinCC flexible panels | Replace with native object or Sm@rtClient picture |
Alarms, Logging, and Scripts
Alarm handling differs in scope: WinCC V6.2 exposes a server-class alarm logging engine backed by SQL Server; WinCC flexible 2008 stores alarm messages in panel-local memory and archives them in CSV or RDB (binary) files. The migration strategy is therefore to mirror the WinCC message classes on the HMI for the same PLC bit alarms, not to copy the WinCC alarm database.
-
Bit-message alarms. Map each WinCC message to a WinCC flexible discrete alarm with the same trigger bit. The discrete alarm editor can import a CSV that lists
Number,Text,TriggerBit,Acknowledge,Class. -
Analog alarms. Use the limit-value monitoring in the WinCC flexible tag editor. The limits defined for the WinCC tag (e.g.
High, HighHigh, Low, LowLow) translate one-to-one. - Logging. Replace WinCC Tag Logging archives with WinCC flexible logs. Configure the data log with the same acquisition cycle, and configure an export path (USB, network share, FTP) on the MP377.
- Scripts. VBScript code transfers with minor adjustments. Functions in WinCC Global Script become Project Scripts; standard modules in WinCC become Procedures in the WinCC flexible project. Re-bind event handlers manually.
Commissioning the Recreated Project
After the project compiles cleanly and downloads to the panel, run the following verification sequence. Each step must pass before moving to the next.
-
Connectivity. Open the WinCC flexible Transfer log. Verify
Transfer OKwith no warnings about firmware mismatch. -
Tag visibility. Start the runtime on the panel. Open a screen with an I/O field bound to a known tag (e.g.
DB100.DBD0) and confirm the value updates in step with the WinCC V6.2 server. - Alarms. Force a known alarm bit in the PLC; confirm the WinCC flexible alarm view shows the correct message number and class.
- Trends. Open a trend with at least three logged tags and verify the curves are continuous and at the configured cycle.
- Scripts. Exercise each event-driven button and confirm the expected VBScript action runs. Use the panel's diagnostic view (Start Center → Information → Scripts) to spot syntax errors.
- Recipes. Write a test recipe, transfer it to the panel, change a record, and write it back to the PLC. Confirm the byte layout matches the original WinCC V6.2 user archive (where applicable).
- Operator logon. Test the user administration: logon, logoff, change password, lock screen.
Forward Path: WinCC flexible 2008 to TIA Portal
After the WinCC flexible 2008 project has been built and commissioned, the next step on a current-generation migration roadmap is the move to TIA Portal. Siemens documents this path in Migrating WinCC flexible 2008 projects. The following preconditions apply:
- The source project must have been created or last saved with WinCC flexible 2008 SP3 or later. Earlier service packs must be opened once in SP3+ and re-saved before TIA Portal will accept the file.
- The target TIA Portal version must support the panel type. Comfort Panels (TP1500, TP1900, TP2200) and the MP377 are supported in TIA Portal V13+ with WinCC Comfort/Advanced.
- The TIA Portal migration wizard is launched from Project → Migrate project. The wizard creates a new TIA Portal project, copies the panels, tags, screens, alarms, and scripts, and reports any objects that require manual rework.
Common remediation items after the TIA Portal migration are: unsupported custom ActiveX (replace with TIA Portal native controls), VB scripts that use deprecated functions, and any device-specific image attributes that no longer map to the Comfort Panel OS.
Compatibility and Firmware Matrix
| WinCC flexible 2008 version | Service Pack | MP377 image | Supported by TIA Portal migration |
|---|---|---|---|
| WinCC flexible 2008 | RTM | V1.x (CE 5) | No (re-save in SP3+ required) |
| WinCC flexible 2008 SP1 | SP1 | V1.x | No (re-save in SP3+ required) |
| WinCC flexible 2008 SP2 | SP2 | V1.x / V2.x | No (re-save in SP3+ required) |
| WinCC flexible 2008 SP3 | SP3 | V2.x (CE 6) | Yes (TIA Portal V13 / V14) |
| WinCC flexible 2008 SP4 | SP4 | V2.x | Yes (TIA Portal V14 SP1 / V15) |
| WinCC flexible 2008 SP5 | SP5 | V2.x | Yes (TIA Portal V15.1 / V16 / V17 / V18 / V19 / V20) |
Troubleshooting Matrix
| Symptom | Root cause | Remedy |
|---|---|---|
| WinCC flexible refuses to open a WinCC V6.2 backup | WinCC flexible has no .mcp importer |
Accept that this import is not supported; rebuild the project manually using the exported tag list |
Compiled project fails to transfer with error 230006
|
Firmware/image version mismatch between project and panel | Match the WinCC flexible image to the panel OS (CE 5 or CE 6) under Device → Image |
Tags show ### on the panel |
STRING length mismatch or uninitialized tag | Set explicit length and substitute value for each tag |
| Alarm does not appear in the alarm view | Trigger bit not configured, or alarm class filter active | Verify the discrete alarm trigger address, then check the alarm view filter |
| TIA Portal migration wizard reports Source project too old | Project last saved before WinCC flexible 2008 SP3 | Open the project in WinCC flexible 2008 SP5, recompile, save, then re-run the TIA Portal migration |
| VBScript error on a button press | Global WinCC function not re-bound | Re-create the procedure under Project Scripts and assign it to the event |
| OCX from WinCC not visible on the MP377 | WinCC flexible does not support ActiveX | Replace with a native object or a Sm@rtClient view of the SCADA |
Verification Checklist
- WinCC flexible 2008 project compiles without errors or warnings.
- Transfer to the MP377 reports
Transfer OK. - All external tags read and write against the S7 controller.
- All alarms with trigger bits in the PLC appear in the WinCC flexible alarm view.
- All buttons and I/O fields trigger the expected VBScript handlers.
- All trends and logs write to the panel's storage and export correctly.
- If the project is destined for TIA Portal, it has been re-saved in WinCC flexible 2008 SP3 or later.
Frequently Asked Questions
Can I import a WinCC V6.2 project directly into WinCC flexible 2008?
No. WinCC V6.2 is a PC-based SCADA and WinCC flexible 2008 is a configuration suite for SIMATIC HMI panels such as the MP377. There is no File → Import path between the two products. Re-create the project manually in WinCC flexible 2008, using the WinCC tag export and the screen PNGs as references.
Which assets from a WinCC V6.2 project can I reuse in WinCC flexible 2008?
Raster graphics (BMP, JPG, PNG, ICO) saved in the WinCC GraCS\ folder can be added to the WinCC flexible 2008 graphics library. The tag list exported to CSV can be re-imported into the WinCC flexible tag editor. Screens, scripts, alarms, and archives must be rebuilt.
Which version of WinCC flexible 2008 should I install?
Install WinCC flexible 2008 SP5 (the final service pack). It is the only release of the line that all current TIA Portal versions can migrate, and it carries the largest set of device images including the MP377 with Windows CE 6.
Why does my TIA Portal migration reject the WinCC flexible 2008 project?
Projects last saved with a service pack older than SP3 are rejected. Open the project in WinCC flexible 2008 SP3 or later, recompile, save, and re-run the TIA Portal migration wizard.
Can a WinCC V6.2 ActiveX control be shown on the MP377?
No. WinCC flexible 2008 panels do not support ActiveX. Replace OCX-based content with a native WinCC flexible control, a Sm@rtClient view of the SCADA screen, or an embedded HTML page served from a PLC webserver.