Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

6ES7416-3XL00-0AB0 INTF led

Created by: AsterPD at: 3/15/2024 8:27 AM (4 Replies)

Rating (0)

Thanks 0

5 Entries

3/15/2024 8:27 AM	Rate (0)
AsterPD Member Joined: 6/5/2015 Last visit: 10/25/2024 Posts: 1 Rating: (0)	Hello, this is my first time consulting here, forgive me if I don't do it right. Two days ago, a CPU 6ES7416-3XL00-0AB0 started to have problems. Randomly, it goes into STOP mode and the INTF LED lights up. When I enter the diagnostic buffer, it tells me that OB1 is generating the fault event, but it doesn't seem to be a programming issue because it doesn't call OB85, nor does it indicate the fault point in the program. It directly calls OB80, which is declared in the program, but still the PLC goes into stop (I assume because the problem persists). To restart it, a hot start is necessary, and the same thing happens: it runs for a whole day without problems until it fails again... Do you know what it could be or has anyone experienced this before? Thank you. ------------------------------------------------------------------------------------------ Split from S7-400 INTF fault. Attachment Diagnose_AAU.txt (458 Downloads)
	Last edited by: Jen_Moderator at: 03/18/2024 08:22:03 New subject after splitting Last edited by: Asterio at: 03/20/2024 07:48:39
Suggestion To thank Quote Answer

3/20/2024 4:03 PM	Rate (0)
Ayman Elotaify Platinum Member Joined: 5/28/2008 Last visit: 11/6/2024 Posts: 4516 Rating: (839)	Hello, In diagnostic buffer, Event 3, it is mentioned that cycle time exceeded, and last cycle execution time is 151 ms. And as per the attached picture, the default setting is 150 ms. So, in case exceeding the 150 ms, the CPU will go to STOP mode. So, you can increase this setting in the HW config. and tell us if it will solve your problem. Attachment 416.jpg (534 Downloads)
	Ayman Elotaify
Suggestion To thank Quote Answer

4/15/2024 4:51 AM	Rate (0)
Deyoung Joined: 2/28/2023 Last visit: 11/3/2024 Posts: 40 Rating: (1)	Ayman Elotaify Hello, In diagnostic buffer, Event 3, it is mentioned that cycle time exceeded, and last cycle execution time is 151 ms. And as per the attached picture, the default setting is 150 ms. So, in case exceeding the 150 ms, the CPU will go to STOP mode. So, you can increase this setting in the HW config. and tell us if it will solve your problem. Agree with Ayman But before changing the parameter settings, it is a coding/programming ethics to ask the question What has changed? Cheers Dyoung
	Cheers. Dyoung Is it resourceful? You can rate it if you wish.
Suggestion To thank Quote Answer

4/15/2024 6:40 AM	Rate (0)
Michael K Gold Member Joined: 9/3/2008 Last visit: 11/8/2024 Posts: 928 Rating: (163)	Hi, Agree with Deyoung. Did you add new program/blocks that added to cycle execution time? O increased for loops? I have also seen a case where the cpu were suddenly flooded with diag interrupts from a distr i/o node that slowed down the ob1 and made it run longer than the max cycle exec time. /Michael
	Michael
Suggestion To thank Quote Answer

4/15/2024 7:03 AM	Rate (0)
Ayman Elotaify Platinum Member Joined: 5/28/2008 Last visit: 11/6/2024 Posts: 4516 Rating: (839)	Hello again, I am here again just to add my experience here for a similar problem I faced a few years ago! Actually, it happened due to an expansion in IOs and for sure an expansion in programming which leads to huge programming code added to the CPU. The problem was that that CPU is very slow compared to recent CPUs. Please note the difference between the processing times of this CPU and recent CPU 416 "6ES7416-5HS06-0AB0" for instance. So extra code will take longer processing time in this old CPU.
	Ayman Elotaify
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on