LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Exe problem

Hi everyone,

I have an application in which I call vis with "open vi Reference" with type specifier. All vis have same connector pane. Some have DAQ functions and some of them does not. At start of application there is option to select which Vis needs to be called.When I run the code, everything is fine.

When I run the exe with vis which does not include DAQmx functions it runs fine , but gives out "Error 1003" with vis containing Daqmx functions.

I read about error 1003, It says it happens when vi is not getting loaded properly.

Either it has broken arrow or it is not able to find some of its sub vis.I think it is related to DAQmx functions.

Because before giving out error it tries to find something from DAQmx library..I had taken printscreen ..So found out.

I am building exe (with DAQmx function) for the first time. Am I missing something?

Gaurav k
CLD Certified !!!!!
Do not forget to Mark solution and to give Kudo if problem is solved.
0 Kudos
Message 1 of 8
(3,223 Views)

I think this might be due to vi missed during the creation of Executable. Check which VI is the LV searches during the Run of Exe and check it whether is it in the correct folder and included in the Executable creation.

 

Smiley Wink

-----

The best solution is the one you find it by yourself
0 Kudos
Message 2 of 8
(3,215 Views)

Hi Br.anand,

All vis are included. Did mass compile as well. No error.

 

Gaurav k
CLD Certified !!!!!
Do not forget to Mark solution and to give Kudo if problem is solved.
0 Kudos
Message 3 of 8
(3,210 Views)

What is the exact code you use to open the VI.

I assume the VI is not included in the build (or it's in a different location).

Is there a specific reason to use the Open VI Reference over a normal VI?

 

Ton

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
Message 4 of 8
(3,200 Views)

Sorry...Vis are not included in "Always include" section while exe.they are kept in different folder. As I said the path is correct.

I had used indicator and checked it. 

"Is there a specific reason to use the Open VI Reference over a normal VI?">>> Its not my code,some one did it long way back in LV6.

I am not suppose to change anything.Smiley Sad

But its not problem of thet. Can yop tell me is there any different procedure to make exe when you are using DAQmx functions?

Gaurav k
CLD Certified !!!!!
Do not forget to Mark solution and to give Kudo if problem is solved.
0 Kudos
Message 5 of 8
(3,194 Views)

No there is no difference to create a application that uses DAQmx.

 

Ton

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 6 of 8
(3,119 Views)

I solved the problem.Thanks anyways

Gaurav k
CLD Certified !!!!!
Do not forget to Mark solution and to give Kudo if problem is solved.
0 Kudos
Message 7 of 8
(3,087 Views)

What was the solution?

/Y

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

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 8 of 8
(3,052 Views)