[PhilBot]

Originally Posted by Ether

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 best way to accidentally prevent parallelism is to run a wire from one loop into to another. The second loop won't run until the first loop is complete. If the first loop never exits, the second loop will NEVER run.

This is the most compelling reason to use local and global variables in LabVIEW. If you need to pass data between parralell loops, you can't wire it, you need to use varaibles. eg: Vision Target information, and anything that the periodic loops are using/generating that are expected to change.