Technical data

SINAUT TD7 software package for the CPU
2.3 Structure of the SINAUT user program
Software
System Manual, 07/2009, C79000-G8976-C222-07
213
The program structure in a cyclic interrupt OB
The structure of the SINAUT program in the cyclic interrupt OB is as follows:
Cyclic interrupt OB
PulseCounter
• One or more PulseCounter FCs can be inserted for acquisition of
counted pulses. FC PulseCounter works with up to 8 pulse inputs
from any type of digital input. The acquired counted pulses are
accumulated in configurable SIMATIC counters that are available to
the function blocks that put together the counted value messages (FB
Cnt..._S, FB ZTZ..). For more detailed information, refer to the
description of the SINAUT program structure in OB1.
• User-specific cyclic interrupt functions that are required independent
of the SINAUT program, can be inserted at any location in the cyclic
interrupt OB.
2.3.4 SINAUT test routine in the programming error OB121
Introduction
When a non-existent block is called in a CPU, the CPU usually changes to STOP and the
missing block (FBxx, FCyy or DBzz) is indicated in the diagnostics buffer. You can then load
the missing block and restart the CPU. If you want to avoid the CPU stopping when there is
a missing block, or only changing to STOP when certain block types or block numbers are
missing, you can specify the type of response you require in OB121 with a user program.
The CPU will continue to operate despite a missing block simply by loading OB121 even it
contains nothing. If you want to specify when the CPU should continue and when it should
stop, you will need to include an appropriate user program in OB121.
In conjunction with SINAUT ST7, it is possible that a CPU will stop if it receives a message
that it does not know (or does not yet know) from another CPU. For example, when you add
a datapoint typical to a station and assign it a complete destination address (destination
subscriber number plus destination object number). The set destination object number may
result in a stop on the destination subscriber because the message is transmitted to the
destination as soon as the new datapoint typical is installed in the station. If, however, the
corresponding receive typical has not yet been installed in the destination CPU, the
destination object number (instance DB of the receive typical to be installed) is also not yet
available. The result is that the CPU stops as soon as this message is received, unless you
have configured OB121 to avoid this. For SINAUT ST7 CPUs it is recommended that you
call the FC ST7ObjectTest function in OB121. Then the CPU does not stop when a SINAUT
object DB is not available as in the example described.
FC ST7ObjectTest has a StopInOtherCases parameter. It allows you to specify what should
occur in other situations: Stop or continue operation when OB121 is called because another
data block, an FB or an FC is missing.