Can I get a 'timetable' of what labview does when it runs the program?

[muks]

What exactly are you not understanding?

[Norbert_B]

The NI Spy logs activities of interfaces like VISA. This does not list any information about what your application internally does. So this is definetly not the correct tool for your request.

Try to stick on Desktop Trace Execution Toolkit or, even applicable, the highlight mode within LV. Remember that the highlight mode completely messes up timing behavior and parallelism of your VI.

Another thing is that you can write your own logging mechanism for execution tracing....

hope this helps,

Norbert 

[Ben]

---

ssteel wrote:

How do I use NI Spy to get the time taken for each sub vi and the order it does them in?Iv tried running the program whilst the ni spy is open, but i dont under stand the results?

Cheers 

---

NI Spy will og the serial port activity, not the code. THat could be done using the trace execution toolkit I mentioned earlier.

From looking at your other thread your issue is the file I/O bottleneck. LabVIEW has to complete everything in a loop before it can start another pass. If your file I/O starts taking longer (to create the file write it close it) the loop will slow down. Follow-up on your other thread and look into the producer consumer design pttaern. THat pattern un-couples the speed of your file I/O from your hardware I/O.

If you don't believe me, then search this forum for the word "benchmark" to see how people have timed operations in LV.

Reader's Digest version:

Drop Get ms timer values at strategic points in your code and then do some subtration to figure out how long each step took.

Anecdotal example:

There are typically two things that people do with a computer that take a long time and we accept it. Connecting to a web-site or opening a file. Why are both slow? THey both require getting data through a slow port (ethernet or disk drive).

Ben