Resolving ProTool OP7 V1.x Project File Opening Errors

Problem Overview

Engineers maintaining legacy operator panels such as the Siemens OP7 frequently encounter the situation in which a working ProTool project can no longer be opened in the currently installed configuration software. The two messages most often reported when opening a V1.x OP7 project in a newer ProTool release (V5.x or V6.x) are:

The project was created with protool version 1.X. In protool version 2.0 and later projects are stored in single file. The directory having the project name is no longer required.

The required device type is not supported by the protool version installed check.

Both errors originate from the same root cause: a file format and device driver gap between ProTool V1.x (mid-1990s) and the V2.0+ single-file generation. The OP7 hardware itself remains supported through ProTool V6.0 SP3 and WinCC flexible 2008 SP2, but a working conversion path must be followed. This reference details every step required to recover, convert, and verify such a project without losing tags, screens, alarms, or communication bindings.

Symptoms and Error Messages

Errors 1 and 2 are the canonical pair; the third error appears when V6.x is installed but the legacy converter was not selected during setup; the fourth error is encountered only after a successful format conversion, when symbol references must be re-linked.

Root Cause: Version Format Incompatibility

ProTool/Pro V1.x stored an entire project as a directory of multiple files. The directory name matched the project name and typically contained a project header file, screen definitions, tag lists, alarm logs, recipes, and a STEP 5/STL symbol file. ProTool V2.0 (released 1997) consolidated every project into a single .pdb database file, eliminating the directory structure and introducing binary indexes for faster compilation.

Because the V1.x converter is implemented as a loadable component, ProTool V5.x and V6.x installations only expose it when the installer is run with the "Legacy V1.x support" option enabled (or when the corresponding update package is installed). If this option is absent, the second error message is produced even though the panel itself is otherwise supported.

The OP7 device family is technically supported in ProTool up to and including V6.0 SP3 (catalog no. 6AV6580-0AD06-0AX0) and in WinCC flexible up to 2008 SP2. After 2008 SP2, OP7 was discontinued and dropped from subsequent TIA Portal releases. Therefore the only viable long-term toolchain for a V1.x OP7 project is:

1. ProTool V6.0 SP3 with the V1.x converter patch, or
2. WinCC flexible 2008 SP2 with the ProTool import option.

OP7 Hardware Reference

The OP7 is a 4-line x 20-character monochrome LCD operator panel. Three communication variants were produced:

Each variant requires a different device driver in ProTool. If the second error message is triggered immediately upon opening a V2.0+ project, the most likely cause is that the installed ProTool build does not contain the OP7 DP device plug-in (a separate sub-package shipped with V6.0 SP3).

File Format Differences: V1.x Directory vs V2.0+ Single File

The conversion process is therefore not a copy operation; the V1.x converter in V6.x rebuilds the symbol references, regenerates internal indexes, and re-binds the tag database to the new binary structure. Tag names longer than 24 characters are silently truncated to comply with the V2.0+ limit.

Solution Path: Update ProTool and Convert Project

Prerequisites

• Windows XP SP3 / Windows 7 SP1 32-bit host (recommended) or a Windows 10/11 32-bit compatibility environment with administrator rights.
• At least 800 MB free disk space for the ProTool V6.0 SP3 install plus the legacy converter.
• A complete, write-protected backup of the original V1.x project directory (copy to external media before any conversion).
• Original ProTool V1.x media (CD or floppy set) or the downloaded update package referenced by Siemens Support entry ID 11772575, which bundles the legacy V1.x converter for V5.x and V6.x.
• Optional: a STEP 7 (Classic) installation of the same vintage as the controller program, to re-link symbols after conversion.

Step-by-Step Conversion Procedure

1. Verify the source format. Browse the project directory. If files such as VAR.DBF, VAR.CDX, ALARM.DBF, and a screen sub-directory are present, the project is in V1.x format and requires the conversion path described here.
2. Install or update ProTool. Run the V6.0 SP3 setup (6AV6580-0AD06-0AX0). On the Custom Installation dialog, enable the optional component Converter ProTool V1.x -> V6.x. Without this component the converter is not present and error #3 will appear.
3. Apply the legacy update. Mount the patch referenced by Siemens Support entry ID 11772575. This update extends the device catalog so that legacy OP7 DP variants remain selectable in V6.x. Restart ProTool after the patch is installed.
4. Open the V1.x project. In ProTool V6.x choose File > Open and navigate to the V1.x project directory (not to a .pdb file). The V1.x converter starts automatically and emits the first informational message; click Continue.
5. Map the device type. When prompted, choose the OP7 device variant that matches the panel's MLFB (see the OP7 hardware reference table). If the variant is missing from the list, the legacy update has not been applied correctly — cancel and reinstall.
6. Resolve symbol references. The converter prompts for the STEP 5 symbol file (Z0.SEQ or Z0.S5D) used by the controller. Point to the original copy. If the controller program is unavailable, select Skip and re-link the tags manually later.
7. Save the converted project as .pdb. Choose File > Save As and save to a new directory. ProTool creates a single-file database named after the project. Never overwrite the original V1.x directory; keep it as a frozen backup.
8. Run the consistency check. Open Project > Consistency Check > All. Address any reported errors (typically truncated tag names, dropped alarm classes, or invalid limit values) before downloading.
9. Recompile and transfer. Use Target > Compile followed by Target > Transfer > OP7. For OP7 DP variants, select the PROFIBUS node address that matches the hardware DIP switches (default 1, range 1-126).

