> I'd try to run Progam -> Vi Metrics... to see which VI was taking up the most
> amount of time. Make sure you have increment timers inside all of your while
> loops, too. Without one of those watch icons, the while loop repeats as much
> as the CPU will allow it to.
>
I'd try the Profiler rather than VI Metrics, but I don't think the
problem is
with computation. I'd suspect it is a timeout somewhere, either on the
GPIB device or in communicating to it. You might try to Leave execution
hiliting on for the top-level diagram to see where the program is when it
pauses. This will help narrow it down, and then you can experiment. Make
sure that you are paying attention to error codes from GPIB or VISA. One
of them may already be timing out and returning a
n error that is being ignored.
Greg McKaskle