Timing Tool

[Greg McKaskle]

I've attached a VI that may give some insight into the timing of LV-based applications. Perhaps something like this will find its way into the default framework next year.


Drop the subVI into the teleop and into vision or periodic loops. You may want to wire a Call Name into the subVI, but if you do not, it will use the calling VI's name.

While running the robot code in development mode, you can open the subVI panel and look at the display of names and deltas. Hopefully it will give some insight into how often various portions of your code are being run. If the CPU is overtaxed, look for things you can increase the loop timing on. If the value for teleop is much larger than 20, it indicates an issue with the amount of time teleop is taking to run.

This will not solve any issues on its own, but it should be lightweight enough to leave in your code and will help you keep tabs on timings as code changes are made.

Greg McKaskle

[Ether]

Thanks Greg. I think this will be quite useful as both a teaching tool and a debugging tool.


~

[Ziaholic]

Thanks Greg. I'm always grateful for a nice new tool.

(and thanks for that "s" at the end of your filename ... saving us from a rename)