LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"Sub-VI's not executable" when running Labview 2012 LLB files. I am using Labview 2014. I was told that I have to relink the "DLL"l file to each sub-VI to fix the issue.

Is this true? If so, what is the process of re-linking the .dll to the VI?

 

thanks.

0 Kudos
Message 2 of 6
(3,012 Views)
What sort of VIs are you talking about? What is the dll that you need to link to? Have you right clicked on the Call Library Function Node?
0 Kudos
Message 3 of 6
(3,004 Views)

thanks for the reply.

I'm calling the comCom.dll and I used the Call Library Function Node to configure the right path for the .dll file. But vi still won't run.

 

please see attachment for screenshots.

 

Is it because I'm using only the Labview 2014 evaluation to run the vi?

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

Are you sure that function name is correct?  It looks like a junk name to me.


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
0 Kudos
Message 5 of 6
(2,942 Views)

@crossrulz wrote:

Are you sure that function name is correct?  It looks like a junk name to me.


It most likely is correct. This is the name mangling you get when you use a C++ compiler and don't explicitedly tell it in the source code to use standard C naming conventions. The descriptions from the OP are vague, but it may have to do that he installed LabVIEW 64 bit and the DLL is a 32 bit DLL.

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
Message 6 of 6
(2,861 Views)