Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

400H System, Secondary CPUB suddenly stopped & Auto Start Again

Created by: Prakash_Chennai at: 6/12/2018 3:51 AM (6 Replies)

Rating (2)

Thanks 0

7 Entries

6/12/2018 3:51 AM	Rate (0)
Prakash_Chennai Posts: 12 Rating: (0)	Hi, can anyone interpret why my B-CPU suddenly stopped at 02:59:42.298 PM 06/11/2018 ...? and Auto Start again 03:01:15.936 PM 06/11/2018 ...? Can anyone help me on these one. Below Mention the Firmware Version: CPUA : FirmWare (V 6.0.6), Firmware expansion (V 6.0.1) CPUB : FirmWare (V 6.0.6), Firmware expansion (V 6.0.1) Diagnostic buffer of module CPU 417-5 H PN/DP: Order No./ Description Component Version 6ES7 417-5HT06-0AB0 Hardware 1 - - - Firmware V 6.0.6 Boot Loader Firmware expansion V 6.0.1 Rack: 0 Slot: 5 Serial number: SVPJ2327973 Event 1 of 120: Event ID 16# 7303 H system (1 out of 2) has gone into redundant mode Occurred in: Master CPU in rack 0 Startup information: - Startup without modified system configuration Update time in ms: 655 Requested OB: CPU redundancy error OB (OB72) Priority class: 28 Incoming event 03:01:16.732 PM 06/11/2018 (Coding: 16# 7303 1C48 CD5B F808 0000 028F) Event 2 of 120: Event ID 16# 43E2 Change from update mode to operating mode RUN (redundant mode) Previous operating mode: UPDATE Requested operating mode: RUN (redundant mode) Event occurred in the master CPU in rack 0 Incoming event 03:01:16.710 PM 06/11/2018 (Coding: 16# 43E2 F8C9 0000 0000 0000 0000) Event 3 of 120: Event ID 16# 43E9 Standby CPU: Change from startup mode to update mode Previous operating mode: STARTUP (warm restart) Requested operating mode: UPDATE Event occurred in the standby CPU in rack 1 Incoming event 03:01:15.936 PM 06/11/2018 (Coding: 16# 43E9 F16C 0000 0000 0000 0000) Event 4 of 120: Event ID 16# 43E1 Change from link-up mode to update mode Previous operating mode: LINK-UP Requested operating mode: UPDATE Event occurred in the master CPU in rack 0 Incoming event 03:01:15.936 PM 06/11/2018 (Coding: 16# 43E1 F8BC 0000 0000 0000 0000) Event 5 of 120: Event ID 16# 43E8 Standby CPU: Change from link-up mode to startup mode STOP due to: Memory reset started automatically (power on not backed up ) Startup information: - Time for time stamp at the last backed up power on - Single processor operation Current/last startup type: - Automatic warm restart after non backed up power on (with system memory reset) Permissibility of certain startup types: - Manual warm restart permitted Last valid operation or setting of the automatic startup type at power on: - Automatic warm restart after non backed up power on (with system memory reset) Previous operating mode: LINK-UP Requested operating mode: STARTUP (warm restart) Event occurred in the standby CPU in rack 1 Incoming event 03:01:15.286 PM 06/11/2018 (Coding: 16# 43E8 F1B6 0000 4309 0820 0720) Event 6 of 120: Event ID 16# 5371 Distributed I/Os: End of the synchronization with a DP master/IO controller on slot 5 in rack 1 Number of distributed stations: 8 Event occurred in the standby CPU in rack 1 Incoming event 03:01:14.880 PM 06/11/2018 (Coding: 16# 5371 F125 0050 0008 0000 0000) Event 7 of 120: Event ID 16# 43E0 Change from STOP (internal) to link-up mode STOP due to: Memory reset started automatically (power on not backed up ) Startup information: - Time for time stamp at the last backed up power on - Single processor operation Current/last startup type: - Automatic warm restart after non backed up power on (with system memory reset) Permissibility of certain startup types: - Manual warm restart permitted Last valid operation or setting of the automatic startup type at power on: - Automatic warm restart after non backed up power on (with system memory reset) Previous operating mode: STOP (internal) Requested operating mode: LINK-UP Event occurred in the standby CPU in rack 1 Incoming event 03:01:08.720 PM 06/11/2018 (Coding: 16# 43E0 F14B C772 4309 0820 0720) Event 8 of 120: Event ID 16# 43E0 Change from RUN to link-up mode Previous operating mode: RUN Requested operating mode: LINK-UP Event occurred in the master CPU in rack 0 Incoming event 03:01:08.720 PM 06/11/2018 (Coding: 16# 43E0 F88B 0000 0000 0000 0000) Event 9 of 120: Event ID 16# 45E4 Standby CPU: Change from redundant mode to error-search mode Event: Loss of redundancy (2oo2) due to CPU failure Previous operating mode: RUN (redundant mode) Requested operating mode: Error-search mode Event occurred in the standby CPU in rack 1 Internal error, Incoming event 02:59:42.298 PM 06/11/2018 (Coding: 16# 45E4 F19E C300 0000 7301 FFFF) Event 10 of 120: Event ID 16# 43E3 Master CPU: Change from redundant mode to solo mode Previous operating mode: RUN (redundant mode) Requested operating mode: RUN Event occurred in the master CPU in rack 0 Incoming event 02:59:42.298 PM 06/11/2018 (Coding: 16# 43E3 F898 0000 0000 0000 0000) Event 11 of 120: Event ID 16# 7301 Loss of redundancy (2oo2) due to CPU failure CPU affected: Standby CPU in rack 1 Requested OB: CPU redundancy error OB (OB72) Priority class: 28 Incoming event 02:59:42.298 PM 06/11/2018 (Coding: 16# 7301 1C48 005B F100 0000 0000) Please anyone help me on these why this problem happened suddenly and goes to Run mode again, Incase same thing happens in Future how to Avoid these one. Best Regards Prakash
Prakash_Chennai Posts: 12 Rating: (0)
Suggestion To thank Quote Answer