Alternative Migration: WinCC flexible 2008 SP2

If ProTool V6.0 SP3 cannot be installed (for example, on a 64-bit Windows host that does not tolerate the legacy installer), use WinCC flexible 2008 SP2 (catalog no. 6AV6 612-0AA51-3CA8), which is the last WinCC flexible build that still supports the OP7 device family. The migration path is:

1. Install WinCC flexible 2008 SP2 with the ProTool Import option enabled.
2. Launch WinCC flexible and choose File > Migration > ProTool Project.
3. Select the V1.x project directory. WinCC flexible invokes the bundled V1.x converter and produces a WinCC flexible project.
4. Re-verify tag names, alarm classes, and screen navigation. WinCC flexible does not always preserve all V1.x field attributes (for example, custom field attributes from OP7 firmware prior to V2.0.1).
5. Compile and transfer to the OP7 using the same MPI/PROFIBUS address as before.

Once the project is migrated to WinCC flexible 2008 SP2, it can still be edited, but no further migration to TIA Portal is possible because OP7 support was removed from TIA Portal V13. Sites that need long-term support must therefore keep a virtual machine running ProTool V6.0 SP3 or WinCC flexible 2008 SP2 with the original installation media archived.

Communication and Tag Configuration to Preserve

The OP7 supports a fixed set of communication drivers. During conversion, verify that the following parameters are carried over:

If any of the above parameters are reported as "unknown" after conversion, the device mapping (Step 5 of the procedure) was not performed with the correct MLFB. Re-open the project, change the device to the correct variant, and re-save.

Verification Procedure

1. Compile without errors. Project > Compile > All must complete with zero error entries. Warnings about truncated tag names are acceptable only if the truncated names still match the controller program.
2. Offline simulation. Run Target > Start Runtime Simulation on the development PC. The OP7 simulator must show every screen, every alarm class, and the trend/parameter fields that were present in the V1.x source.
3. Tag cross-check. Export the tag list (Project > Export > Tags as CSV) and compare it line-by-line against the original VAR.DBF from the V1.x directory. Discrepancies greater than 1% usually indicate that the converter patch was not applied.
4. On-line test. Connect the OP7 to the controller via MPI/PROFIBUS. Cycle power to the panel, observe the startup screen, and confirm that values update in real time. Open every alarm class and acknowledge at least one event to confirm the alarm buffer is intact.
5. Backup the new project. ZIP the new .pdb file, name it ProjectName_YYYYMMDD.zip, and store it in two independent locations (for example, the engineering server and an offline NAS).

Troubleshooting Matrix

Field-Proven Caveats and Edge Cases

• 16-bit installer restriction. ProTool V6.0 SP3 contains a 16-bit setup stub that does not run on any pure 64-bit Windows build. Use a Windows 7 32-bit VM or XP Mode. Once installed, the application itself runs correctly on Windows 10/11 32-bit compatibility layers.
• OP7 firmware < 2.0.1. Panels shipped before 1998 cannot load compiled V2.0+ projects without a firmware upgrade. The firmware update is delivered as an EPROM image; modern OP7 panels already contain the latest firmware.
• Multi-language projects. The V1.x converter loses font mappings for Cyrillic, Greek, and Baltic character sets. Re-select the correct font in V6.x and re-enter any user-defined texts.
• Recipes. V1.x recipe handling stored data in RECIPE.DBF. The converter imports up to 99 recipes with a maximum of 99 entries each (OP7 hardware limit). Larger recipes are split silently.
• Passwords. V1.x project passwords are case-insensitive; V2.0+ passwords are case-sensitive. The converter carries the password over but enforces case on first save.
• Trend curves. Trend definitions in V1.x referenced bit-packed DB areas. After conversion, the bit fields are re-mapped to byte-aligned addresses. Always re-validate trend accuracy against the live process.
• Symbolic I/O vs absolute I/O. Projects that referenced symbolic tags from STEP 5 STL files lose the symbolic binding during conversion. Re-export symbols from STEP 7 and re-link.
• PROFIBUS GSD. For OP7 DP variants, ensure the GSD file SIEM8117.GSD is installed in the STEP 7 hardware catalog before configuring the DP master.

FAQ