Invoke node

Ciao a tutti, sono un principiante con LabView.
Voglio fare un'interfaccia che contenga una parte ripetuta piu' volte: penso si debba usa invoke node; ho iniziato con un semplice esempio.
Base.vi: contiene un integer input and un integer output collegati tra di loro. Questi due widjet devo essere visibili sull'interfaccia principale
Top.vi: usa Load.vi per generare il reference of Base.vi
Run.vi: passa i parametri a Base.vi
Nell'esempio che allego, per semplicita', ho inserito solo un'instanza di Base.vi...ma anche cosi' non funziona
Hi All, I'm beginner using Labview.
I want an UI thant contains more istances of a single part: I think I have to use a "invoke node"; I started with a simple example.
Base.vi: it contains un integer input and an integer output likend one to the other. These two widjets are visible in the main UI.
Top.vi: it's the main UI; it uses Load.vi to generate the reference of Base.vi
Run.vi: it gives the parameters to Base.vi
In the example in attachment, in a simple way, I inserted only one istance of Base.vi...but it does not work.
Attachments:
TestSubVI.zip ‏43 KB

Similar Messages

"Error 7 occurred at Invoke Node..." when attempting to open .vi for editing

I am attempting to open a vi for editing, and instead the vi is attempting to execute. I get the error:
"Error 7 occurred at Invoke Node in BuildTargetBuildSpecification.vi->BuildXFS.vi"
Possible reason(s): LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
Method Name: Project: Open
When I close the Error Message dialog, Labview terminates.

Hi R.Jay,
Error 7 generally occurs when trying to create an executable when there is an extra instance of a top-level vi. You may need to remove the file as a support file (but leave it as the top level vi).
Are you trying to run an executable that has already been created? Unless you have already built an executable, it should not automatically run when opened. Also, was it built in a previous version of LabVIEW? Sometimes this error can be seen when you upgrade to a newer version without compiling.
Regards,
Lauren
Applications Engineering
National Instruments

Is it better to use Invoke nodes or property nodes to set/get control values?

I have a series of VI's that run in parallel, each to manage different functions- pumping, sensing, a fluid flow model, an experiment generator/runner.
These need to exchange data, which I am currently doing using invoke nodes (that are all in subVIs), using methods "Set control value" and "Get control value". I find that every now and then (perhaps 1% of the time) the data isn't exchanged correctly and therefore the system doesn't work. I can imagine how "set" could go wrong if they happen simultaneously, and can devise ways of preventing this. However, the "Get" method suffers from the same problem. This is a major problem, because I want to leave it running for several hours.
I could in
principle achieve the same thing using property nodes and find myself wondering if this might be more reliable. But I don't want to change over only to find it makes no difference!
Can anyone advise?

You can use some kind of syncronization such as queues, occurances, or notifiers but I think the easiest way would be to create and action engine. This was only one action can execute at a time avoiding a "race condition". Possibly a write action and a read action might help. You also can add queues or notifiers into this concept. hope this helps.
BJD1613
Lead Test Tools Development Engineer
Philips Respironics
Certified LV Architect / Instructor

Excel ActiveX invoke nodes are broken

I am using LabVIEW 2007. We are using a VI that runs on most of the PC's in our facility however on some the "invoke node" related to Excel functions don't operate. They are broken and the VIs won't run. We get errors that the "Invoke Node: contains unwired ro bad terminals". When going to select methods or properties not all of the properties are shown as seen on the functional PCs. Some of the properties are missing from the selection menus, thus making it incompatible.
Has anyone seen this problem and a solution?
Thanks
Manliff,

What about separating the compiled code from the source? I recognize that this will only work in LV2010, but I expect that that will prevent the compiler from breaking activeX code that depends on a different version than the local one...
Testing this idea is on my to-do-list, but I was wondering if anyone has tried it already.
-Barrett
CLD

Strange behaviour with ActiveX invoke node and Excel

