9/13/2021 11:57 AM | |
Joined: 7/23/2015 Last visit: 1/16/2024 Posts: 3 Rating: (0) |
Ok. These are the CPU errors. I don't have SFB20 programmed anywhere. The mmc and the CPU I have changed recently. Load memory and work memory are ok too. Tnaks for your answers. AttachmentErrorCPU.txt (218 Downloads) |
9/13/2021 3:34 PM | |
Joined: 9/27/2006 Last visit: 4/26/2024 Posts: 12257 Rating: (2665)
|
Hello themikis; You should be right, that there are no calls for SFB 20 "STOP" in your program, this function is seldom used voluntarily by the programmer. In your case, the order to stop the CPU comes from the CPU's operating system, when it faces events that it cannot control or bypass. The problem is that your diagnostic buffer only logs the last 10 messages saved, and it does not give us much information to go on. messages 9 and 10 are more informative, but you should open the diagnostic buffer screen, click on the Settings button, and increase the number of messages logged to the buffer (you can easily go up to 100 messages). Then run the CPU and use the Save As.. button once more to create a more complete diagnostic file. Message 9 states that OB 86 ("remote rack failure") is being called for a Profibus slave with diagnostic address 2020 (Dirección base lóg. del esclavo DP: Dirección de entrada: 2020). You should be able to locate that slave in HWConfig, in the Profibus configuration. If you open HWConfig onlineyou will see that defective slaves will be marked with a red cross, identifying them. Message 10 requires the presence of OB 122 ("I/O access error") , this fault often occurs when your program blocks try to read or write to a remote slave that has failed. It looks as if the unreachable address is PIW302 (al leer área P, acceso a palabra, Dirección de acceso: 302), see if you can find it in your program, you can look for it with cross-references.. Once you hace located the problematic Profibus slave, you have to understand nd diagnose the problem. This small document should give you a list of thisng to check: https://us.profinet.com/top-5-reasons-your-profibus-network-failed/ I hope these basic informations can help you look for the failed save, shpow us the more complete diagnostic buffer and we may provide more help. Hope this helps, Daniel Chartier |
Follow us on