LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Calling VIs by older exe files

can an exe file build in older lab view version call the latest VIs
0 Kudos
Message 1 of 6
(2,517 Views)
Your question is not clear. What do you mean by calling the "latest VIs"? Are you referring to, for example, an application that was built in LabVIEW 7.1 trying to dynamically load a VI that was created with LabVIEW 2009? Or, are you referring to calling VIs that were compiled into a DLL that was created with, say, LabVIEW 2009?
0 Kudos
Message 2 of 6
(2,516 Views)

hi riaz,

 ofcourse  you can open the exes build with older labview version,(but only thing is that you should have proper run time engine to open that exe... ) from new labview version VI through the system exec.vi.

 

 

T hanks and regards,

srikrishnaNF

Regards,
Srikrishna


0 Kudos
Message 3 of 6
(2,512 Views)

Dear Sir;

 

I am stuck up in a problem. I have a very huge testing software  written in lab view 4.0 in Win 98 and Ni daq ver 4.8.5. Lab view 4.0 accesses daq (ISA based) through CIN. Similarly it also had an ISA GPIB card. Now as the ISA has been obsoleted and i want to upgrade to PCI cards. I have used the same image of the OS system with the same LV4.0 folder and all. The software was compiled and an exe files was built in LV 4.0. This exe files calls various VIs placed in different folders during run time. Now after upgrading to PCI cards, the CINs and the lower level VIs are not linking up with the driver. I have tried various verisons of No daq from 4.9.2, 5.0.3, 5.0.5, 6.0, 6.1 6.5.0, 6.7 etc. driver versions like 5.0 are successfully installed and configure the device however, in lab view VIs the broken arrows are shown giving  the error of missing CIN or fatal errors in various cases. Now i have an idea that if i maintain the exe file and i just upgrade the standalone VIs in Lab view 7.1 or later would it be possible that the exe built in 4.0 can dynamically call / load the VIs update din Lab View 7.1 or later. Similar case for GPIB. 

 

Submitted for your kind help.

Thanks 

0 Kudos
Message 4 of 6
(2,506 Views)

ear Sir;

 

I am stuck up in a problem. I have a very huge testing software  written in lab view 4.0 in Win 98 and Ni daq ver 4.8.5. Lab view 4.0 accesses daq (ISA based) through CIN. Similarly it also had an ISA GPIB card. Now as the ISA has been obsoleted and i want to upgrade to PCI cards. I have used the same image of the OS system with the same LV4.0 folder and all. The software was compiled and an exe files was built in LV 4.0. This exe files calls various VIs placed in different folders during run time. Now after upgrading to PCI cards, the CINs and the lower level VIs are not linking up with the driver. I have tried various verisons of No daq from 4.9.2, 5.0.3, 5.0.5, 6.0, 6.1 6.5.0, 6.7 etc. driver versions like 5.0 are successfully installed and configure the device however, in lab view VIs the broken arrows are shown giving  the error of missing CIN or fatal errors in various cases. Now i have an idea that if i maintain the exe file and i just upgrade the standalone VIs in Lab view 7.1 or later would it be possible that the exe built in 4.0 can dynamically call / load the VIs update din Lab View 7.1 or later. Similar case for GPIB. 

 

Submitted for your kind help.

Thanks 

0 Kudos
Message 5 of 6
(2,498 Views)

Hi Riaz,

 

I don't believe that your exe will be able to call the newer VIs since it won't be able to use the newer Run-Time engine to call the newer VIs.  Is there a reason that you don't want to upgrade the software in addition to the hardware?

Jared S.
Applications Engineering
National Instruments
0 Kudos
Message 6 of 6
(2,462 Views)