5/1/2022 8:51 PM | |
Joined: 7/10/2021 Last visit: 5/7/2022 Posts: 1 Rating: (0) |
Dear All, Recently we observed one problem in CPU-317/2pn- DP. CPU-317 incorporate with some input/output cards and one Communication Processor. Our problem is some times CPU 317 goes to stop mode and SF enable. Its occurred after one week or sometimes after 2-3 days. can anybody figure out the real cause of this problem? ------------------------------------------------------------------------------------------ AttachmentDiagnose_09032022_09_39.txt (614 Downloads) |
Last edited by: Jen_Moderator at: 05/02/2022 06:05:29New subject after splitting |
|
5/1/2022 9:49 PM | |
Joined: 9/27/2006 Last visit: 11/7/2024 Posts: 12293 Rating: (2691)
|
Hello umayb; Reading your diagnostic buffer, we can see these problems immediately: "Requested OB: Rack failure OB (OB86) OB not found, or disabled, or cannot be started in the current operating mode" and "Requested OB: Diagnostic interrupt OB (OB82) OB not found, or disabled, or cannot be started in the in the current operating mode" To recognize and respond to a specific type of fault, Step 7 uses diagnostic organization blocks specifically designed to gather information from these faults, You can find a list of such diagnostic OBs, for S7-300 in the screenshot below, take from this document: - Which organization blocks do you need for error handling in STEP 7 V5.5? https://support.industry.siemens.com/cs/ww/en/view/11499205 In your case, you are experiencing I/O rack failure on your Profibus or Profinet networks, for which OB86 is needed, and hardware interrupt faut on specific modules in the CPU rack or the network, for which OB82 is required. If the CPU cannot find OB86 and OB82 in the user program, the CPU will go to fault with SF and BF (for communication fault) LEDs active. To obtain more details on the faults in the diagnostic buffer and possibly keep the CPU running even in the prsence of a single fault, introduce OB86 and OB82 in your program: create 2 New Blocks (in the Step 5 Block forlder), name them OB86 and OB82, compile and dwnload them to the CPU. For the moment empty blocks will do the job, no need for any program inside them. When the SF and BF LEDs appear again (but the CPU is still running) open the diagnostic buffer once again, you should have enough information to identify the faulty modules by their addresses in HWConfig, so you can examine why they are at fault. Hope this helps, Daniel Chartier |
Follow us on