From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Including the RunTime Engine in a build

Once a year (or is it only once?) you'll need to open MAX to agree to a license in order to use it, else DAQmx might be problematic. You'll just need to click agree and continue, it sounds like that's the issue here.

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 31 of 38
(1,188 Views)

@Yamaeda wrote:

Once a year (or is it only once?) you'll need to open MAX to agree to a license in order to use it, else DAQmx might be problematic. You'll just need to click agree and continue, it sounds like that's the issue here.

/Y


Pretty sure I used to get it each and every time I started it. But that was in times of LV7. Hopefully it improved. Or I could be wrong...

 

Anyway, probably not related to OP's problem.

0 Kudos
Message 32 of 38
(1,182 Views)

OK.  I went to my old files on the server in my old shop and found 'configData2' NI Configuration file.  I moved it on to the server at the shop that is having issues.  I asked the end user to move that file on to the computer with the M 2345 front end and the PCI 6221 card.  I am assuming if he runs that config file, it will do what he needs?

He confirmed today that the other application I built that requires the RunTime Engine but not the DAQmx config DOES WORK!!! 

So, anything else I need to know to run the config file would be greatly appreciated.

Ron

Message 33 of 38
(1,174 Views)

Or will he need to download and run the DAQmx drivers file first?

0 Kudos
Message 34 of 38
(1,171 Views)

That config file needs to be imported in MAX. There is an import menu function to do this.

 

IIRC, there is a LabVIEW function for it as well, but that would require code change and recompiling.

 

This can be automated, by including the config file in the installer, doing it manually is just another route.

 

Feels like we're getting somewhere...

0 Kudos
Message 35 of 38
(1,153 Views)

In the Installer you can "Import MAX file" and attach this file for automatic installation as part of the program.

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 36 of 38
(1,148 Views)

To All,

It is nerve racking to trouble shoot these type of problems long distance, but I am happy to reply that we have a successful install!  The main problem appears to have been when the old computer died, Corporate IT moved the entire hard drive to a new computer.  In doing so, the PCI 6221 driver was corrupted.  I never could get an Installer to do the job.  It worked for the RunTime Engine, but not for the niconfig files.  The end user finally downloaded the correct NIMAX for LabVIEW 2015 and this program found the corrupted driver and replaced it!  Up and running!  Thanks to all for your advice and comments.  I would very much like to build a successful Installer file, but without someone walking me through each of the option selections, I don't think I'll ever get there.

0 Kudos
Message 37 of 38
(1,114 Views)

@Coryman wrote:

I would very much like to build a successful Installer file, but without someone walking me through each of the option selections, I don't think I'll ever get there.


I think it mostly just looks intimidating. I'd say the help would give information about most options (did not test that theory), but often the defaults are OK. But feel free to ask if you want details. 

0 Kudos
Message 38 of 38
(1,097 Views)