5/14/2012 8:02 PM | |
Posts: 947 Rating: (45) |
1.Hello. see screenshot in attach 2. you have a lot of errors during the upgrade process image. Event 2 of 120: Event ID 16# 4541 STOP caused by priority class system Event: Current OB1 start event initiated by end of OB1 (free cycle) Cycle time exceeded Run time of the last cycle (ms): 401 Cause: Current OB1 start event initiated by end of OB1 (free cycle) Causing OB: Cyclic program (OB1) Causing priority class: 1 Requested OB: Timing error OB (OB80) I/O access error when updating the process image input table P area, byte access, access address: 2422 process image partition no.: 0 not user relevant(Z1): 2942 Requested OB: Program execution error OB (OB85) I/O access error when updating the process image input table P area, byte access, access address: 2421 process image partition no.: 0 not user relevant(Z1): 2942 Requested OB: Program execution error OB (OB85) Event 6 of 120: Event ID 16# 39B1 I/O access error when updating the process image input table P area, byte access, access address: 2420 process image partition no.: 0 not user relevant(Z1): 2942 Requested OB: Program execution error OB (OB85) Event 7 of 120: Event ID 16# 39B1 I/O access error when updating the process image input table P area, byte access, access address: 2393 process image partition no.: 0 not user relevant(Z1): 2942 Requested OB: Program execution error OB (OB85) . . . . . . I/O access error when transferring the process image to the output modules P area, byte access, access address: 2422 process image partition no.: 0 not user relevant(Z1): 2943 Requested OB: Program execution error OB (OB85) . . . This has to be something Delate. Probably should remove the automatic update in OB1 and make it manually, rather than for this IB, QB used PIB, PQB . . . |
This contribution was helpful to2 thankful Users |
5/15/2012 1:17 AM | |
Joined: 7/2/2008 Last visit: 9/25/2024 Posts: 928 Rating: (308)
|
HelloNisar Ahmed, If I were you I would have followed Aret's advice and check the I/O access error. I highly believe that this is your main problem. For the time being I recommend to check the call of OB 85. You can check the setting of OB85 call up by going in hardware configuration and inside CPU properties>Cycle/Clock memory make sure that the OB85 call up isOnly for incoming and outgoing events. You can read the following in SIMATIC Manager help
Best regards, H-H
|
5/26/2012 4:00 PM | |
Joined: 10/7/2005 Last visit: 9/25/2024 Posts: 3022 Rating: (1054)
|
Hello Nisar Ahmed not too sure if you've managed to fix your problem already, but in case you haven't, I'm going out on limb here and fear the following is going on in your program: The supplierwho programmed it protected his software by hardcodinga program checksum test into it to avoid any unauthorised program modifications (an OEM may for example do so to cover the warranty period of his machine). Oneexample on how this could be done can be found in How can you detect a change in the S7 user program in STEP 7 V5.5? The FC/FB in whichthis is done will also most likely be protected (via Know How protect or password)and in your case most likely contain additional"rubbish" code to loop endlessly as well as flood the Diagnostics Buffer with nuisance messages (in order to hide the true cause). As said above, I'm speculating here, but this would explain that a simple program change causes the kind of problem you have. I suggest you get in touch with the supplier of the Automation system to seek clarifcations and post your findings here. I hope this helps |
Cheers |
|