4/19/2012 4:33 AM | |
Joined: 10/7/2005 Last visit: 9/15/2024 Posts: 3020 Rating: (1054)
|
Hello vananhtuan85 my guess (your info is a bit slim on detail) is that your CPU exceeded the cycle time which would lead to a a call of OB80 and a CPU stop incaseOB80 does not exist in yourCPU. The reason for the above asumption are thatonline monitoring requires extra resources in the CPU and as such extends the cycle time. Assuming your cycle time is already close the maximum allowed cycle time, going online will now "push it over the edge". I suggest you check the following: 1.) Open "Module information" (shortcut CTRL+D),go to the scan cycle tab andsee what the max recorded scan time was (NOTE: This may also crash your CPU again as this is also online monitoringand will icnrease the cycle time). In the bottom of this window you'll also see the configured max allowed scan cycle monitoring time. 2.) Assuming you are running borderline and need to or want tochange the scan cycle monitoring time, do so by opening HWconfig, double click on the CPU and changethe value for "Scan cycle monitoring time" in the "Cycle/Clock memory tab". I hope this helps and please let us know what you'll find |
Cheers |
|
This contribution was helpful to6 thankful Users |
4/20/2012 8:03 AM | |
Posts: 69 Rating: (2) |
Just check if there is any endless loop executing in your program |
This contribution was helpful to1 thankful Users |
4/20/2012 9:37 AM | |
Joined: 3/21/2006 Last visit: 9/10/2024 Posts: 10228 Rating: (1181) |
Useful info - How to use SFC 64 w.r.t determine the Scan Cycle Time in Program?? As Darius said:
Best regards, Hristo Mihalev
|
This contribution was helpful to2 thankful Users |
Follow us on