installed program running slowly

[gpib_user]

I have an application using 2 NI DAQ 6230 cards that works perfect on my development machine. However, when I build the exec and use installer , the program runs very slowly on the new machine. I took it so far as to completely install labview on the target machine and  compiled shared library / source distribution and tried running it again with no luck. The target machine is faster / newer than my development machine. I know it seems to point to a hardware isssue - but I truly believe it is a labview issue. Is it possible some links are broken somewhere. I do not get any runtime errors - the application is just unusable.

[RobBoyer]

What version of LabVIEW are you using?  If you're using 7.0 or earlier, code running on a machine with a multi-core processor may actually run slower.  Is the target machine multi-core and the development not?  I think 7.0 was the cutoff, because I think I remember reading that version 7.1 is the first version that can make use of a multi-core processor.

On the other hand, if the difference is that drastic maybe that doesn't account for everything.  Anyway, if this theory does match your situation, you can try setting the affinity on the LabVIEW.exe process in the task manager.  Right-click it, select Set Affinity and deselect all CPUs except for 0.

Hope that helps,

Rob

[gpib_user]

I am running 8.5 full development pkg.

[David_B]

Can you provide some additional information about your two setups (HW, SW, OS, etc)?  Can you also provide additional information about your program (does it interface with HW, what is it's main function, etc.)?

Something you may want to try is running the executable on another system (that does not have LabVIEW installed) that you could use to test your application in order to isolate the problem to either the computer or your program.

Generally this occurs when the target machine has either a slower video card, CPU, or less memory than the development machine; so your situation is a bit unique.

Regards,

[TroyK]

I've seen this problem before when the wrong version of DAQmx is installed on the target machine.

It still works, just very slowly.

Check what version of DAQmx is installed on the development pc that you compiled the application on and compare it to the version of DAQmx on the target pc.

[gpib_user]

Thanks for you replies. I initially suspected daqmx however I installed the latest version from ni on both machines. I am using 2 6230 daq cards to drive and read analog setpoint on an MKS flow controller and use dig i/o to control some solenoid valves via ss relays. I run xp pro on both my development and target machine , both employ the same video card (matrox dvi) and in fact the target machine has a faster cpu and more memory. I have to guess it is not a hardware issue. The development machine runs fine even if I created an executable and istall it and run it from the development machine. If I install this same exec (using installer) on the target machine it just runs very slowly - like it is using way too much cpu time or memory - though no other apps are running simulateously on the target machine - it is pretty much dedicated to run this setup.

[TroyK]

Have you tried completely removing all NI software from the target machine then reinstalling your application and correct level drivers?

What happened with me was that the user installed the hardware and drivers that came with the hardware (which were old).
For some reason the drivers weren't replaced properly when I tried to update DAQmx.

I had to completely uninstall all NI software on the target machine for it to work.

The other time I've seen similar problems is when I updated the DAQmx drivers on my development machine but included a pre-update exe in an installer.

All the vis in the application should be mass compiled after new driver versions are installed. Then the application recompiled to a fresh exe with the updated vis.
Then the installer built with the up to date exe.