8/17/2021 2:25 AM | |
Joined: 8/17/2021 Last visit: 9/12/2023 Posts: 6 Rating: (0) |
Hello I would like you to help me to determine why my PLC wents to STOP During the PLC review, a SIMATIC 6ES7 414-4HR14-0AB0 PLC was found in STOP mode. I share below some lines of the diagnostic buffer of the CPU 414-4 H PG: I hope it would be enought to get an idea about why the PLC is in STOP mode. Thanks Diagnostic buffer of module CPU 414-4 H PG [snip] Thanks RHurt AttachmentDiagnostic_Buffer.txt (712 Downloads) |
Last edited by: Jen_Moderator at: 08/17/2021 10:26:59Added diagnostic buffer as txt. file. |
|
8/17/2021 5:33 PM | |
Joined: 9/27/2006 Last visit: 10/16/2024 Posts: 12289 Rating: (2687)
|
Hello RHurt: The messages of the diagnostic buffer all seem to start with a failure of one o the synchronization modules o your CPUs (message 14 of 120, failure of IFMF2). Is that module still showing a fault LED? If the fiber-optic submodules fail, the primary CPU cannot send the program and the Active status of the registers to the stand-by CPU, and the primary will fail and switch control to the stand-by. his is all described in the different messages of the diagnostic buffer. What is the status of your system now, has it evolved at all? Can you replace the failed SYNCH submodule? If this is the basic cause of the CPU turnover, once replaced, the CPUs should re-synchronize and the primary will return to ccontrolling the process. https://support.industry.siemens.com/cs/ww/en/view/82478488/64854101515 Hope this helps, Daniel Chartier |
This contribution was helpful to1 thankful Users |
8/23/2021 11:12 PM | |
Joined: 9/27/2006 Last visit: 10/16/2024 Posts: 12289 Rating: (2687)
|
Hello Rogelio; How long have you had this H-system running in your plant? The H-CPUs you have appear to be v4, and they are not compatible with v6 synchronization modules that yoy can purchase today. The screenshot below shows the mechanica construction of v4 nd v6 synch modules, they are not of the same design. However, v4 synchronization modules (6ES7960-1AA04-0XA0 should still be in the spare parts list, even though they will be a bit more expensive. Considering the cost of replacing your S7-400H system with a new, v6 system, I think it would be best to inquire to your local Siemens rep about purchasing v4 synch modules... or open the Services link found at the top of this page, so you can contact Siemens Spare Parts and inquire from them (an alternative would be the Siplus sybchroniztion modules v4, 6AG1960-1AA06-7XA0, definitely on the spare parts list (remember ou need 4 identical synchroniation modules in your H-system). - Sync modules and FOC sync cables The sync modules have also been newly designed and are not compatible with the old modules. The FOC sync cables have not changed. https://support.industry.siemens.com/cs/pg/en/view/59903098 - Definition of “Replacement part” https://support.industry.siemens.com/tf/ww/en/posts/replacement-part/98728/?page=0&pageSize=10 - 6ES7414-4HR14-0AB0 status https://support.industry.siemens.com/tf/ww/en/posts/replacement-part/98728/?page=0&pageSize=10 Hope this helps, Daniel Chartier |
Last edited by: dchartier at: 08/24/2021 02:11:46Last edited by: dchartier at: 08/24/2021 02:21:59 |
|
9/3/2021 9:13 PM | |
Joined: 9/27/2006 Last visit: 10/16/2024 Posts: 12289 Rating: (2687)
|
Hello RHurt; I was able to find a manual for v4.5 of the S7-400H systems, and the following link points to the section on "Failure and replacement of a synchronization module or fiber-optic cable". I hope it can help you out. https://support.industry.siemens.com/cs/ww/en/view/1186523/26862397579 Notice the first step after the detection of a problem with the synch modules: "First, check the fiber-optic cable.", it is a source of failure that is often overlooked... Hope this helps, Daniel Chartier |
Last edited by: dchartier at: 09/03/2021 21:19:44 |
|
10/13/2021 10:01 PM | |
Joined: 8/17/2021 Last visit: 9/12/2023 Posts: 6 Rating: (0) |
Hello Chartier! I got the module 6ES7 960-1AA04-0XA0; i changed the module and i followed the procedure to change it on PLC is running the program (Rack 0). It did not work. When i told you I decided to take a good PLC module 6ES7 960-1AA04-0XA0 from another system and do some tests, i did not commend to you that the CP-443-1, on Rack 1, failed. The following activities we did on past days, when the CP 443-1 failed: 1) I put in STOP the PLC of system "B" that was in SLAVE mode and, later we turned it off. 2) Next, I turned off the PLC of system "A" that is faulty (and in STOP). We take the 6ES7 960 from system "B" and put it in "A", in the PLC in STOP. We turned on the PLC and put the selector in RUN mode and it did not work. 3) I took the 6ES7 960 from system "A" that we considered could be faulty, we put it in "B", and it worked. From the above, I now know that the 6ES7 960 module of system "A" that is in STOP is not the one that is faulty. 4) I did a test on system "B" to replicate the failure we found on system "A". I removed a fiber optic cable and the PLC that was in SLAVE mode went to STOP. 5) On one moment of thease points the CP 443-1 failed. **************** Yesterday october 12, 2021, I changed the 6ES7 960 module; the LEDs of the module blinked green and gooes off. I put the switch of PLC Rack 1, that was in STOP mode, to STOP->RUN, but it did not keep on RUN mode. I taked the 6ES7 960 module from the Rack 0 PLC (RUN MODE) and it changed on another PLC, from another system and it worked. I saved the Diagnostic Buffer of both PLCs, Rack 0, Rack 1, and CP 443-1 from Rack 1, whitch I send to you. I think now, we have a trouble with the CP 443-1. I would like you to see this Diagnostic Buffer and comment about it. Thanks very much for the attention. Rogelio Hurtado [snip] Thanks Rogelio Hurtado Díaz AttachmentDiagnostic_Buffer.txt (638 Downloads) |
Last edited by: RHurt at: 10/13/2021 22:01:46Last edited by: RHurt at: 10/13/2021 22:19:00Last edited by: RHurt at: 10/13/2021 22:25:01Last edited by: RHurt at: 10/13/2021 22:26:55Last edited by: Jen_Moderator at: 10/14/2021 09:18:05Edited text for better reading. Added diagnostic buffer as txt. file. |
|
Follow us on