Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

CPU does not start after power failure

Created by: Romarik_c at: 3/12/2021 11:36 AM (7 Replies)

Rating (0)

Thanks 0

8 Entries

3/12/2021 11:36 AM	Rate (0)
Romarik_c Member Joined: 1/28/2021 Last visit: 10/16/2024 Posts: 11 Rating: (0)	Hello, Following a power cut on CPU319, it did not start in run. In the diagnostic buffer, the event is: Event 3 of 10: Event ID 16 # 4301 Switching from STOP to START-UP Cause of STOP: STOP by I / O management Getting started information: - Saving the time for time stamping at the last power-up - Monoprocessor mode Start-up in progress / carried out last: - hot start by positioning the switch; last power-up saved Authorized start-ups: - manual hot start allowed - automatic hot start allowed Last command in force or automatic start-up on power-up: - hot start by positioning the switch; last power-up saved Operating status so far: OFF (internal) Requested operating status: START-UP (warm start) Occurring event 12: 08: 47.196 11/03/2021 (Coding: 16 # 4301 FF46 C772 4548 0813 7713) By activating the stop / run switch, the cpu started normally. On the rack there is only the CPU and a Phoenix Contact card for the Interbus network (IBS S7 300 DSC-T). I think the IBS card is involved, because it probably takes longer to start up than the CPU (I have to test this soon). Can you help me find a solution so that the CPU starts up without intervention on the switch? Can the startup of the CPU be delayed, for example? Attachment 20210311_DEP_TUI_MICROCOUPURE.txt (419 Downloads)

Suggestion To thank Quote Answer

3/12/2021 11:50 AM	Rate (0)
mopS04 Platinum Expert Joined: 3/5/2014 Last visit: 8/5/2022 Posts: 5521 Rating: (1054)	hi Romarik_BMI, please share the diagnostic buffer in english. So it is easier for us to help you, thanks!
	FCK WAR! Be nice!
Suggestion To thank Quote Answer

3/12/2021 12:14 PM	Rate (0)
Romarik_c Member Joined: 1/28/2021 Last visit: 10/16/2024 Posts: 11 Rating: (0)	mopS04 hi Romarik_BMI, please share the diagnostic buffer in english. So it is easier for us to help you, thanks! Ok ,sorry, The diagnostic buffer in english is in attachment. Attachment Diagnose.txt (446 Downloads)

Suggestion To thank Quote Answer

3/18/2021 7:48 AM	Rate (0)
Romarik_c Member Joined: 1/28/2021 Last visit: 10/16/2024 Posts: 11 Rating: (0)	Does anyone have a suggestion regarding this problem?

Suggestion To thank Quote Answer

3/18/2021 10:06 AM	Rate (0)
Duris_I Diamond Member Joined: 4/28/2015 Last visit: 11/16/2024 Posts: 10614 Rating: (828)	Hello, you have some DP Slaves identification problem, looks like. It can take some time to ident Slaves on bus so this can be problem. I recommend generally include more types of diagnostic OBs to your prj and also download to CPU. In diag buffer you have already one that isn't included, also other like comm OBs and other need to be included and then can solve your start-up ident bus problem.
	Last edited by: Duris_I at: 03/19/2021 09:42:54 Slaves With best regards... Ivan Duris Flight: OMICO
Suggestion To thank Quote Answer

3/18/2021 10:35 AM	Rate (0)
Ayman Elotaify Platinum Expert Joined: 5/28/2008 Last visit: 11/6/2024 Posts: 4516 Rating: (839)	Hello, Ensure that all slaves connected to CPU are powered up again. May be one or more are not powered up due to fuse cut or MCB trip.
	Ayman Elotaify
Suggestion To thank Quote Answer

3/19/2021 8:51 AM	Rate (0)
Romarik_c Member Joined: 1/28/2021 Last visit: 10/16/2024 Posts: 11 Rating: (0)	Hello, The following OBs are loaded: OB80 - OB82 - OB85 - OB86 - OB87 - OB100 - OB121 - OB122 The Interbus card is special, I am not sure that it is ready "before" the CPU. Is there a solution to delay the setting in RUN of the CPU, when starting up? I'll do a power-up test next week.
	Last edited by: Romarik_BMI at: 03/19/2021 08:54:52
Suggestion To thank Quote Answer

4/1/2021 8:29 AM	Rate (0)
Romasxp Experienced Member Joined: 8/13/2015 Last visit: 11/12/2024 Posts: 85 Rating: (6)	Hello, do you really have OB86? By error log there is no such OB. Just add all empty OB's shown in error log. This helped for my in similar problem.

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on