Commissioning
12.4 Operating and system states
S7-1500R/H redundant system
388 System Manual, 01/2024, A5E41814787-AF
If the cyclic program exceeds the maximum cycle time, the operating system may start the
time error OB (OB 80). You can find additional information in the section Start events
(Page 323).
Points to note in the RUN operating state
In non-redundant operation, the CPUs are independent of each other. They can have
different projects.
RUN-Syncup operating state
In the RUN-Syncup operating state, the backup CPU synchronizes with the primary CPU. The
SYNCUP that temporarily affects the primary CPU (for example delay of asynchronous
services, cycle time extension through transfer of the load and work memory contents) runs
simultaneously in the backup CPU. You can find more information in the section SYNCUP
system state (Page 388).
RUN-Redundant operating state
The redundant system is in the RUN-Redundant system state. Both CPUs process the user
program synchronously.
12.4.6 SYNCUP system state
Requirements
• The article numbers and firmware versions of the two CPUs are the same.
• There is a SIMATIC Memory Card in each CPU.
• The PROFINET ring is closed and configured.
• There is at least one redundancy connection (fiber-optic cable) in the S7-1500H redundant
system.
• Media redundancy role in the configured PROFINET ring:
– The two CPUs have the media redundancy role "Manager (auto)".
– All other devices in the PROFINET ring have the media redundancy role "Client".
• Pairing for the two CPUs has been implemented.
• The primary CPU is in the RUN operating state.
• The execution of SYNCUP is not disabled (default setting).
• No load functions are running.
• Testing with breakpoints is not used.
No SYNCUP is performed during testing with breakpoints. You can find more information
on testing with breakpoints in the STEP 7 online help.
To Next Page
Loading...
Need help?
General
