LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

DAQmx 16.1 executable won't work with earlier daq versions

Hello,

 

I have been using DAQmx for many years.  I give my customer executables to run their software.  In the past an exe built with a higher DAQmx version will work on my customer's machine with a lower DAQmx version.

 

I have DAQmx 16.1 on my development machine.  When I build an exe for my customers they get an error.  I have them upgrade to DAQmx 16.1 and that seems to solve the problem.

 

Is this the desired functionality?  Did something change in DAQmx 16.1 that doesn't allow earlier versions to play nice?

 

Thanks

Dan Shangraw, P.E.


   

0 Kudos
Message 1 of 2
(2,561 Views)

In general, when you distribute an executable built on a specific RunTimeEngine (such as LabVIEW 2016), you need to include the appropriate RunTimeEngine on the machines on which you run the Executable.  I know that there are some systems that won't run LabVIEW 2016 code on Windows 10 using the 16.0 releases of some of the RunTime routines, which is why the 16.1 versions were pushed out via the Updates -- this might also have been your problem ...

 

If, in the past, you were able to run new code using an old library, I'd say "You were lucky" (as even NI Engineers, as good as they are, aren't perfect at predicting new features that will be added in the future).  Your routines appear to be taking advantage of a "truly new" feature that wasn't covered in the old Libraries, requiring the new (current) Libraries.

 

Bob Schor

0 Kudos
Message 2 of 2
(2,514 Views)