416-2XK01-0AB0 INTF

Hi, 

No problem. Have a look at this link about diagnosing Profibus networks:

https://support.industry.siemens.com/tf/ww/en/posts/19855/

By the way my favorite method is the visual inspection. Most of the cases the issue caused by a broken plug, loose wire, injured cable ... and POWER SUPPLY... This can be found by a good pair of eyes!

Good luck!

Hello

Thanks microman 

Today we conducted testing of profibus communication by using profibus tester (Profi-TM Professional) during the testing it shows a good communication signal, i attached the recent diagnostic buffer i extracted in reference with the alarm happen recently. I suspected that it is lose its communication suddenly that is why there is an access error recorder and at the event 69 it stop already.

I will check all the profibus connector and cables for visual problem and will update you again regarding the problem.

Thanks  

Hi,

I think we have got it! Great work there!
It is important that the panels and instruments are regularly checked. If you can find the reason of the profibus "disruptions" the nightmare probably over. Anyways If the error coming and going randomly it is likely that it is a loose wire somewhere. Maybe a loose terminal in Power Supply.

By the there is a good FAQ about your problem: STOP through the priority class run system

Hello,

Thanks microman for the support hopefully we able to solve the problem today we are planning to check all the profibus connector and replace some of it that showing in the diagnostic will also check the power supply connection that might some lose on it.

Hello

We already had a shut down and and these are the things we done we make the communication speed slower from the default 1.5Mbps to 500kbps (setting from the CPU) and we checked all the profibus connector and changed the master profibus connector with PROFIBUS DSUB connector with diagnostic LED with Integrated programming / diagnostic port. I attached the quick test result we had after all the job was done.  Hope we improve all the communication issue.

Thanks for the support ;)

Hello,

After several weeks of observation problem start to come back we already changed some IM that we suspect having problem since it always appears in diagnostic buffer, now almost all station were already replaced the PROFIBUS connector and still there are time it shutdown the machine with the same fault in diagnostic buffer but in different stations.  PROFIBUS diagnostic test shows also satisfactory results that all communication and signals are in good.

What else do you think that we must check and rectify?

Thanks ;)

Hi, 

So your DP slaves still dropping off the network even in lower speed. OK. Uploading the diagnostic buffer is a good idea just to see what is going on but maybe the issue is related rather to HW/installation/passive componnents. 

Anyways I have the funny feeling that the reason of this random behavior is that the Profibus slot time(or any other related bus parameter) too short, which is usually automatically calculated by HW config/Netpro. The reason of this being too slow can be the delay introduced by multiple "transparent" NW componnents. 

So questions:

• CPU Diag buffer please
• Diag of the failing head module if possible
• Please screenshot of the Profibus properties and the bus parameters
• Do you have Transparent Network devices installed in your network? If yes how many and what type
• If possible a layout drawing of network(as built)