Building executable without PCI connector

[M. Bobby]

Hello,

I have developed a program that makes use of DAQ Assistant to send commands to a PCI-6221 card inside a desktop computer.  I have used MAX to assign the device to the name 'Dev2', and now I wish to build an executable to run the program on a separate desktop computer, that also has a PCI-6221 card. 

However, I have to use a laptop to build the executable (the first desktop does not have full version of Labview), and when I open the program on the laptop, the Physical Channel remains the same (Dev2/ao0 for example) but the Device Type changes from PCI-6221 to USB-6009.  I can still build the program without errors, but when I run the executable on the desktop without Labview (only Run-Time Engine), there are problems with the voltages applied (although there are no Labview errors with running the executable).  I have changed the Physical Channel of the second PCI-6221 to Dev2 as well, but there are still issues. 

Is there a way to change the Device Type on the laptop to PCI-6221 without adding a PCI-6221 card, or should the physical channel be sufficient, and there is some other issue. 

The program initially ran correctly on the desktop, and only has issues with the executable. 

Thank you very much for any advice.

[Ali M]

Hello M.Bobby,

It may be advantageous to include code that will detect all devices on the deployment machine, determine which one is the correct device, and then output it's DAQmx resource name for use within the exectable. I have included a similar example in the link provided below:

1. Programmatically Determine DAQmx Device Name when Deploying Executables: http://decibel.ni.com/content/docs/DOC-10014

Best regards,

Ali M

Applications Engineer

National Instruments

[rolfk]

Besides what Ali M said, you can create DAQmx simulated devices in NI-MAX. Go with Devices and Interfaces->NI-DAQmx Devices and right click on it. Then in the popup menu select Create NI DAQmx Simulated Device.

But the way you should actually make this in a normal application is to have somewhere a configuration section which allows you to set the device and channels to use for you application and then save those settings in an INI file or similar, loading this information on every startup of the application.