Stop CPU 414-4H

Project with CPU 414-4H (6ES7 414-4HJ00-0AB0 Firmware V3.1.1) The reserve CPU (Rack 1) has stopped. H system in Solo mode.

Diagnostic buffer of module CPU 414-4 H
Order No./ Description Component Version
6ES7 414-4HJ00-0AB0 Hardware 1
- - - Firmware V 3.1.1

Rack: 1
Slot: 3

Event 1 of 120: Event ID 16# 5371
Distributed I/Os: end of the synchronization with a DP master
Slot of the DP master: 3 in rack 1
Number of distributed stations: 6
Event occurred in the standby CPU in rack 1
Incoming event
01:56:09:478 am 09/10/06

Event 2 of 120: Event ID 16# 530D
New startup information in STOP mode
Startup prevented by:
- STOP request exists
- Cold restart or warm restart necessary
Startup information:
- Time for time stamp at the last backed up power on
- Single processor operation
Current/last startup type:
- Warm restart triggered via MPI
Permissibility of certain startup types:
- Manual warm restart permitted
Last valid operation or setting of automatic startup type at power on:
- No startup type/following memory reset
Operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
Incoming event
01:56:09:173 am 09/10/06

Event 3 of 120: Event ID 16# 43DA
STOP due to synchronization error between H CPUs
Previous operating mode: RUN (redundant mode)
Requested operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
Incoming event
01:56:09:169 am 09/10/06



After warm restart h system again works in redundant mode
In what there can be a reason of a stop of the controller and how to avoid occurrence of the given situation?

Hi,

I think, that the important event in your case, is the event 3, but maybe there’s some other informations in others events (4, 5, etc).

This looks like that the Standby CPU can't actualize its data bank with the data of the Active CPU

So,if this occurred, the standby CPU can't assumes an Active CPU with data consistence if the Active CPU goes to stop. So the system goes to solo mode.
I’m induced to believe that the problem stays on the IF or optical fibers, however, normally this type of fault are clear diagnostic in the diagnostic buffer. It may be a fault in CPU too.

I suggest you first looks the diagnostic buffer (events 4, 5, etc.) to find another informations.