How do you update invalid block calls (time stamp conflicts) in calling blocks?
If you make changes to a block which is called in another block, or if you change a UDT definition which is used in a DB, FC, FB or in another UDT, this gives rise to a time stamp conflict. The time stamps (code and interface time stamp of the blocks) are used to monitor consistency in the STEP 7 program. There is more information available about the time stamps in the Online Help in STEP 7 under
- Time Stamps as a Block Property and Time Stamp Conflicts
- Time Stamps in Instance Data Blocks
- Time Stamps in UDTs and Data Blocks Derived from UDTs
- Time Stamps in Logic Blocks
- Updating Block Calls or UDT Applications
If you have made changes to a block (FB, FC, DB) in the interfaces, the following error message appears when the calling block is opened:
- "There is a time stamp conflict with at least one block call.".
After clicking OK to acknowledge, the called block which has been changed appears in red in the LAD/STL/FBD editor. The table below describes a series of possibilities or remedies for remedying time stamp conflicts in blocks:
|1||Menu command: "Check and Update Accesses"|
This instruction is used to check all operands for type compatibility; if any errors are discovered, they are highlighted in red. Furthermore, the data blocks are updated or restructured, and the call interfaces are updated insofar as possible.
Open the LAD/STL/FBD editor for the calling block and update the block call via "File > Check and Update Accesses".
If, for example, you have removed variables from the interface for the called block, then STEP 7 cannot find a unique assignment between the variables, and the call remains red. In this case, proceed to No. 2 or perform the "Updating Block Calls" function.
|2||Menu command: "Edit > Go To > Next Error"|
After opening the LAD/STL/FBD editor, click "Edit > Go To > Next Error" to automatically jump to the block call which is highlighted in red.
|3||Updating Block Calls|
Click the block highlighted in red in the LAD/STL/FBD editor or apply the function described in No. 2. The "Edit > Call > Update" menu command can be used to update any block which has become invalid. The following interface changes in the called block are then automatically updated:
If you click the "Update..." button, this will take you to the "Interface Update" dialog box. In this dialog box, the left pane shows the block prior to the interface change, and the right pane shows the block as it currently is. You can now update the existing parameters in the old box. This involves selecting a parameter from the old block and copying or moving it to the new block.
Once you have performed an interface update and clicked "OK" to exit the dialog, the invalid block is replaced by the updated block.
|4||Deletion and new entry of the block call|
The block call can also be updated by deleting the block call and re-entering it.
Then call the block, including the instance DB, again and confirm the subsequent message with "Yes".
The instance DB or block call are now updated and can be saved in the LAD/STL/FBD editor.
Further processing of a DB if the UDT used in the block has been changed
The message also indicates that the UDT's time stamp is more recent than the data block's. When you acknowledge the message described above, the variables of the UDT are marked in red. In addition you see the structure of each UDT before the UDT was changed. Update the block call with the menu command "File > Check and Update Accesses".
Perform the block-consistency check and compile the entire STEP 7 program in the block-consistency check via the function "Program > Compile all". The block consistency check function automatically clears the majority of all time stamp conflicts and block inconsistencies. You can also find more information is our entry entitled
User-defined data type