If the amount of F module parameters *.PAR_ID in a safety program exceeds the limit of 65535 and a part of the PAR_IDs is used for F module types, the overall signature of the safety program in the printout footer and in the program information part might differ. It might also happen that the safety mode can no longer be enabled after a delta load of the safety program.
When should you expect this behavior?
You should expect this behavior if all the following conditions apply:
- Safety program created with F systems V5.2 or V6.0
- Safety program contains F module types
- Limit of 65535 PAR_IDs exceeded
- Changes in the program incorporated with delta load
How can you prevent this behavior?
You can prevent this behavior by not exceeding the limit of 65535 PAR_IDs in your project. You can reduce the amount of PAR_IDs by:
- Deleting F modules and F module types that are not required from the safety program
- Reducing the amount of unused inputs and outputs to F module types (such as by creating a F_OR8 instead of a F_OR16)
- Dividing the safety program across several F-CPUs.
You can determine the amount of PAR_IDs by using "S7FPIdInfo.exe".
Use of "S7FPIdInfo.exe" is intuitive. Press the "Search" button to select the appropriate S7 program. Alternatively, you can drag the S7 program from the SIMATIC Manager to the "Search" button. The count procedure begins when you press the "Start" button. The amount of PAR_IDs of the S7 program is given under "Total". Select the relevant S7 program via the "Search" button again if you want to carry out more Par_ID count procedures.
The "S7FPIdInfo.exe" tool is only to be used in connection with F Systems V5.2 SP4 or V6.0.
S7FPIdInfo_e.zip ( 478 KB )