Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

profibus diagnositc frame

Created by: edek at: 8/10/2009 2:59 PM (4 Replies)

Rating (0)

Thanks 0

5 Entries

8/10/2009 2:59 PM	Rate (0)
edek Bronze Member Joined: 7/20/2006 Last visit: 11/5/2024 Posts: 128 Rating: (8)	hello, I'm using AmprolyzerV32 to diagnose my profibus and one of the salves is sending every 5sec diagnostic frame (DpSlaveDiag). It mean that it's something wrong with this slave? I'm asking becuase I had same problems with this slaves in the past. regards edek

Suggestion To thank Quote Answer

8/10/2009 9:02 PM	Rate (0)
jklm Platinum Member Joined: 12/22/2006 Last visit: 1/25/2022 Posts: 1742 Rating: (309)	Hello, Could you post an exchange?
	Best regards jklm Suggestion was helpful? Feel free to rate it.
Suggestion To thank Quote Answer

8/11/2009 9:36 AM	Rate (0)
TomDeWou Platinum Member Joined: 11/15/2006 Last visit: 5/7/2021 Posts: 1319 Rating: (173)	Did you have the same problems with this slave or just a device of this type? If you change this device, does it still appear? Does it show any errors in diagnostics?
	Have Fun! TomDeWou
Suggestion To thank Quote Answer

8/11/2009 11:05 AM	Rate (0)
edek Bronze Member Joined: 7/20/2006 Last visit: 11/5/2024 Posts: 128 Rating: (8)	hello, Sorry for that my last post was not clear. I had the problem with Linmot controller(after few days of using profibus modul of this controller broke down). I put the new controller and start to diagnose profibus network to find the reason. I noticed that the controller is sending diagnose frame, but i don't know exactly what is it mean? It could be standard procedure for this controller or maybe there is something wrong with modul? regards

Suggestion To thank Quote Answer

8/11/2009 11:16 AM	Rate (0)
fritz Diamond Expert Joined: 10/7/2005 Last visit: 11/7/2024 Posts: 3026 Rating: (1057)	edek ... one of the salves is sending every 5sec diagnostic frame (DpSlaveDiag). It mean that it's something wrong with this slave? could be dear edek, but it could also be caused by simply loosing the comms to the DP Slave. Put simple, you'll see a diagnostic message from a DP Slave in the follwoing two cases: 1.) On bus/DP Slave startup 2.) In cases where the DP Slave has the "need" to let the Master know that it is not "happy" (what diag infothe Slave can havedepends on what the DP Slavemanufacturerdecided) in which case it will flag this to the DP Master who will then request the Diagnostic data from the DP Slave in the next bus scan. The first 6 bytes of a Slave Diag message are mandatory and standardised by Profibus International and are the minium Diag message lenght (which tells you the "generic" stuff, attached is quite a nice biefpdf that explains the meaning of these first 6 bytes). A manufacturer may however decide to submit extra data with it (so called extended diagnostic). If your Slave issues these, you can "decipher" their meaning together with the Slave manual (where they should be listed) and/or GSD file. Ihope this helps Attachment SlaveDiag.pdf (139 Downloads)
	Cheers fritz The advice and opinion given in this thread is that of the author and does not necessarily reflect the views of I S Systems Pty Limited. To find out how I S Systems can help you with your automation needs please visit www.issystems.com.au.
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on