I want to send a table of numbers from LV50.1f to Excel97. After getting a
reg to Excel8.Application I retrieve the Workbooks property, Invoke Item to
select a certain Workbook reference, retrieve the Worksheets collection
reference, Invoke Item and then get a reference to WORKBOOKS again.
Strangely, there is an example code from the NI web site that does exactly
the same, but in the last step a variant is returned in stead of a
reference, which is converted using Variant to G to a Worksheet reference.
when I copied that last invoke node to my VI I also had a variant returned,
so on one diagram I had to invoke nodes connected to the same sources, one
returning a ref, the other returning a variant!
Disco
nnecting the sources to my Invoke node and rewiring gave no change.
Also type casting the ref to workbooks to a worksheets ref, didn't work - I
get errors in the following property node that retrieves a Range - which
exists in Worksheet, but not in Workbooks.
Appearantly, LV gets the returned type mixed up sometimes, and there is no
way to fix it other then copying a invoke node from another diagram?
Finally I got it working though, but this behaviour puzzles me. Contrary to
the example from NI, I now managed to send a table (2d array of strings) in
one call to Excel (don;t need to loop over cells or columns).
PS
I used to do the same using DDE but ranges are different for each language
version of Excel (i.e. R1C1 for English and R1K1 for Dutch), so my VI's need
to know the language of Excel. Also with NT and Win98, getting a DDE
connection often hangs LV. But a big progress has been made - now I need
different VI's for each version of Excel!!!
Ferry Toth
Enraf BV, The Netherlan
ds

Hi Enric,
Can you try your queries again using the new release of DB XML? It contains some improvements in this area.
http://www.oracle.com/technology/software/products/berkeley-db/xml/index.html
John

ActiveX Object Creation method to pass to an Invoke Node

Hi!
I'm trying to optimize the way in which I use MathCAD from LabVIEW. One of my VIs is having really poor performance in terms of execution speed and memory usage.
My VI converts a 2D LabVIEW array of doubles into a 2d Mathcad matrix and puts that matrix into a Mathcad worksheet. The issue is that you do not just pass the 2d array of doubles into the SetValue invoke node as a variant. You have to create a Mathcad.MatrixValue object, and then pass the object to the SetValue invoke node.
Here is the example code provided in the Mathcad developers manual:
SetElement Method
var m = CreateObject("Mathcad.MatrixValue");
for(row = 49; row >=
0; --row)
for(col = 9; col >= 0;
--col)
var val = row + col;
m.SetElement(row, col, val);
Here is my implimentation in LabVIEW:
Here is my SubVI
Here is my main VI:
My SubVI is running out of memory and throwing the following error:
Exception occured in mplrun: Exception of type 'System.OutOfMemoryException' was thrown. in NL SubVIs Library.lvlib:Convert LabVIEW 2d Array to MathCAD Variant Matrix (SubVI).vi->test.vi
It doesn't always throw the error. When I watch the memory consumption of LabVIEW it goes up to about 250k and then drops to 90k and slowly builds back up to 250k. Initialy starting the code takes awhile too on my computer. From start of VI until first loop iteration it is about 20 seconds, and then about 150-250ms after that. Not very good performance.
Any advice on how to optimize this code would be appreciated. I'm not really sure when I should close some of these references. I tried closing the reference in my converting SubVI, but I guess that destroys it so MathCAD can't use it.
I'm in LabVIEW 2009. Any help is appreciated.
Thanks for your time and input!
-Nic

