9/25/2006 10:42 AM | |
Posts: 2348 Rating: (264) |
Hi all.
About a week ago my CPU went to stop mode with error 494D. I belive that IO error means not signal modules (i have all OBs needed for error handling), but internal communication. After that CPU doesn't start until power off. Siemens support said, that this problem caused by defective module and/or backplane bus. Futher information is not avaiblу so they adviced to check every module. The problem is - i can't check every module (2 racks ~approx. 30 modules). Problem first appeared after 2 weeks of uninterrupted work - so it would take more than a year to check out what module should be removed. I have 7-9 days only because system must be started in that time and we can't also order new modules due to delivery time.
In attachement you can see station confuguration and diagnostic buffer.
AttachmentDiagnose_GA17_2006_09_17.zip (472 Downloads) |
9/29/2006 3:37 PM | |
Posts: 198 Rating: (17) |
can you please check your obs, if you made a prog. error in an ob it will stop cpu make them all empty if you can. i dont know what else can be. |
10/2/2006 6:44 AM | |
Posts: 2348 Rating: (264) |
I have all OBs, but in fact no OB is called on STOP. |
8/14/2014 10:35 AM | |
Joined: 7/25/2011 Last visit: 1/13/2020 Posts: 9 Rating: (0) |
Hi all, I had thesame issue and my CPU went to stop mode cause by I/O error ID 494D. What was the cause of this error? |
8/18/2014 5:13 PM | |
Posts: 2348 Rating: (264)
|
Cause unknown, was solved by replacing CPU. Sorry, cant remember details - it was nearly 10 years ago |
Follow us on