416-2XK01-0AB0 INTF

Good day! I have facing this problem in our system the CPU 416-2DP having INTF alarm (LED red lit) when i open the hardware dianostic buffer there are several errors enlisted the very first error i found is I/O access error when updating the process image and some errors are I/O access error in the nth read access (n>1) then the system CPU stop with error in diagnostic window and stating that STOP by priority class system.

Can anyone help me to interpret this error is it my CPU already faulty and needs to be upgraded to new version since this CPU is already out of the rack in the market...TIA

lowprofile69

Good day! I have facing this problem in our system the CPU 416-2DP having INTF alarm (LED red lit) when i open the hardware dianostic buffer there are several errors enlisted the very first error i found is I/O access error when updating the process image and some errors are I/O access error in the nth read access (n>1) then the system CPU stop with error in diagnostic window and stating that STOP by priority class system.

Can anyone help me to interpret this error is it my CPU already faulty and needs to be upgraded to new version since this CPU is already out of the rack in the market...TIA

Hi,

The INTF led can be on for many reasons. Unless you save(and upload) the diagnostic buffer we can not tell you the reason(s).

Have a look at this manual for info about your hardware and LED statuses:

https://support.industry.siemens.com/cs/us/en/view/19538001

I hope I could help!

Hello MicroMan

In the diagnostic buffer event it was saying that CPU STOP caused by priority class system and before the CPU stop there are several error came in the diagnostic buffer as you can see in the attached image i took several photo of the event but cant upload all of it here.

Hi,

If you click on the "save as" button when you see the attached screen, you can save the content into a text file. The text file contain a lot of information allow us to see what is going on. So, go online, read the buffer, then save it as text file, zip it and upload it.

That is the most efficient way of identify issues. Easy!

hello

Thanks microman will do as you said will get ol and will save all the data from the diagnostic buffer.

Today our machine stopped again with different error in the diagnostic buffer  will save this error and will upload it here what i don't understand is that every time it stop there are different error coming in the diagnostic buffer and it is difficult from where we can focus to solve the problem.

Hello 

Here is the diagnostic txt that our CPU having TIA 

Hi,

"Event 68 of 120:  Event ID 16# 39C4
Distributed I/Os: station Failure
Address of the affected DP slave: station number:   51"

same with address 9 and  6 also 52.

That is causing a lot of IO access error. I did not find indication of CPU stop. The Diag-buffer entries were overwritten with the high number of new messages. Without this it is a guessing game, but investigate the reason of these Remote IO racks dropping off. Maybe the lot of IO access error cause the CPU stop (maybe trough "watchdog" of OB1).

Hello

I was not able to save the txt file of the previous alarm of the CPU showing the INTF that was already overwritten by the new alarm that came today, i will conduct again the communication test for the profibus and see the quality of the communication between this several stations i was suspecting again the profibus connection having problem thats why it show sometimes the rack failure error.  I'll keep you updated after i test the communication between the stations.

Thanks for assistance