Changing NI-DAQmx Hardware When Using an Executable Built in LabVIEW

Updated Dec 12, 2019

Reported In


  • LabVIEW
  • LabVIEW Application Builder Module


  • NI-DAQmx

Issue Details

  • I want to use different NI hardware than what my executable is currently using with a hardcoded value. Is this possible?
  • I have an executable that is built with LabVIEW that uses NI-DAQmx hardware for data acquisition. I no longer have the project files for the executable. I have a different product that I would like to use instead of the hardware the executable was built for. Is this possible?


You can change the NI-DAQmx hardware that your executable is using if the new hardware uses has the same features that the executable is using with the old hardware. For example an analog input module may be able to be replaced by another analog input module, but not a module that only has analog outputs. You can change the resource used by your executable by giving the new module the same name as the old module in NI-MAX. If there is no resource in NI-MAX with the same name, an error will appear when running the executable with the name of the resource the task is attempting to access.

Additional Information

It is best practice to create a physical channel control with a default value instead of hardcoding the physical channel name within a LabVIEW executable. This allows the channel to be more easily changed in the future.