2/12/2018 9:14 AM | |
Posts: 21 Rating: (0) |
Dear All, I have a problem of redundancy in my S7-400 Cpu 414-4h Network. REDF led is permanantly on as well as BUS1F is blinking continously. I am unable to make my system redundant. Could you please tell me what would be the problem in the network. Thanks Muhamma saqib ------------------------------------------------------------------------------------------ |
Last edited by: Jen_Moderator at: 2/12/2018 2:57:36 PMNew subject after splitting |
|
5/27/2018 1:29 PM | |
Posts: 21 Rating: (0) |
Thanks Daniel for you cooperation . Please see the attached Diagnostic Buffer Text files for both 2 PLC's. Please reccomend me how can i get redandancy. Mainly problems are timer faults that are used in functions. Thanks AttachmentDiagnose.txt (551 Downloads) |
5/27/2018 1:30 PM | |
Posts: 21 Rating: (0) |
AttachmentDiagnose.txt_1.txt (400 Downloads) |
5/27/2018 5:08 PM | |
Joined: 9/27/2006 Last visit: 11/16/2024 Posts: 12294 Rating: (2691)
|
Hello saquib; Both the types of messages linked to OB 122 (I/O Access Error) in your diagnostics buffer messages and the comibination of the active LEDs point to one (or more) DP slave not responding on your MPI/DP port (BUSF1). See the attachment below, taken from the following manual (which I recommend you study when working with fault-tolerants Systems; this is from section 5.2): Simatic Fault Tolerant Systems S7-400H : https://support.industry.siemens.com/cs/ww/en/view/82478488 The faults relevant to OB 121 (Programming error: Timer number error) I have not seen before; it may be resolved along with the redundancy error linked to the REDF LED when you correct the Profibus-DP connectoion to the failing slaves. The easiest way to locate the faulty slaves is to open the HWConfig editor, and then go ONLINE (click on the glasses icon in the menu bar). In that view, failing nodes are identified with a red cross icon, meaning failure. if you double click on the identified slaves, you will open the diagnostic buffer for ghe slaves and the messages logged there can help you understand the cause of the problem locally. Hope this helps, Daniel Chartier |
Follow us on