Quote:
Originally Posted by Greg McKaskle
Unless you do something to prevent parallelism, LV is all about the parallelism. During Autonomous, the Auto Independent VI is running its code, the vision code is parallel and the loop is running -- the code within may be disabled. The periodic tasks are always running, even when disabled. Robot Main is running. Start Communications is running.
|
Assuming our new-to-LabVIEW programmers try to stay within the guidelines for proper use of the framework, and don't try to get too "clever", is there anything they could do inadvertently to "prevent parallelism"? I guess what I'm asking is, is there a short list of common LabVIEW programming errors (particularly for newcomers) that I should warn them about?
The answer to the following question is probably obvious to a LabVIEW programmer (which I admittedly am not), but when you say "The periodic tasks are always running, even when disabled" ... why would a task continue running when it is "disabled" ? Maybe the word has a different meaning in this context?
~