Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

PROBLEMS REGARDING CPU 414-4 H REDUNDANT SYSTEM

Created by: PKG at: 9/4/2008 9:09 AM (12 Replies)

Rating (0)

Thanks 0

Result pages:: |; 1 | 2; |

13 Entries

Entries per page: 10 | all

9/4/2008 9:09 AM	Rate (0)
PKG Posts: 8 Rating: (0)	Dear, the probem is regarding the CPU 414-4 H (6ES7 414-HM14-0AB0)redundantsystem. Theexistingsystem is the set of CPU 414-4 H and there are14 no's ofET 200 station connected with cpu on profibus and communication processor cp 341-RS232c (6ES7 341-1AH01-0AE0)connected with the one of the ET 200 station for communication with yokogawa DCSworkingas amodbus slave.After downloading the program the both cpu's run with the healthy mode with run led (green) shows on both CPU'S and one of two cpu become master andanother become slave, we checked all redundant possibilties, But porblem is that after running processfor the 30 sec. to 50 sec. both cpu's goes in the faultmode and all the LED'S on both cpu's blinked (with red flashingcolour)simultaneously. System pdf are attached for your referance. Best Regards, PrashantGheewala Cotmac Electronics Sachin GIDC,Surat, Gujarat, India. Attachment SIMATIC H Station(1).pdf (400 Downloads)
PKG Posts: 8 Rating: (0)
Suggestion To thank Quote Answer

9/4/2008 9:12 AM	Rate (0)
PKG Posts: 8 Rating: (0)	PKG Dear, the probem is regarding the CPU 414-4 H (6ES7 414-HM14-0AB0)redundantsystem. Theexistingsystem is the set of CPU 414-4 H and there are14 no's ofET 200 station connected with cpu on profibus and communication processor cp 341-RS232c (6ES7 341-1AH01-0AE0)connected with the one of the ET 200 station for communication with yokogawa DCSworkingas amodbus slave.After downloading the program the both cpu's run with the healthy mode with run led (green) shows on both CPU'S and one of two cpu become master andanother become slave, we checked all redundant possibilties, But porblem is that after running processfor the 30 sec. to 50 sec. both cpu's goes in the faultmode and all the LED'S on both cpu's blinked (with red flashingcolour)simultaneously. System pdf are attached for your referance. Best Regards, PrashantGheewala Cotmac Electronics Sachin GIDC,Surat, Gujarat, India.
PKG Posts: 8 Rating: (0)
Suggestion To thank Quote Answer

9/4/2008 9:16 AM	Rate (0)
Darius Platinum Member Joined: 9/28/2005 Last visit: 11/5/2024 Posts: 2957 Rating: (242)	Hello, I've seen this behaviour before on CPU-417H system similar to yours. The only sollution I found is that you do full memory reset on both CPU's and re-download everything (including system data) to both CPU's and then try to go to run. This should help, if not, please post here diagnostic buffer.
	Best regards, Darius
Suggestion To thank Quote Answer

9/4/2008 10:49 AM	Rate (0)
dchartier Grandmaster-Expert Joined: 9/27/2006 Last visit: 11/16/2024 Posts: 12294 Rating: (2691)	Hello Prashant; What you need to do at this time is to go Online with the CPUs and open the Diagnostic buffer on each of them. This isthe best diagnostic tool that you can have. It holds the last 100 events (Run, Stop, faults) thathave happened to the CPU, with a timestamp for Sequence of Events checking, and required action suggestions. The easiest way to open the diagnostics buffer is through the HWConfig editor of Step 7, Online view; all modules will be shown, with a symbol indicating their status.The CPUs should show a red X over them, indicating failure. Double-clicking on the failed CPUs will open the diagnostic buffer that is dedicated to them. Try examining the different entries in the buffer to establish the cause of the Stop mmode and LED affectation. The contents of theDiagnostic buffer can be saved as text, and can then be posted here so we can have a look, and perhaps provide hints for a solution. Hope this helps, Daniel Chartier

