LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Indentical runtime engines required?

I am having some issues with getting an exe I just built to run on one of our target machines. This program is an upgrade to an existing one (complete rewrite), but were made using LabVIEW 2015. When I try running it on the target it comes up saying it is missing resources, that it can't open the front panels of DAQmx Create Channel(DI Digital Input).vi and DAQmx Create Channel(DO-Digital Output).vi. The program runs fine when on the development machine, I've tried a couple of things, explicitly including those to DAQmx vis in the project, rather than them being in Dependencies, so that I could change the "remove" front panel, but that seems to cause other problems, where I get the message that the main vi won't run and it "needs the full development system to fix" so I have rolled that change back. Why it needs the front panel of a polymorphic DAQmx vi that never has its front panel show is beyond me. 

 

After all that, my question is, does the target need the identical version of LabVIEW runtime, my dev machine is 2015sp3 I just noticed the target is 2015sp1.

 

 

One last thing, the target only has the Runtime, MAX etc., where as my dev machine has 2015, 2016 and 2017 installed.

 

 

As usual, thanks in advance.

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 1 of 3
(2,675 Views)

Hi Putnam,

 

Do you have a newer version of DAQmx on your development machine, than the DAQmx runtime on the target machine? If yes, you may need to upgrade the DAQmx runtime. If you can't do that, maybe you can create a virtual machine on your development computer with LabVIEW 2015 and the same version of DAQmx drivers as on your target machine (15.0?)

 

Can you create a full installer for your application and include recommended installers?

0 Kudos
Message 2 of 3
(2,667 Views)

LOL. Sorry, laughing at my situation here. I will try and get IT to upgrade the target machine. I suspect it is because of my machine having 2015 - 2017 installed (I protested, since, except for people trying out the new features, most actual dev work is being done in 2015), meaning multiple newer versions of everything. Unfortunately all our machines are locked down, none of us has full admin rights, so running installers, VM, etc., aren't feasible. I will see about building an installer, might get IT to run that. Of course, if the building of an installer requires using the original media, well, while I do have that (my personal company has all versions back to 2.5.2) I am not authorized to plug in any of my "unapproved" USB, and these machines, like so many now, don't have optical drives.

 

Thanks,

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 3 of 3
(2,654 Views)