LabWindows CVI 9.0 very slow

[Leonhard]

To the community:

We are developing some test with LabWindowsCVI 9.0 + DAQmx + NI-6229 + NI-6255 + NI-6525 on Windows XP.

After a couple of days, when the DataAcquisiton routines we done (reading the channels), when you compile to debuggable_executable and try to debug step by step, some C developed functions running cycles on arrays with acquired data run extremelly slow. The funny thing is that when I compiled it for executable release, the execution speed was ok.

This behavior happens after the Data Acquisition processing was finished on an AI channel @ 125000 Samples, the next function, which looks for peak of the waveform and so on are the ones that are running painfully slow.

Did I modify by accident any setting in the debugger ?

Please advice.

[StevieZ]

Leonhard,

Try isolating the issue to the analysis functions, this seems unrelated to DAQmx. If you were to perform the same peak of waveform function on a generated array does the debug execution still run "extremely slow"? In addition, if instead of debugging step-by-step you compile it in debug mode and run it without breakpoints is it still slow?

Regards,

Steven Zittrower

Applications Engineer

National Instruments

http://www.ni.com/support

[Leonhard]

Hi Steven, thanks for answering...

The answer is yes. When I compile as debbugable and run it without breakpoints is extremelly slow. Let me try to isolate to the analysis functions. The funny thing is that this functions are used in another three projects in other three computers, and compiles, runs, debbugs much faster.

Should I try to repair our installation of CVI 9.0 ?

[StevieZ]

Leonhard,

If you want to go the route of repairing CVI you can. If it runs well on other computers then it may be an issue with settings, a repair should reset those to their defaults.

Regards,

Steven Zittrower

Applications Engineer

National Instruments

http://www.ni.com/support

[LuisG]

You might also want to make sure that you currently don't have watch points associated with this workspace. If you do, this could cause a noticeable slowdown when debugging, depending on the type of watch point(s) you have.

Luis