Siemens S7-1200 - TC_CONFIG for changing configuration data of the CP

PLC concepts
4.1 Execution of the user program
S7-1200 Programmable controller
96 System Manual, 03/2014, A5E02486680-AG
Understanding event execution priorities and queuing
The number of pending (queued) events from a single source is limited, using a different
queue for each event type. Upon reaching the limit of pending events for a given event type,
the next event is lost. Refer to the topic about time error interrupt OBs (Page 88) for more
information regarding queue overflows.
Each CPU event has an associated priority. In general, the CPU services events in order of
priority (highest priority first). The CPU services events of the same priority on a "first-come,
first-served" basis.
Table 4- 13 OB events
Event
Quantity allowed
Default OB priority
Program cycle 1 program cycle event
Multiple OBs allowed
1
4
Startup 1 startup event
1
Multiple OBs allowed
1
4
Time delay Up to 4 time events
1 OB per event
3
Cyclic interrupt Up to 4 events
1 OB per event
8
Hardware interrupt Up to 50 hardware interrupt events
2
1 OB per event, but you can use the same OB for multiple
events
18
18
Time error
1 event (only if configured)
3
22 or 26
4
Diagnostic error
1 event (only if configured)
5
Pull or plug of modules
1 event
6
Rack or station failure
1 event
6
Time of day
Up to 2 events
2
Status 1 event 4
Update
1 event
4
Profile 1 event 4
1
The startup event and the program cycle event never occur at the same time because the startup event runs to
completion before the program cycle event starts.
2
You can have more than 50 hardware interrupt event OBs if you use the DETACH and ATTACH instructions.
3
You can configure the CPU to stay in RUN if the scan cycle exceeds the maximum scan cycle time or you can use the
RE_TRIGR instruction to reset the cycle time. However, the CPU goes to STOP mode the second time that one scan
cycle exceeds the maximum scan cycle time.
4
The priority for a new V4.0 CPU is 22. If you exchange a V3.0 CPU for a V4.0 CPU, the priority is 26, the priority that
was in effect for V3.0. In either case, the priority field is editable and you can set the priority to any value in the range 22
to 26.
Refer to the topic "Exchanging a V3.0 CPU for a V4.0 CPU (Page 995)" for more details.