I'm not sure this will solve your problems but it should help. You need to close ALL of your references to Mathcad objects when you're done using them. That means you need to close the reference to the Mathcad MatrixValue after you pass it to Mathcad (to do this you'll need to convert it back from a variant, or pass the reference directly out of your subVI), and you should also close the reference to the matrix that you get back after you've converted it to a LabVIEW array. Otherwise you'll continuously allocate more and more memory rather than allowing it to be reused.
Less importantly, you should also close your references to IMathcadWorksheets and IMathcadWorksheet (but since you only open them once it's not causing your memory problems).

Error 6 at Invoke Node in Dist Send Result File to RT.vi-- Build Applicaiton.vi

I am using cFP 2000 RT in my application. When I build exe and download the application to the cFP 2000 RT, I get "Error 6 occured in Invoke Node in Dist Send Result File To RT.vi--> Build Application.vi"
The steps followed.
1. In the LabVIEW 7.0 Main Panel, Select the execution target as RT Target.
2. Tools --> Build Application or Shared Library. In the Target Tab the destination directory is selected as \\xxx.xxx.xxx.xxx\c\ni-rt\startup automatically.
3. In the SOurce file tab, select the Top level VI.
4. Press Build to make the executable of the application. The application is built and at the end the error message is poped up. (see the attached file)
Software Configuratio
n:
1. LabVIEW 7.0
2. Field Point 4.0
3. LabVIEW RT 7.0
Help me solve this problem. Thanks in advance.
Attachments:
Error_Message_and_RT_Info.bmp ‏313 KB

This is most likely coming from the specific file it mentions in the error, Dist Send Result File To RT.vi. The error 6 means the file can't be found. One thing to try first is to add this VI as a Dynamic VI in Application Builder. Another option is to change the path that this VI is invoked from, or is not called by an Invoke Node at all.
I hope this helps, feel free to contact support if the problem continues.
Regards,
Robert Jackson
Application Engineer

Build error after upgrading from 8.2.1 to 8.5 "Error 1055 occurred at Invoke Node..."

After upgrading to 8.5, I'm getting the following error when trying to build an EXE:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1055 occurred at Invoke Node in AB_Source_Library.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Object reference is invalid.
I have been building this application for both Windows and Mac OS, and I even get the same error when building the .app on an Intel Mac.
Things that I've already tried:
* Mass-compiling all my code
* Created the project from scratch
* Enabled each panel of the "diagram disable structure" one at a time and compiled again
Any ideas?

Hi Travis,
Ben’s advice if definitely the best place to start. Error 1055 is a very general LabVIEW error for “Object reference is invalid.” The cause is usually a bad install where important LabVIEW function aren’t placed in the right directory or aren’t installed at all.
Charlie M. CLD

Error 1003 occurred at Invoke Node

Good morning.
I work with LW8.5 and created with the following architecture:
There is main.vi on the links at the user's calls and runs the other VI.
That is, not directly, these are not included in the VI block diagram main.vi.
In the development of a happening in normal mode, all dynamically called VI,
But once I make EXE, when you try to call the dynamic VI error 1003.
Error 1003 occurred at Invoke Node in Main.vi
Possible reason (s):
LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Open the VI in LabVIEW using File>> Open and verify that it is runnable.
VI Path: C: \ Shaikov \ Labwiev \ builds \ NSIAES \ Initialsettings \ Initialsettings.vi
Show you how to act?
Thank you.

Hello margasan.
In my Projects I use to pass more dynamic and VI classes.
In the attached file - an example of my project:
In the main folder is a folder UpperClass, it is the parent class and child classes and HeirClass.lvclass Heir2Class.lvclass are organized into folders respectively Plugin1 and Plugin2, and these Classes inherit from the parent one and the same WI - UpperClassTest.vi. Plus, this Plugin1 has two, independent from the others, but related classes. A block diagram for an object placed Core.vi UpperClass.
So, here, if you take EXE, making llb files and run them from start VI for each of the Plugin, then everything works OK.
But as soon as I on the block diagram of a Plugin will put any object UpperClass, or one of its nasalednikov, there arises a familiar ERROR 1003. Prompt, plc, margasan I get rid of it in this case?
Attachments:
Example.zip ‏1481 KB

Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi- AB_Engine_Build.vi- AB_Build_Invoke.vi- AB_Build_Invoke.vi.ProxyCaller

Hi there,
Hope someone can help me. I recently upgraded to LV 8.5 and am having a problem building a .exe which has a subvi in it that opens in a new dialog window. When I try to build this I get the following error:
Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
Method Name: Build:Application
I have built the .exe with the same subVi but without opening it in a dialog window and it works fine., so the problem seems to be linked to the inclusion of the dialog window.
Any advice greatly appreciated
Regards
Tadhg

UPDATe: I can get the .exe to build but now I get an error when I run teh .exe which is shown in the picture attached.
Attachments:
error screen1.JPG ‏122 KB

Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi- AB_Build.lvclass:Bui

During software build to make exe file, I got the following error message:
Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
Method Name: Build:Application
The vi was working fine before the build. It just access some text files and creates some excel files. No hardware is involved. See if anybody know how to solve this problem. Thanks.

I am using LabVIEW 2014 and have been getting this error randomly, but fairly consistently on a recent build. I searched all over and could not find a solution that worked. However, just through trial and error I discovered that the problem is related to SSE2 Optimization in the Advanced properties window. I can consistently cause this error by enabling this feature and consistently compile successfully when it is disabled. Try turning this feature off and see if it solves the problem.
...UPDATE: After closing and re-opening LabVIEW this error came back, and did not seem to be affected by the SSE2 option. Not that it isn't related, but perhaps not the silver bullet I thought it was.
I also got the error to go away sometimes when I compiled the EXE while the main program VI was open, whereas it gave the error most of the time when no VIs were open...again, nothing seems to consistently solve the problem...there is definitely some kind of bug in the appllication builder, and it seems like there are a lot of people that have been struggling with this for a long time (as far back as LV 8)...hopefully NI eventually finds this bug and squashes it!..although, I doubt that anybody at NI is even looking for it...

Error 7 occurred at Invoke Node in AB_EXE.lvclass

I get the "Error 7 occurred at Invoke Node in AB_EXE.lvclass" error when trying to build an executable in Labview 8.5.1. I can run the application without any errors but when I try to build the executable, I get the error. I have tried a mass compile of the project, tried ctrl + shift + run on the top level vi, and tried to mass compile the folder where the project is located and nothing seems to help. I have also looked at the project dependencies for conflicts and found none. I have made a new project and tried to build an executable from this same code without any luck. How can I get this to build an executable?
The exact error is:
Error 7 occurred at Invoke Node in AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface.
Method Name: Build:Application

Are you using the Report Generation Toolkit? A lot of error 7's during builds seem to be related to this toolkit. Any dynamically called VI's?
Take a look here and here.
Also search the forums for "error 7" and you'll find some other threads related to error 7 and the application builder.

Error 7 occurred at Invoke Node in Dist read linkages.vi- Dist Cmp Settings to Disk Hier.vi- Build Application.vi

Error 7 occurred at Invoke Node in Dist read linkages.vi->Dist Cmp Settings to Disk Hier.vi->Build Application.vi????
Hi I do not understand how to resolve this nagging problem.
I run the program in the development time and it all goes smoothly.
However when i wanted to build the program. I often run into this problem.
How to resolve it?
Clement

Hey Clement,
Which version of LabVIEW are you using? There some knowledgebases out there that address the issue. Click here for the first KB or here for the second one. Hopefully these would help.
Regards,
Chetan K
Application Engineer
National Instruments

How to get a LabVIEW class object to expose an invoke-node method?

Hi,
      I like the property/invoke-node "paradigm" used for interacting with "objects". Can LabVIEW-class objects expose their properties and methods this way? Can one or more LabVIEW-class objects be compiled into a library or "assembly" (or other distrubution format) that allows the property/invoke-node usage?
I've looked at (but not completely understood) "Creating LabVIEW Classes". Have also searched for related posts.
The pic below shows an invoke node wired to a class with a Public VI "VAT.Status.Hello.vi". I'd like to see VAT.Status.Hello show-up as a Method. (I just tried "Select Method", and selected "VAT.Status.Hello.vi" but dialog's "OK" button stays greyed-out.)
Cheers.
Message Edited by tbd on 03-29-2007 03:15 PM
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
Attachments:
VATStat.JPG ‏54 KB

Hi Aristos,
      Thanks for the reply!  It was a bit dissappointing, though.
It appears the LabVIEW-class object will be moving away from (what seems to me) a convenient object-interface presented by the invoke-node/method paradigm - which allows us to interface with a large set of "objects" (.NET, ActiveX, LabVIEW GUI, VISA Resource, ?) in a similar manner and independent of the object's origin. Being able to read the methods and parameters that appear in these nodes is also helpful for understanding diagram logic!
I do like the option of dropping a friendly "VI looking" icon on the diagram, but perhaps an optional - even default - VI-icon representation for a class-object invoke-node is feasible - so the LabVIEW class-object could be the more generic object first, but with a traditional-G representation(?)
Given the answer "We would like, someday, to support the property node"
and "in the next version of LV, wiring the LV class to the property/invoke nodes will break the wire so we'll avoid confusion in the future",
... I guess you'll break the wire in the next version, but (perhaps) allow it again - if support of the property node is ever implemented?
Regards.
P.S. For the record, huge THANKS to whoever it was that straightened-out enumerated-types (somewhere) between LV4.1 and LV6.1.  Every time I add or remove an enumeration in a typedef, I silently give thanks to the bright and thoughtful soul(s) who made this valuable tool work so well!
Hello. This is your friendly neighborhood R&D guy for LabVIEW classes.
Regarding your request about property and invoke nodes as relates to LV classes....
Short story: We would like, someday, to support the property node. We have no intention of ever supporting the invoke node.
Long story: As we were creating LV classes, we had to evaluate the right programming interface for these things. We wanted LV classes to behave as new data types in LV. A developer should be able to create a LV class, then give it to someone who doesn't even know OO programming, and that second programmer could use the new data type without learning a lot of new concepts. From this principle, we held fast to the idea that the programming interface should be subVI calls whereever possible. The invoke node is really nothing more than a VI minus the icon. If you want, you can popup on any subvi node and uncheck the option "View as Icon". This will make the node display in a way that has the terminals listed as text, like the invoke node. So, at the end of the day, the invoke node is simply a subroutine call in LV that is language dependent, as opposed to the language independent iconography of LV generally.
The property node is a slightly different story -- the functionality of a property node is actually different than an invoke node as its terminals are various subsets of the properties available, not a fixed list of parameters like the invoke node. The property node provides a nice interface for setting multiple properties in a block and only having to check a single error return. Very friendly. Our intent is to allow you to create a VI that has 5 terminals: object in, object out, error in, error out, and either a single input or a single output of your chosen type. VIs with this conpane could be marked as "properties" of the class and would show up when you wire the class wire to the property node. We would call the subVIs behind the scenes as needed to get/set the properties.
This is on the longer term roadmap because it is "syntactic sugar" -- it sweetens the programming style, but it is not necessary to program effectively. You can get the same effect by writing those same VIs and stringing them along on a block diagram "railroad track" style. We'll probably get around to it in three or four versions of LV -- there are some major user requests that impact functionality that have to get done first.
PS -- in the next version of LV, wiring the LV class to the property/invoke nodes will break the wire so we'll avoid confusion in the future of people thinking there's a way to use these nodes.
Message Edited by Aristos Queue on 04-02-2007 09:56 AM
Message Edited by tbd on 04-03-2007 12:39 PM
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)

