10/8/2020 12:35 PM | |
Posts: 6 Rating: (0) |
Hi dear engineers i have s7-300 with 3152DP-2AH14-0AB0 and some im361 and 3 im 153 and micromaster profibus DP module this is the error code appears on cpu information Event 25 of 209: Event ID 16# 494D STOP due to IO error No relevance for user (Z2): 5752 (Z3): 2101 Previous operating mode: RUN Requested operating mode: STOP (internal) External error, Incoming event 04:18:49.197 PM 08/22/2015 (Coding: 16# 494D FF84 C000 0000 5752 2101) Log. base address of the DP master: 2047 Requested OB: Rack failure OB (OB86) OB not found, or disabled, or cannot be started in the current operating mode External error, Outgoing event 01:18:06.747 PM 08/22/2015 (Coding: 16# 38C4 FE56 C054 07FF 07F9 0103) i've checked bus connector and profibus connectors and all module connection is there any body to help me find this error code comes from wich one thanks ------------------------------------------------------------------------------------------ |
Last edited by: Jen_Moderator at: 10/09/2020 08:23:25New subject after splitting |
|
10/8/2020 2:53 PM | |
Posts: 6 Rating: (0) |
here my diagnostic buffer
AttachmentDiagnose.txt (155 Downloads) |
10/8/2020 4:28 PM | |
Joined: 9/27/2006 Last visit: 4/26/2024 Posts: 12257 Rating: (2665)
|
Hello amir.r; Your diagnostic buffer shows a recurring message for a great number of DP slves: "Requested OB: Rack failure OB (OB86) OB not found, or disabled, or cannot be started in the current operating mode" Without an OB86 in your program, when a rack failure is detected on your distributed I/O network, your CPU will show the BF LED (possibly also the SF LED) and go to Stop mode. With an OB86 in the PLC program, the CPU will show the error LEDs but will not go to STOP, and the diagnostic buffer wiill show in much more details the înformation on the fault. So, first step is to create a new OB (in the program blocks), name it 86, and download it to the CPU. No need for any internal programming at this time, the interface parameters of the OB86 are enough to connect with the CPU diagnostics. Your diagnostic buffer seems to show a great many rack faults occurring at very close intervals to each other m(note that your system Real-Time Clock is not showing present time, you should correct that), which leads me to believe that you are facing a termination problem on your network. Remember that the terminators must be active AND POWERED on both end-stations of your network. If for any reason the terminators are OFF or the end-node has lost power you will get reflections on the network that will swamp the CPU with fault messages (which would look like the contents of your diagnostic buffer). That would also explain why the diagnostic address of the CPU is included in your fault messages. If the termination switch on one of the end-stations is loose (occasionally turns OFF without user intervention, then returns ot ON status) then your CPU would receive messages from remote stations entering fault state, then returning to operating status. Have a look at this very informative (and short) troubleshooting guide for Profibus networks: https://us.profinet.com/top-5-reasons-your-profibus-network-failed/ Hope this helps, Daniel Chartier |
Last edited by: dchartier at: 10/08/2020 16:45:52 |
|
This contribution was helpful to1 thankful Users |
10/8/2020 6:40 PM | |
Posts: 6 Rating: (0) |
here the screenshot , and there is no new fault , but previous faults still needs OB86 |
Follow us on