Suggestion To thank Quote Answer

9/4/2008 12:04 PM	Rate (0)
Darius Platinum Member Joined: 9/28/2005 Last visit: 11/5/2024 Posts: 2957 Rating: (242)	dchartier What you need to do at this time is to go Online with the CPUs and open the Diagnostic buffer on each of them. I'm sure that diagnostic buffer will say something about inconsistent configuration. As I said before I had this behavior on system like that and diagnostic buffer was full of entries about inconsistent configuration.
	Best regards, Darius
Suggestion To thank Quote Answer

9/5/2008 7:55 AM	Rate (0)
PKG Posts: 8 Rating: (0)	As per different comment, whenever the cpu 414 h goes in to the fault mode the communication has breakdown between pc and plc and so, we can't able seen the events in the diagnostic buffer due to communication breakdownat the moment of fault. Prashant Gheewala Cotmac Electronics Sachin GIDC, Surat.
PKG Posts: 8 Rating: (0)
Suggestion To thank Quote Answer

9/5/2008 8:08 AM	Rate (0)
Darius Platinum Member Joined: 9/28/2005 Last visit: 11/5/2024 Posts: 2957 Rating: (242)	Hi, Have you tried to vlear memory and reload everything again as I suggested ?
	Best regards, Darius
Suggestion To thank Quote Answer

9/5/2008 8:15 AM	Rate (0)
dchartier Grandmaster-Expert Joined: 9/27/2006 Last visit: 11/16/2024 Posts: 12294 Rating: (2691)	Hello Prashant; The diagnostic buffer is retentive; whenever communications are re-established, go to the diagnostic buffer to gather information on your problem. One of the messages you will get is "Missing or required OB: " followed by an OB number. These are diagnostic OBs; as their name implies they are called by the operating system whenever the system detects a condition that requires diagnostics. If they are not present in the CPU memory, the PLC goes to stop mode and shows SF LED. You can find informatiojn o the different OBs in the Online help of Step 7, or in the manual Standard and System Functions (in Simatic-->Documentation). If these OBsare present in PLC memory (even without any programming inside) then whenever any critical condition arises the CPU calls the required OB, logs the diagnostic information to the diagnostic buffer and resumes the processing whjere it left off. The SF LED lights up, signaling a fault, but THE CPU NO LONGER GOES TO STOP. Cycle time might be extended, but the working portions of your program are still being processed. So if you see this message, open the program's Blocks folder, insert a New Block, select OB, and write in the number of the OB signaled in the diagnostic buffer. Do no place any network in the OB for the moment. Save and download to the PLC. Then, open the diagnostic buffer again: you will find much more info on your problem. Hope this helps, Daniel; Chartier

Suggestion To thank Quote Answer

9/5/2008 8:36 AM	Rate (0)
Aret Posts: 2348 Rating: (264)	Please check also your firmware version (module information->General). For your system it'd betterifevrsionwouldbethelastone-it'savaiblehere: http://support.automation.siemens.com/WW/view/en/6741018 PS. Please note - perhaps you'llneedFlashcardformakingOSupdate.
Aret Posts: 2348 Rating: (264)
Suggestion To thank Quote Answer

9/5/2008 8:56 AM	Rate (0)
Darius Platinum Member Joined: 9/28/2005 Last visit: 11/5/2024 Posts: 2957 Rating: (242)	dchartier . One of the messages you will get is "Missing or required OB: " followed by an OB number. These are diagnostic OBs; as their name implies they are called by the operating system whenever the system detects a condition that requires diagnostics. If they are not present in the CPU memory, the PLC goes to stop mode and shows SF LED. I may be wrong, but as I remember if you have diagnostic buffer entry something like "inconsistent configuration" PLC goes to STOP anyway. No OB will help. Maybe I'm wrong. I had this error on H system and the only way was to compeltely clear FLASH card and reload everything from scratch.
	Best regards, Darius
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on