Debug vs no debug mode

[pluccio]

My VI reads a waveform from oscilloscope. If I work in debug the results are OK, in no debug mode NO.
SYSTEM: LabVIEW v6.1, Windows 2000, PCI-GPIB

[shoneill]

If you mean by "debug" that the highlighting is switched on (Data flow shown graphically as it happens) then your problem is most likely timing.

LabVIEW operates many operations in parallel (or almost at least) unless there's data dependency between functions. If one function relies on another, but they aren't linked by data flow, it can happen that they're executed in the wrong order without highlighting. WITH highlighting the execution is much slower, and the actual order of execution may be different.

Try linking all functions which are interconnected with data (The error clusters are great for this).

Shane.

[Bob_Y.]

It could also be timing in another sense. You could need to have some delay between sending commands out and reading data back. Running it with Highlight Execution turned on could be giving it enough of a delay to make it all work out. You can try adding delay between your communication calls and see if that helps. If this is the solution, you might want to make it a subVI as you will probably use it a lot.