During runtime, there is a small performance hit on the Logix controller when switching between tasks. You should avoid using tasks to organize a project's structure and instead rely more on programs and tasks to create a logical structure that resembles the process being automated. If numerous tasks are running on a controller, this increases the risk of some tasks not having the time to complete their program execution before they are triggered again and reset. Often, we hear of programmers who are new to the Logix platform who create dozens of tasks in a project (for example, one per process cell). An experienced automation professional will limit the use of tasks to less than a handful (however, certainly, there are exceptions). A typical Logix application will have one continuous task to handle the main program execution and perhaps one or two event tasks to handle special cases.
Now that we have covered the best...
