[Greg McKaskle]

I looked at and ran some of your code, and it seems fine to me. I didn't see the CPU usage being more than a few percent on the computer when running the popup panel for the test. I didn't run it on the cRIO or the simulator.

The general idea is to give you a way to test out a mechanism in order to validate it after work or after a match. So this seems like a good example.

As for the question -- a static VI is one that is known about at compile time, as opposed to a dynamically called VI. At least that is what I assume you are asking about. Do you have a specific location in the environment that is calling it static and confusing you?

Greg McKaskle