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

Full Shutdown of F Program Activated

Created by: Surendhar_M at: 11/20/2024 8:10 PM (4 Replies)

Rating (0)

Thanks 0

5 Entries

11/20/2024 8:10 PM	Rate (0)
Surendhar_M Advanced Member Joined: 2/4/2015 Last visit: 7/1/2025 Posts: 72 Rating: (0)	Hi all, We have S7 410-5H redundant system for burner system application. We recently faced total stoppage of system. Found Rack 1 Power supply was faulty but Rack 0 CPU was in Run mode. Replaced the Power supply, both CPU went to Run mode but still found all safety charts in shutdown mode. We tried to restart using F_Shutdn block but not successful so entire program downloaded. Then all charts became healthy. Need to understand why logic went to shutdown mode? In diagnostic buffer logs were filled with other faults so no logs found during the stoppage time. We are now getting Internal fault with error OB requesting error in OB35. But system is running. As per manual , Errors that always trigger a full shutdown When an OB request error occurs (due to an OB overload, for example), a full shutdown is triggered irrespective of the F-STOP parameter assignment. But now system is running. Request experts to suggest the way forward. Attachment Burner Scheme.PNG (316 Downloads)

Suggestion To thank Quote Answer

11/22/2024 5:25 PM	Rate (0)
hdhosseini Diamond Expert Joined: 1/28/2009 Last visit: 8/31/2025 Posts: 6874 Rating: (1368)	Dear user, Errors that always trigger a full shutdown When an OB request error occurs (due to an OB overload, for example), a full shutdown is triggered irrespective of the F-STOP parameter assignment. Development of the an extensive safety logic in e.g. OB35 (only) may cause this error. As an example , OB35 is called in each 100ms and the execution of this extensive logic and the rest of controller's tasks extend to the next OB35 request and this is an overload. The logical solution would be classification of logic sections to FAST , SLOW. You can classify the critical analog signal monitoring and shutdown routines in FAST OBs while slow task such as valve operations , communication and less critical topics in SLOW OBs. By using this technique in design phase you may never encounter OB overload. Kind regards, hdhosseini
	Demo Channel on Youtube
Suggestion To thank Quote Answer

11/23/2024 8:42 AM	Rate (0)
Surendhar_M Advanced Member Joined: 2/4/2015 Last visit: 7/1/2025 Posts: 72 Rating: (0)	Hi Sir, Thanks for the reply. Can we try increasing the OB35 scan time from 100ms to 150ms? Regards Surendhar M

Suggestion To thank Quote Answer

12/5/2024 9:17 PM	Rate (0)
hdhosseini Diamond Expert Joined: 1/28/2009 Last visit: 8/31/2025 Posts: 6874 Rating: (1368)	If this is a machine in operation and System Acceptance Test was performed , I don't recommend to change the safety program because it may alter the overall signature . The best way is to contact the program developer and explain your situation and ask them for support.
	Demo Channel on Youtube
Suggestion To thank Quote Answer

6/28/2025 4:51 AM	Rate (0)
Surendhar_M Advanced Member Joined: 2/4/2015 Last visit: 7/1/2025 Posts: 72 Rating: (0)	Sure sir. Thanks....

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on