5 Software Conversion
Safety project where the program structure of Distributed Safety and the overall
signature has been preserved.
Note
The acceptance printout created with S7 Distributed Safety V5.4 SP5 remains
valid!
With compilation
Only when the migrated project is recompiled with STEP 7 Safety Advanced V13
will it receive the new program structures and a new overall signature.
Note
The safety program is only compiled when the password for the F program is
entered! Without entering a password, only the standard user program is
compiled!
Checking or reworking required
When you want to migrate a project that includes a safety program that has been
created with Distributed Safety, the following points should be checked or
observed.
During the 1st step of the migration of the STEP 7 V5.x project to the TIA Portal
there will be no messages yet. Only when the CPU is migrated to S7-1500 the
process is aborted with the respective error message(s) if there are certain
instructions.
Table 5-8
At present no runtime group
communication is supported by STEP 7
Safety
For the migration onto S7-1500 the
name of the I/O DB is changed
Replacement of F_GLOBDB.VKE0/1 by
FALSE/TRUE for S7-1500
Replacement of QBAD_I_xx or
QBAD_O_xx by the value status
Migration S7-300/S7-400 nach S7-1500
Entry ID: 109478811,
V1.1,
Problem
05/2017
Remedy/note
Restructure the F runtime groups already in the
STEP 7 V5.x project
STEP 7 Safety changes the name as well as the
number of the I/O DB. Adapt the places of use
manually in the program
Adapt the places of use manually in the
program
This change is valid for the I/Os ET 200SP/ET
200MP and others that support the "RIOforFA-
Safety" profile.
Adapt the places of use manually in the
program
51