Commissioning
12.4 Operating and system states
S7-1500R/H redundant system
System Manual, 01/2024, A5E41814787-AF
387
12.4.4 SYNCUP operating state
SYNCUP operating state (only in the backup CPU)
In the SYNCUP operating state, the operating system synchronizes the backup CPU with the
primary CPU. The primary CPU is in the RUN-Syncup operating state and controls the process.
Unlike the primary CPU, the backup CPU and if applicable, central modules, do not go
through the STARTUP operating state. The communications processors at the backup CPU are
therefore not operational during SYNCUP.
You can find more information in the SYNCUP system state (Page 388) section.
Points to note
You have only limited access to online functions during SYNCUP. You can find more
information in the Test functions (Page 471) section.
12.4.5 RUN operating states
RUN operating states
The primary CPU goes through multiple operating states before reaching the RUN-Redundant
system state:
• RUN
• RUN-Syncup
• RUN-Redundant
The backup CPU only has the RUN-Redundant operating state.
Response
In the RUN operating state, the primary CPU behaves just like an S7-1500 standard CPU. It
performs cyclic, time-driven and interrupt-driven program execution on its own.
Addresses that are in the "Automatic update" process image are automatically updated in
each program cycle. You can find more information in the section Process images and
process image partitions (Page 314).
Once the CPU has written the outputs and read the inputs, it runs through the cyclic program
from the first instruction to the last instruction. Events with a higher priority such as
hardware interrupts, diagnostic interrupts and communication can interrupt the cyclic
program flow and prolong the cycle time.
If you have configured a minimum cycle time, the CPU does not terminate the cycle until
after this minimum cycle time has expired, even if the user program is completed sooner.
The operating system monitors the runtime of the cyclic program on the basis of a
configurable upper limit known as the maximum cycle time. You can restart this time
monitoring at any point in your program by calling the RE_TRIGR instruction.
To Next Page
Loading...
Need help?
General
