9/26/2021 3:44 PM | |
Posts: 7 Rating:
|
Hello Our system bug from time to time random and we cannot define the cause of faults. When we check the HW online the program is running normal. The diagnostic buffer contains the following attached 02 saved text . Could you please help me how to find reason correct and localization of error. AttachmentDiagnose_last events 2.txt (635 Downloads) |
9/26/2021 4:49 PM | |
Joined: 9/27/2006 Last visit: 8/17/2024 Posts: 12277 Rating:
|
Hello nadi; The first 2 messages from your diagnostic buffer (setup for up to 500 messages tota). indicate the need for diagnostic OBs 86 and 122. Please do a search for OB 86 and in the diagnostic buffer logs, see if other remote rack errors are present. do the same for OB 122, I/O access error , and list these entries, this will be useful later. First thing is to determine if some ofthese messages messages are linked, that is, if the calls to OB 86 and OB 122 come from the same event. Let's look at events 1 and 2 first, as an example. OB 86 is called when a Profibus station (or Profinet device) loses communication physically with the master. In your case , the faulty slave in message #1 is at Profibus address 4. Please look at the hardware configuration and open slave no. 4 to identifuy what it is and where it is located in your plant; you can open the local diagnostic buffer on this node, to see if there are events specific to that node that have been logged. You should look at the I/O addresses associated with that slave no 4 and check if you find address 1006 in the I column. OB 122 will be called if your program tries to reach PIW 1006 while the slave is at fault and connot exchange data with the Profibus master: "I/O access error, reading P area, word access, Access address: 1006" If address PIW 1006 and slave node 4 are linked, it means you have lost connection to that slave temporarily (you will get incomig OB 86 and outgoing OB 86 entries in your buffer.. If we look further in the diagnostic buffer log, you will find recurrent calls of OB 122, for addresses 1000 to 1008. Are these linked to the same slave no. 4? The buffer contains also OB 86 calls for slaves no. 6 and no. 20, these must be checked also. Most issues with temporary loss of DP slaves come from physical connection problems, on the cable, the connectors or the termination switches; on older machines or equipment that is subject to vibrations these elements should be checked more frequently. Have a look at this quick overview to guide you: https://us.profinet.com/top-5-reasons-your-profibus-network-failed/ Hope this helps, Daniel Chartier |
Last edited by: dchartier at: 09/26/2021 16:55:56Last edited by: dchartier at: 09/26/2021 16:58:42 |
|
This contribution was helpful to
3 thankful Users |
9/26/2021 7:41 PM | |
Posts: 7 Rating:
|
Hello Mr chartier, first thanks for your reply the problem is not the appearance of an event OB or the reading, i don't understund why each event happend give new adress and when we check online all HW are ok (mean each time an event appeared/disappeared in few milliseconds like a voltage fluctuation) for exemple we have diffirent Rack failure OB (OB86) for diffirent station and area : Event 378 : at 01:57:48.550 PM 09/26/2021 ---- station 6 Event 302 : at 02:14:07.355 PM 09/26/2021 --- station 4 Event 226 : at 02:36:44.378 PM 09/26/2021 --- station 11 Event 146: at 03:09:17.694 PM 09/26/2021 --- station 6 Event 70: at 03:10:16.050 PM 09/26/2021 ---station 17 … etc
AttachmentDiagnose_HW online 3.txt (732 Downloads) |
9/26/2021 7:42 PM | |
Posts: 7 Rating:
|
Hello Mr chartier, first thanks for your reply the problem is not the appearance of an event OB or the reading, i don't understund why each event happend give new adress and when we check online all HW are ok (mean each time an event appeared/disappeared in few milliseconds like a voltage fluctuation) for exemple we have diffirent Rack failure OB (OB86) for diffirent station and area : Event 378 : at 01:57:48.550 PM 09/26/2021 ---- station 6 Event 302 : at 02:14:07.355 PM 09/26/2021 --- station 4 Event 226 : at 02:36:44.378 PM 09/26/2021 --- station 11 Event 146: at 03:09:17.694 PM 09/26/2021 --- station 6 Event 70: at 03:10:16.050 PM 09/26/2021 ---station 17 … etc
AttachmentDiagnose_HW online 3.txt (559 Downloads) |
9/26/2021 8:24 PM | |
Posts: 7 Rating:
|
also all slave are in same link. see attached image HW.
|
9/28/2021 10:34 AM | |
Posts: 7 Rating:
|
Hello Mr Aymen It's continues casting machine *(Steel Meltshop factory) , we have 6 strands same architecture (in software & HW) but separate, work since 8 years. Last month we had problem only in strand N:4 I change completely the Profibus socket by new one on the first and the last node on the bus and ensure termination resistor in ON position (station 25 && station 26). Also I also assured all other terminators on the intermediate nodes in OFF position. the problem still continue and today we have module ok and Error LED (SF) in permanent status. see attached last diagnostic. Event 1 : 07:46:17.432 AM 09/28/2021 : station 8 : return Event 86 : 07:46:17.338 AM 09/28/2021 : station 8 : Failure Event 87 : 07:35:35.324 AM 09/28/2021 : station 17 : return Event 160: 07:35:35.239 AM 09/28/2021 : station 17 : Failure Event 161: 07:34:13.535 AM 09/28/2021 : station 4 : return Event 234: 07:34:13.448 AM 09/28/2021 : station 4 : Failure Event 235: 07:29:54.978 AM 09/28/2021 : station 17 : return Event 308: 07:29:54.895 AM 09/28/2021 : station 17 : Failure Event 309: 07:03:41.692 AM 09/28/2021 : station 4 : return Event 390: 07:03:41.594 AM 09/28/2021 : station 4 : Failure Event 391: 06:48:15.611 AM 09/28/2021 : station 20 : return Event 392: 06:48:15.772 AM 09/28/2021 : station 20 : Failure Event 393: 06:42:26.866 AM 09/28/2021 : station 20 : return Event 394: 06:42:26.696 AM 09/28/2021 : station 20 : Failure Event 395: 06:30:26.506 AM 09/28/2021 : station 8 : return Event 462: 06:30:26.428 AM 09/28/2021 : station 8 : Failure Event 463: 06:04:34.067 AM 09/28/2021 : station 20 : return Event 464: 06:04:33.894 AM 09/28/2021 : station 20 : Failure Event 465: 06:03:35.101 AM 09/28/2021 : station 11 : return thakns for support. Kheireddine AttachmentDiagnose_28092021.txt (571 Downloads) |
9/28/2021 9:28 PM | |
Joined: 9/27/2006 Last visit: 8/17/2024 Posts: 12277 Rating:
|
Hello Kheireddine; You seem to have done a great deal of investigating by yourself, and we have tried to help you with our knowledge and experience. Still, we always return to the same conversation about intermittent faults on your network nodes. Looks like it is time for you to investigate your netwok problems with specialized tools that would help you discover the reasons behind your error messages and loss of communications. Tools such as this one, from Softing: https://industrial.softing.com/products/network-tester-and-analyzer/profibus-tester-5.html The video presentation below will give you an introduction to troubleshooting techniques with the Profibus tester 5.: https://youtu.be/nwgx8GZ51nw This is another excellent Profibus network troubleshooter equipment, from Procentec: https://procentec.com/products/profitrace/?content-1 Another option from InduSol: There are other vendors of similar test equipment, with a range of functions and price that you will need to evaluate. If you would rather not purchase at this time, or go yhrough thr necessary learning curve, look for an integrator who has this type of equiment and the knowledge to use it, and rent his services to analyze your Profibus-DP network and provide solutions. Hope this helps, |
Last edited by: dchartier at: 09/28/2021 22:01:51Last edited by: dchartier at: 09/29/2021 02:46:29 |
|
This contribution was helpful to
2 thankful Users |
Follow us on