12/29/2019 12:02 PM | |
Joined: 9/27/2006 Last visit: 9/22/2024 Posts: 12282 Rating: (2684) |
Hello sujith; Have you used the CPU's diagnostic buffer to identify the fault messages logged by the PLC when it detects a communication fault? If the required diagnostic OBs are part of your program (OB86, OB 121, OB122...) there should be indications on the faulty nodes and the source of the program. If the error messages of the diagnostic buffer are difficult to decipher, simply use the Save As button on the diagnostic buffer screen to save all messages to a text file that you can attach here: we can then have a look at them and help you locate the problem nodes. Next, follow the available troubleshooting suggestions from these websites, to organize your interventions: Top 5 reasons your Profibus network failed Tips for trouble shooting on the PROFIBUS-DP You should examine the possibility that the source of your problem is located in the terminators of your network segment. If the termination circuit is no longer functional at both ends of a segment or if it is left without power (the end-node where the terminator is ON is left without power) you will lose the complete network. More technical information is also found in the Downloads section of Profibus.com, it is a site well worth visiting when dealing with a Profibus-DP network. Not every plant is equipped with a Profibus tester, but they are efficient tools to locate the source of a network fault. They are provided by Procentec, SMAR, Softing, and others. If you feel you require one and do not want to invest right now, you could try to locate a local integrator who possesses one and us proficient in it: Google search on Profibus testing equipment Hope this helps, |
Follow us on