||Requirements for migration|
The software components listed below must be installed on the computer on which you wish to perform the migration.
- STEP 7 Professional (TIA Portal) V11 or higher
- STEP 7 V5.4+SP5 or higher with the associated license
- STEP 7 options packages used in the project to be migrated
The complete STEP 7 V5.x project must be consistent. This means that the STEP 7 program, the hardware configuration and the network configuration must be consistent. Perform the relevant function for consistency checking in each case to check and ensure consistency.
More information about consistency checking is available in Entry ID: 5416540 and in the relevant help menu of STEP 7 V5.x.
Compilation in the block consistency check causes the tags in the instance DBs for the technology blocks (PID function blocks, for example) to be reset to their default values. This applies also to the data blocks in which recipes were configured. We recommend the following as a remedy:
- Save the instance data blocks beforehand and copy them back into the block folder after compilation in the block consistency check or
- Restore the consistency of the blocks without compilation in the block consistency check. Generate a new instance DB and copy all the data from the old (inconsistent) DB into the new (consistent) DB.
Then you can migrate the project in the TIA Portal with your configured values.
All the hardware components in your STEP 7 V5.x project must be in the hardware catalog of the TIA Portal. The modules that could be ordered and were not discontinued by 1.10.2007 are supported by the TIA Portal and are stored in the hardware catalog of STEP 7 (TIA Portal). An overview of the supported modules is given in Entry ID 50029532 for STEP 7 V11.
As from STEP 7 Professional V12 the "Exclude hardware configuration" option in the "Migrate Project" dialog is disabled by default. If you want to migrate the hardware configuration, you must enable this option. If your project contains hardware components that do not fulfill these requirements, migration is aborted. In this case you must
- replace the non-migratable modules from STEP 7 V5.x with modules that are still being actively marketed
- or install the missing GSD files in the TIA Portal.
||Migrating projects from earlier versions of STEP 7|
You can also migrate projects from earlier versions of STEP 7, created with V5.3, for example, to STEP 7 Professional (TIA Portal). The requirements in points 1 to 3 also apply here. This means that you must recompile these projects beforehand in STEP 7 V5.4+SP5 (or higher).
You can migrate projects with protected blocks to the TIA Portal and then download them to the CPU. Here, blocks from STEP 7 V5.5 encrypted with S7 Block Privacy are marked as not supported. Note the following restrictions in this case:
- The block protection from STEP 7 V5.x (KNOW_HOW_PROTECT or encryption with S7 Block Privacy) is not supported in the TIA Portal. A modified block protection is available in STEP 7 Professional.
- You cannot open or edit these blocks.
- The block protection from STEP 7 V5.x can no longer be removed in the TIA Portal.
Before migrating the project, you should remove the block protection from your blocks in STEP 7 V5.x. After migration you can protect your blocks again with the protection mechanism of STEP 7 Professional (TIA Portal) in this menu: "Edit > Know-How Protection".
In order to migrate STEP 7 V5.x projects with an F program, you must have STEP 7 Safety Advanced V11 installed. After migration you receive a complete STEP 7 Safety project in which the program structure of S7 Distributed Safety and the overall signature are retained.
- The check sum and the overall signature of the F program are not changed by the migration. The migrated projected does not have to be approved again and can be downloaded into the F CPU without renewed compilation (1).
- If, however, you edit or recompile the migrated F program with STEP 7 Safety V11, then the program structures are changed to STEP 7 Safety Advanced V11 (2). In this way the F program receives a new overall signature and a new check sum. This means that the F program has to be approved anew.
You cannot migrate a Distributed Safety Project to STEP 7 (TIA Portal) V12, because the Safety Option is not yet available.
||IEC languages and software tools|
Programs created in the IEC languages LAD, FBD, STL, S7-GRAPH or S7-SCL can be migrated to STEP 7 Professional (TIA Portal).
S7-SCL blocks can be migrated with or without the associated "STEP 7 V5.x - SCL source".
- S7-SCL source block available in the STEP 7 V5.x project (recommended)
In order for you to be able to edit your S7-SCL blocks as required in STEP 7 Professional (TIA Portal), the S7-SCL sources must be stored in the source folder of the V5.x project before migration. These S7-SCL sources from STEP 7 V5.x are migrated to STEP 7 (TIA Portal) as S7-SCL blocks. The actual sources are not transferred, because no more work is done with block sources in STEP 7 (TIA Portal). In STEP 7 (TIA Portal), an SCL block is always created here in unprotected form (even if there is "KNOW-HOW-PROTECT" in the V5.x source).
- No S7-SCL source available for SCL block in the STEP 7 V5.x project.
S7-SCL blocks for which the associated source file is missing in STEP 7 V5.x are migrated to STEP 7 (TIA Portal) as protected blocks. Restrictions for editing these blocks apply in the same way as for the protected blocks in Point 5.
The S7-GRAPH and S7-SCL blocks must be consistent and have to be recompiled after migration to STEP 7 (TIA Portal). Then you have to download the project into the CPU. It is only possible to have an Online View of the blocks after compiling and downloading.
Please also observe the information given in Entry ID: 59784005. A number of instructions cannot be transferred and these have to be entered manually after migration.
The components and software tools below are not yet supported in STEP 7 (TIA Portal).
- Process diagnostics S7-PDIAG
S7-PDIAG blocks (FB44, DB44, …) are migrated but are marked as not supported. These blocks can be downloaded, but cannot be edited. The message texts and address monitoring instances are not longer available in the STEP 7 (TIA Portal) project.
- H systems
- Multiprojects (only separate projects can be migrated)
The components and software tools below are no longer supported in the TIA Portal.
These blocks are migrated but are marked as not supported.
- FMS connections
- Libraries created with STEP 7 V5.x. To remedy this we recommend copying the blocks from the library into a project. After migration you can copy the blocks into a TIA Portal library.
||System diagnostics/report system errors (SFM/RSE)|
The SFM blocks (FB49, DB49, FB50 and FC49) are not migrated. After migration, system diagnostics is enabled in the CPU properties. After migration you must compile the hardware configuration in STEP 7 (TIA Portal) in order to create the new SFM blocks including new alarms and test lists. Then you have to download the project into the CPU.
||PLC messages (Alarm_S, Alarm_D, Alarm_8, …)|
The PLC messages are migrated with all the parameters and including all message classes which are newly created. The message types and message instances are also migrated and stored under the PLC messages in the TIA Portal. The requirement is that in STEP 7 V5.x the assignment of message numbers for the separate stations is preset to "CPU-oriented unique". You can enable this setting in the STEP 7 V5.x project. Proceed as follows:
- In the SIMATIC Manager of your STEP 7 V5.x project you mark your station ("SIMATIC 300", for example).
- In the menu bar you select the "Options > Customize..." dialog.
- Select the "Message numbers" tab and enable the setting "Always assign CPU-oriented unique message numbers".
- Then save your project with the "File > Save as..." function and the "With reorganization (slow)" option.
Messages are migrated only with this setting as shown in Fig. 03.
||Block calls in S7-SCL sources|
In the S7-SCL sources, with STEP 7 V5.x you could set the block parameters before or after the block is actually called. This means that the block could be called with incomplete parameters and tags or values could be assigned to the In/Out parameters of the blocks at another point in the S7-SCL source. This type of programming is not possible in STEP 7 (TIA Portal) and will not be supported in the future. You can migrate and compile the STEP 7 V5.x project in the TIA Portal without any errors, but the function of this block call is no longer possible in the S7-SCL program. Note the points below before you compile your S7-SCL source in STEP 7 V5.x and migrate the project to TIA Portal.
- All parameters of the called block must be assigned in the call statement.
- None of the parameters of the called block is allowed to be deleted and inserted and parameterized at another point in the S7-SCL source.
||TIA Portal Readiness Check Tool|
The TIA Portal Readiness Check Tool delivers an easy way of checking whether the TIA Portal supports the hardware in the project. The tool can be used for:
- STEP 7 V5.4
- STEP 7 V5.5
- WinCC V7
- WinCC flexible 2008
More information is available in Entry ID: 60162195.
||Configurations of options packages not supported|
If your project includes configurations from options that are not compatible with your current version of STEP 7 or which are not installed on your computer, you cannot migrate the project to STEP 7 (TIA Portal). If you open the project in STEP 7 V5.x, you get the message indicating that options packages are missing.
In case these configurations are still obligatory, you must install the missing options packages. Note here the hardware requirements for installing with the current version of STEP 7. For example, you need version V4.2.1 (or higher) for SIMOTION SCOUT with STEP 7 V5.5+SP2 in Windows 7 (32-bit). More information about compatibility is available in Entry ID: 18734363. After installing the missing options packages you must recompile your project.
If you no longer need the configurations of the missing options packages, you must reorganize the project in STEP 7 V5.x. For this, in the SIMATIC Manager you open the dialog "File > Save as..." and activate the option "With reorganization (slow)". Change the project name or the path and acknowledge with OK. After saving and reorganizing you can migrate the newly created project to STEP 7 (TIA Portal).
With this option the project is checked and reorganized in addition during the saving procedure. Under certain circumstances this method reduces the project's memory requirement. All the elements of the missing options packages are removed from the project. More information is available in the Online Help of STEP 7 V5.5 under "Save project as".
||PLC migration to S7-1500 with STEP 7 (TIA Portal) V12 or higher|
Recommendations for programming and information about migration to S7-1500 with STEP 7 (TIA Portal) V12 are available here:
- Entry ID: 67858106 (Migration to S7-1500)
- Entry ID: 67582299 (Recommendations for programming for migration to S7-1500)