Block library TeleControl ST7
5.5 Structure of user program for TD7onCPU
TIM 1531 IRC
136
Operating Instructions, 02/2018, C79000-G8976-C468-02
Example of a TD7 program for a station
Cyclic OB1
BasicTask
The respective FC BasicTask must always be called at the start of the cyclic
program.
Generally, data is ready for further processing after it has been received.
The FC has only one parameter, "UserFC". Normally 0 can be specified. If you
require user-specific processing for received data, specify here the number of an
FC containing the program for this processing.
You can also copy received data chronologically to an archive memory via this
interface.
TimeTask
As an option, you can call the FC TimeTask immediately after FC BasicTask.
The FC has no parameters. FC TimeTask TimeTask must be included if you
need the time of day. This allows data frames to be time-stamped.
However, you can also use the time of day to start program components at a
specific point in time or to schedule the transmission of data frames. FC Trigger,
described below, is then required.
For this FC Time Task to be used, the CPU must be provided with the time from
a local TIM module. You specify this in the configuration.
Trigger
FC Trigger can be included as an option. The FC sets its output for the duration
of one OB1 cycle when the point in time or the time interval set for the FC has
been reached.
The FC can be inserted several times if several times or various time intervals
are required. Using the FC requires that FC TimeTask must be called first in the
OB1 program (see above) and the CPU time must have already been set once.
PartnerStatus
FC PartnerStatus can be included as an option. The FC shows the reachability
for a maximum of 8 communications partners.
ListGenerator
•
ListGenerator300 for S7-300 CPU
•
ListGenerator400 for S7-400 CPU
•
ListGenerator1500 for S7-1500 CPU
The FC can be installed as an option. The FC is required if the station receives
frames containing no destination address or an incomplete destination address.
This happens if the configuration of the destination address has been completely
or partially omitted in a partner for data point typicals. ("PartnerNo" and "Part-
nerObjectNo" were not specified, so transmission to all known destination sub-
scribers takes place.)
PulseCounter
PathStatus
PartnerMonitor
When necessary
