LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

save vi calling routine at runtime

Hello,

I have been trying to find a way to save a VI heirarchy at runtime. By this, I do not mean the regualar LabVIEW hierarchy. I want to know as each VI is executed in memory (minus the vi.lib stuff) and the order of the execution as it runs in memory.

Currently I can find the exe state of each vi in memory, but it will take roughly 50 ms to check each vi's state. Is there a way to allow a vi to run slower so that I can check each vi? And of course this would have to be controlled at runtime. Some vis may only take 1 ms to operate and the 50ms would not allow the time to catch it.
Any ideas would be useful! Thanks.
Kevin Shirey | CLA | Champion | Senior Project Engineer II | DMC
0 Kudos
Message 1 of 2
(2,468 Views)
> I have been trying to find a way to save a VI heirarchy at runtime. By
> this, I do not mean the regualar LabVIEW hierarchy. I want to know as
> each VI is executed in memory (minus the vi.lib stuff) and the order
> of the execution as it runs in memory.
>

Another approach which you could take would be to use the profiler. It
can save the output to a file, which you could then parse in order to
get a list of all VIs executed.

Greg McKaskle
0 Kudos
Message 2 of 2
(2,468 Views)