6/12/2018 7:33 AM	Rate (1)
mopS04 Platinum Expert Joined: 3/5/2014 Last visit: 8/5/2022 Posts: 5521 Rating: (1054)	hi, can you attach the complete diagnostic buffer? I guess some of the entries before can tell us whats up there. regards,
	FCK WAR! Be nice!
Suggestion To thank Quote Answer

6/12/2018 10:01 AM	Rate (0)
Prakash_Chennai Posts: 12 Rating: (0)	Hi, I have attached the diagnostics buffer. Note: Event 1 to Event 11 - 06/11/2018 (During this time only B-CPU becomes Auto Stop & Auto Start) Event 12 to Event 120 - 04/04/2018 (Previous Events) Attachment CPUA_1515.txt (684 Downloads)
Prakash_Chennai Posts: 12 Rating: (0)
Suggestion To thank Quote Answer

6/12/2018 10:40 AM	Rate (1)
mopS04 Platinum Expert Joined: 3/5/2014 Last visit: 8/5/2022 Posts: 5521 Rating: (1054)	okay, so there is no hint in the previous entries. in a S7-400H-system the CPU goes into error-search mode, when there is a internal error. this error can be a memory-error, or something like this. When the CPU has checked the error, it is linking up automatically with its partner-CPU. CPU-behaviours in those cases is being improved in FW-Updates.I recommend you to update the FW to the newest version. Operating system updates V6 CPU412-5H PN/DP, CPU414-5H PN/DP, CPU416-5H PN/DP, CPU417-5H PN/DP To get information what was exactly, you need to contact Siemens with a Support Request. They can read the hex-codes in the diagnostic buffer. hope this helps, regards,
	FCK WAR! Be nice!
Suggestion To thank Quote Answer

6/12/2018 2:37 PM	Rate (0)
Prakash_Chennai Posts: 12 Rating: (0)	Hi mopso4, Thanks for the feedback, Because of the current Firmware Version (V 6.0.6) of the CPU It causes B-CPU to act like these. Internal error means due to program download or..? Regards Prakash
Prakash_Chennai Posts: 12 Rating: (0)	Last edited by: Prakash_Chennai at: 6/14/2018 10:41:12 AM Last edited by: Prakash_Chennai at: 6/14/2018 10:41:39 AM
Suggestion To thank Quote Answer

5/6/2024 12:21 PM	Rate (0)
VELOX-SURAT-PROJECTS Regular Member Joined: 12/21/2018 Last visit: 10/24/2024 Posts: 3 Rating: (0)	Dear sir, Problem solved or not???

Suggestion To thank Quote Answer

5/8/2024 4:55 AM	Rate (0)
Ayman Elotaify Platinum Member Joined: 5/28/2008 Last visit: 10/29/2024 Posts: 4516 Rating: (839)	VELOX-SURAT-PROJECTS Dear sir, Problem solved or not??? Hello, Please share your CPU part number and diagnostic buffer. The post from 2018. and we need to understand exactly your case from your CPU's diagnostic buffer to guide you with the reason.
	Ayman Elotaify
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on