How to name a new Excel worksheet using an invoke node??

I want output from my specific labview code to be written to a new and specific worksheet (meaning I want to provide the specific worksheet name) of an Excel spreadsheet my LabVIEW code will generate. My code will run in a loop where I want data that is generated in each pass of the loop to be written to a new worksheet each time through the loop. I know how to do this if I am ok with just having each worksheet be named 4, 5, 6, etc (on top of the 1, 2 and 3 that comes standard with a new Excel spreadsheet) but I want more meaningful names than just those numbers... So how do I add a new worksheet and give it a name of my choosing??? Also, when right click on an invoke node and then click on "Help for Item" which is right under the Methods selection that comes up, nothing happens, meaning I am not directed to any help file. I see that same behavior under LabVIEW 6.1 and also under LabVIEW 7.1. My guess is either I didn't buy some option required to have that help area be populated or I had it as some option but didn't know to install it when I originally installed LabVIEW??? Having that help available might help answer the question I pose above... I find working with ActiveX components to not be straightforward. Granted I haven't done it much and what I have done has been sort of follow examples and get it to work... But on this naming a new worksheet I have found no useful examples. My guess is it's easy but I'm clueless... Any help would be much appreciated... Note, in case it matters, I do not own the Report Generation tool/capability... thanks... bob...

