9/30/2017 3:04 PM | |
Joined: 9/27/2006 Last visit: 11/14/2024 Posts: 12294 Rating: (2691) |
Hello nanchi; BF stabnds for Bus Faullt: an error occured on the network. SF stands for System Fault, which could stand for any internal problem in the CPU, such as accessing an unreachable address in a block (FC, FB..), or a programming error... Depending on the diagnostic OB that is called for the fault (as shown in the diagnostic buffer messages) you can determine what type of error occured. First, are all the slaves showing the BF LED active? That would indicate a complete failure of the network, often due to lost termination on the end points of your network. Very oftem, the SF that appears at the same time as the BF means that your program is trying to access data from slaves that are no longer reachable, therefore a SF fault appears. So first check the diagnostic buffer of the CPU; for example, open the HWConfig, go online, click on any module that shows a red slash icon (inficating error), even the CPU. That opens the diagnostic buffer for each fault modue, ans you can see (sans Save) the messages logged for these modules. If you save the messages from the cPU and post the text file here on the forum as an attachment, we can probably help you understand the messages and identify the possible source of the fault. For Profibus-DP troubleshooting, especially if it is the first time, you might need some guidance. I can suggest this document: PROFIBUS fault finding and health checking Hope this helps, Daniel Chartier |
Last edited by: dchartier at: 9/30/2017 3:27:54 PM |
|
This contribution was helpful to1 thankful Users |
10/1/2017 10:18 AM | |
Joined: 7/27/2017 Last visit: 7/25/2024 Posts: 79 Rating: (0) |
hello sir, i have checked my terminations on the two ends i think they are ok, and i still have SF/BF on cpu and BF on all the slaves. the attachement is the massege on the diagnostic buffer on the cpu. pls help. AttachmentDiagnose.txt (417 Downloads) |
Follow us on