LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Can I use labview 2015 and 2019 DAQmx functions at the same time?

Solved!
Go to solution

I am using the 2019 version of Labview to create a new program.
The old program is made of Labview 2015, so if i want to make modifications, Labview 2015 is required.
DAQmx 2019 version does not support Labview 2015
Labview 2019 is not supported when using DAQmx 2018 version.
Is there a way to use both without using VMware?

0 Kudos
Message 1 of 7
(2,234 Views)

You can open files created in 2015 with 2018. It works just fine.

Message 2 of 7
(2,202 Views)

Why don't you just convert the LabVIEW 2015 code up to LabVIEW 2019?

 

You say "if i want to make modifications, LabVIEW 2015 is required."  Why do you say that?  There might a valid reason, you need to, but otherwise I would recommend upgrading your code.

Message 3 of 7
(2,190 Views)

I am in charge of program maintenance and modify many types of programs.
PCs with older programs do not have a Labview 2019 license.
That's why we have to use Labview 2015 as it is.

0 Kudos
Message 4 of 7
(2,165 Views)

Are you saying you run all your programs from source code in the IDE on every computer? Unless you have a site license that would seem a very expensive solution.

But more importantly your operator could by accident (or not) change the program and totally nullify any test results in an untraceable manner. You really always should create executables for operator stations and then the LabVIEW version mostly is just a development decision (unless you want to run a program on some dinosaur computer with fully unsupported OS).

Rolf Kalbermatter
My Blog
Message 5 of 7
(2,160 Views)

Hi Kwon,

 

the answer to the question in your topic line is no.

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 6 of 7
(2,157 Views)
Solution
Accepted by topic author RevolutionKwon

@RevolutionKwon wrote:

Is there a way to use both without using VMware?


snarky answer: Sure.  Use Virtualbox.

 

To be honest, you really should be working with a VM anyways.  Having a VM for each project is not out of the question, depending on industry/business requirements.  That is the only real way to lock down your drivers, support software, support libraries, etc. without interfering with your other projects.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 7 of 7
(2,142 Views)