Hi, Paris1:
Take a look at "Excel Workbook Properties", that is located in
REPORT GENERATION
-> EXCEL SPECIFIC
-> EXCEL GENERAL
-> EXCEL WORKBOOK PROPERTIES
One of its outputs is "Current Worksheet Name".
You can insert a ExcelWorkbookProperties VI in a blank VI and then double-click it.
You will se a rose vi named Excel Get Properties
And inside it (double-clicking it), the way Worksheet's name is got. If you "Change to Write" that property node, you can set it's name.
This way is very complicated, it can be done faster, but this way you can see a process to do that, and checking it, you can build your own excel VIs to do specific tasks.
Hope it helps,
Aitortxo.

LabVIEW Application throws Error in Run VI Invoke node

Hi All,
We are facing an issue with an application developed from LabVIEW 2010SP1.
Application Description:
In our application, there is a top level VI which tries to run VIs dynamically[using Run VI invoke node] from a particular folder. This folder is like a plugin - not part of Exe. This implies when the top level VI is launched, the plugin VIs under particular folder will not be in memory. When we try to run a VI dynamically from the top level VI, the VI execution works perfectly in LabVIEW development mode.
Problem Faced:
When we created an EXE, it worked well in my PC [LabVIEW is installed]. We created an installer and tested in few other PCs.
[Non LabVIEW PCs – Win XP and 7]. In few PCs it throws the following error, when the plugin VI is run dynamically.
Error 1003 occurred at Invoke Node
Possible reason(s):
LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.
Method Name: Run VI
We tried the following possible ways to find the reason for the issue:
1. Installed LabVIEW - Issue got fixed.
2. Installed .net 2.0 without installing LabVIEW - Issue got fixed.
3. But in one of the Windows 7 [Non - LabVIEW PC] in which .net was already installed, we faced the same error.
Only after installing LabVIEW the error got fixed.
4. When .net 2.0 is uninstalled the EXE itself is broken.
We are not sure what is the Exact reason fo the issue. Anyone faced these kind of issues? Please share the solution. Thanks in advance.
Note:
1. The VIs which are dynamically called is a plugin and not a part of EXE.
2. These plugin VIs have no dependencies from vi library and is completely isolated.
3. We are not using any .net related objects in any of the VIs.
4. The plugin VIs use Call library function node in which a C DLL developed from Microsoft Visual Studio 2010 is used.
Thanks,
Meena
Solved!
Go to Solution.

Error 1003: This clearly indicates that the 'Dynamic VI' is broken and now you should check for the various reasons, why the 'Dynamic VI' is broken.
Also path of 'Dynamic VI' is not a problem.
One thing that you may try is:
-> First open just the 'Dynamic VI' in a new LabVIEW project and check for the 'Dependencies'.
-> Now if any of the item in 'Dependencies', other than what is listed in vi.lib (lets call it 'Dependency.VI'), is also a part of your 'Main Exe', then its a problem. Because when you will execute the 'Main Exe', say in a new computer other than your development computer, it will load all its dependencies including 'Dependency.VI' (and the path will be within the 'Main Exe', but when it will try to (dynamically) load the 'Dynamic VI', this VI will also try to load the same 'Dependency.VI' but from different path and that will cause a conflict. I had experienced this.
-> If thats the issue, you may want to rename (add suffix/prefix) to all dependencies of your 'Dynamic VI' which is common to the 'Main Exe'.
Hope this solves your issue.
I am not allergic to Kudos, in fact I love Kudos.
Make your LabVIEW experience more CONVENIENT.

Invoke node

Similar Messages

Maybe you are looking for