It worked two years without problem.
Problems started three weeks ago.
CPU goes to STOP mode when error occures.
CPU reports errors at the inputs located on rack_1 (analog inputs).
In the diagnostic buffer I can see the reason of STOP:
The strange thing about alarm: CPU reports different I/O access errors for IM 365 rack areaError wrote:STOP CAUSED BY I/O MANAGEMENT.
Yesterday it has reported
We have restart it and after a couple of hours alarm occured again.Error wrote:I/O ACCESS ERROR READING (P area addresses 448, 450,452_this is the fifth analog card at rack_1).
The last alarm is on the link http://webfile.ru/4383109Error wrote:I/O ACCESS ERROR READING (P area addresses 384,386,388,390,392,394,396,398, 432,434,436,438,440,442,444,446_these are the first and fourth analog card at rack_1).
Project is on the link http://webfile.ru/4383115
We tried to exchange PLC (same type CPU) but with no result (it was two weeks ago).
After that We exchanged MMC card, and alarm did not occur for ten days, so we thought that the problem was solved.But two days ago it happened again.
Now alarm occurs every 6-8 ours or even more often.
I have downloaded empty OB122 but CPU goes to STOP anyway. I thought it should not go to STOP if there is OB122 on it.
We also have a strange situation with a MMC card, but I will write in an another post about it.
Any suggestion is wellcome.