7/9/2018 11:29 AM | |
Joined: 6/12/2009 Last visit: 5/20/2024 Posts: 75 Rating:
|
Hello dchartier, Thanks for feedback and problem is solve. Dont mind one more question... Suppose due to some problem of drive that particular drive will out of profibus loop then how can we identify node add ?? Means profibus node not communicate with master (here cpu 315 2 dp) then need acknowledgement. Regards, Susmit Prajapati.
------------------------------------------------------------------------------------------ |
Last edited by: Jen_Moderator at: 7/9/2018 1:25:44 PMNew subject after splitting |
|
7/9/2018 4:44 PM | |
Joined: 9/27/2006 Last visit: 1/22/2025 Posts: 12330 Rating:
|
Hello sus; All Profinus-DP masters have mechanisms to provide diagnostics for a lost or unresponsive node. On a CPU 315-2DP, you will get a BF active LED (Bus Fault), and probably a SF (System Fault, due to a programming or I/O access error).on the CPU. Using diagnostic OBs 86, 121 and 122 will provide this informatuon in the diagnostic buffer of the cPU, but that requires that someone with a programming software and cable interface with the CPU. If you would like to have runtime information on failed Profibus slaes, you could look to this sample provided by Siemens: Sample program: history for failed slaves https://support.industry.siemens.com/cs/ww/en/view/2289283 Hope this helps, Daniel Chartier |
7/10/2018 8:40 AM | |
Joined: 6/12/2009 Last visit: 5/20/2024 Posts: 75 Rating:
|
Hello dchartier, Again thanks... I know how to diagnose node in profibus loop but i want to give some indication on HMI regarding that faulty node add. Means responsible person can easily trace out of profibus loop node add through HMI only. No need to go online with step 7 or portal. Just through HMI can identify it. regards, susmit prajapati.
|
Follow us on