Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Stop of B-CPU

Created by: JoBa at: 4/20/2010 5:01 PM (4 Replies)

Rating (1)

Thanks 0

5 Entries

4/20/2010 5:01 PM	Rate (0)
JoBa Posts: 4 Rating: (0)	Hi, can anyone interpret why my B-CPU suddenly stopped at 04:00:50:986 pm 04/20/10 ...? Thanks for all help =) Jon Diagnostic buffer of module CPU 417-4 H Order No./ Description Component Version 6ES7 417-4HL01-0AB0 Hardware 1 - - - Firmware V 3.1.4 Rack: 0 Slot: 3 Settings: Time including CPU/local time difference (0 h) Event 1 of 1500: Event ID 16# 7303 Event ID: 16# 7303 OB: 16# 48 PK: 16# 1C DatID 1/ 2: 16# 5B CD Additional info1 / 2 / 3: 16# F908 0000 0084 Incoming event 04:05:02:300 pm 04/20/10 Event 2 of 1500: Event ID 16# 43E2 Event ID: 16# 43E2 OB: 16# C9 PK: 16# F9 DatID 1/ 2: 16# 00 00 Additional info1 / 2 / 3: 16# 0000 0000 0000 Incoming event 04:05:02:296 pm 04/20/10 Event 3 of 1500: Event ID 16# 43E9 Event ID: 16# 43E9 OB: 16# 6C PK: 16# F0 DatID 1/ 2: 16# 00 00 Additional info1 / 2 / 3: 16# 0000 0000 0000 Incoming event 04:05:01:376 pm 04/20/10 Event 4 of 1500: Event ID 16# 43E1 Event ID: 16# 43E1 OB: 16# BC PK: 16# F9 DatID 1/ 2: 16# 00 00 Additional info1 / 2 / 3: 16# 0000 0000 0000 Incoming event 04:05:01:376 pm 04/20/10 Event 5 of 1500: Event ID 16# 43E8 Event ID: 16# 43E8 OB: 16# B6 PK: 16# F0 DatID 1/ 2: 16# 00 00 Additional info1 / 2 / 3: 16# 4309 0820 0720 Incoming event 04:04:57:972 pm 04/20/10 Event 6 of 1500: Event ID 16# 5371 Event ID: 16# 5371 OB: 16# 03 PK: 16# F0 DatID 1/ 2: 16# 50 00 Additional info1 / 2 / 3: 16# 0004 0000 0000 Incoming event 04:04:56:224 pm 04/20/10 Event 7 of 1500: Event ID 16# 43E0 Event ID: 16# 43E0 OB: 16# 8B PK: 16# F9 DatID 1/ 2: 16# 00 00 Additional info1 / 2 / 3: 16# 0000 0000 0000 Incoming event 04:04:46:712 pm 04/20/10 Event 8 of 1500: Event ID 16# 43E3 Event ID: 16# 43E3 OB: 16# 98 PK: 16# F9 DatID 1/ 2: 16# 00 00 Additional info1 / 2 / 3: 16# 0000 0000 0000 Incoming event 04:00:50:986 pm 04/20/10 Event 9 of 1500: Event ID 16# 45E4 Event ID: 16# 45E4 OB: 16# 9E PK: 16# F0 DatID 1/ 2: 16# 72 C4 Additional info1 / 2 / 3: 16# 4533 0000 0F7C Internal error, Incoming event 04:00:50:986 pm 04/20/10 Event 10 of 1500: Event ID 16# 7301 Event ID: 16# 7301 OB: 16# 48 PK: 16# 1C DatID 1/ 2: 16# 5B C4 Additional info1 / 2 / 3: 16# F000 45E4 0000 Incoming event 04:00:50:986 pm 04/20/10
JoBa Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

5/2/2010 1:58 AM	Rate (0)
H-H Platinum Member Joined: 7/2/2008 Last visit: 12/21/2025 Posts: 929 Rating: (309)	Hello JoBa, I'm sorry for such late contribution and I hope that youhad already foundthe reason why the standby CPU had gone into STOP. I hope (in future) you change settings of your diagnostic buffer in order not to show event information in hexadecimal format. I think people will understand diagnostic buffer better if it's not in hexadecimal format. Best regards. H-H

Suggestion To thank Quote Answer

5/2/2010 7:37 PM	Rate (1)
Late Platinum Member Joined: 1/7/2006 Last visit: 5/11/2025 Posts: 2705 Rating: (321)	Hi, There is one newer Firmware version V3.1.5 at the next link: Operating System Updates for CPU412-3H / CPU414-4H / CPU414-4H PG / CPU417-4H I prefer also the ascii presentation of the diagnostic buffer. Correction with firmware version V3.1.5 In case ofa power-off to a subsystem in redundant mode,while a memory compression is active, it could occur that the remainig subsystem is unoperable. With this version it is possible to force bit memory adresses in ranges greater than 8191. Hmm, that won't change anything I think...
	I hope that the answer will help, if you have still questions, don't hesitate to ask me. All the best, Late Never say never, think in solutions, not in trouble......
Suggestion To thank Quote Answer

10/29/2010 11:49 AM	Rate (0)
Xia Bofeng Posts: 1 Rating: (0)	Isthe logic & IO modules still function well after B CPU stop in this case (Event ID 16# 4533) ?
Xia Bofeng Posts: 1 Rating: (0)
Suggestion To thank Quote Answer

10/29/2010 7:39 PM	Rate (0)
gre_m Posts: 947 Rating: (45)	Hiello JoBa Your diagnostic buffer: Event 1 of 1500: Event ID 16# 7303 = *H system (1 of 2) changed to redundant mode* Event 2 of 1500: Event ID 16# 43E2 = *Change from updating to redundant mode* Event 3 of 1500: Event ID 16# 43E9 = *Standby CPU: change from startup after updating* Event 4 of 1500: Event ID 16# 43E1 *Change from link-up after updating* Event 5 of 1500: Event ID 16# 43E8 = *Standby CPU: change from link-up after startup* Event 6 of 1500: Event ID 16# 5371 Distributed I/Os: end of the synchronization with a DP master Event 7 of 1500: Event ID 16# 43E0 = *Change from solo mode after link-up* Event 8 of 1500: Event ID 16# 43E3= *Master CPU: change from redundant mode to solo mode* Event 9 of 1500: Event ID 16# 45E4 = *Standby CPU: change from redundant mode after error-search mode* Event 10 of 1500: Event ID 16# 7301 = Loss of redundancy (1 of 2) due to failure of a CPU CPU goto in stop before event 10, but event before 10 not in your meassage
gre_m Posts: 947 Rating: (45)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on