Invoke node: invalid method error

hi, can someone help me explain what i did wrong or help me try to solve these errors..
i am trying to work on an example problem and i dont see where i did wrong..
thanks in advance
labview 7.0
Message Edited by krispiekream on 03-14-2008 12:11 PM
Message Edited by krispiekream on 03-14-2008 12:15 PM
Best regards,
Krispiekream
Attachments:
doing wrong.PNG ‏51 KB
cont_mult_vis_rem_pan.zip ‏155 KB

I'm a little confused, because I'm pretty sure you can't insert a VI into a tab control.
I think that's the source of your error, but I have no idea how you got those invoke nodes to appear on the block diagram.
edit - I see what you did. When you changed the example, you deleted the subpanels that were originally on each Tab page. You have to insert the VI into a subpanel which is displayed on a tab page. (Subpanels are on the Control Palette under Containers)
Message Edited by JeffOverton on 03-14-2008 01:23 PM
=============
XP SP2, LV 8.2
CLAD
Attachments:
subpanel.PNG ‏18 KB

Similar Messages

Invoke node wiring "weird" error

Greetings NI community,
    I know I have posted a lot about going from I2C to USB communications, and right now I am currently programming another controller in addition to the USB 8451, namely the Diolan DLN-2 - http://www.diolan.com/products/dln2.html.
   Now basically I'm trying to assemble my LabVIEW code that I've written before to work with Diolan, and Diolan has been of tremendous help - same level as NI!
   But I was trying to run this code (attached), but I get an unwired or bad terminal error at both invoke nodes (read and write - 2 errors - 1 for each) - but there's nothing to wire to/from, and the Diolan Engineer assisting me - his works fine (screeshot attached). It's the same exact code, I just cleaned mine up a bit, but didn't make any changes.
   Is there something I have to enable on my end for my code to run?
   Thanks!
    TheLT
Solved!
Go to Solution.
Attachments:
i2c-master-configure.vi ‏17 KB
i2c_master-read_write.jpg ‏73 KB

TheLT wrote:
Greetings NI community,
    I know I have posted a lot about going from I2C to USB communications, and right now I am currently programming another controller in addition to the USB 8451, namely the Diolan DLN-2 - http://www.diolan.com/products/dln2.html.
   Now basically I'm trying to assemble my LabVIEW code that I've written before to work with Diolan, and Diolan has been of tremendous help - same level as NI!
   But I was trying to run this code (attached), but I get an unwired or bad terminal error at both invoke nodes (read and write - 2 errors - 1 for each) - but there's nothing to wire to/from, and the Diolan Engineer assisting me - his works fine (screeshot attached). It's the same exact code, I just cleaned mine up a bit, but didn't make any changes.
   Is there something I have to enable on my end for my code to run?
   Thanks!
    TheLT
Can you show us the error messages please?
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Should a dot net Invoke node fill the error cluster?

Situation, a dll called by LabVIEW attempts to communicate with an instrument and can not because the instrument is not present. The DLL returns a standard LabVIEW error cluster with no error.
Person A says this is wrong : it must return an error. Further modules in the chain can not succeed with no communication. And that it is possible to return an error by throwing an exception.
Person B says : The program ran and did not die. This is our module not a LabView function. The error cluster should return no error. And that it can not return an error either,
The questions are Who is right A or B? And , since is has already gotten to a ‘is to, is not’ kind of disagreement, Where is any supporting documentation to reference that will authoritatively resolve the issue?
Solved!
Go to Solution.

In order for the dll to produce an error in LabVIEW, it must be programmed to throw an exception if no instrument is available. LabVIEW will then convert this exception into a generic error with code 1172 (see attached article.) LabVIEW can be programmed to give a custom error message using the attached example. In this case, it should be possible to have the .NET dll throw an exception, and then have LabVIEW generate a custom error message to display to the user. In this instance, it appears that Person A is correct. Hope this helps resolve the issue.
LabVIEW and .NET Exceptions
http://digital.ni.com/public.nsf/allkb/B15CE9F2715434C386256D3500601878
Programmatically Generate Custom Error Codes/Messages
https://decibel.ni.com/content/docs/DOC-9557
Regards,
Chris L
Applications Engineer
National Instruments
Certified LabVIEW Associate Developer

Invoke node error in PDSF vi

Iam using NI datalogger,for reading analog and digital inputs.In this datalogger there are many sub VIs.when i run the data logger iam getting the errors like, the sub vi PDSF_logistics.vi(process data standard format )is not executable.The error what it is showing is
Invoke node:Invalid method
The method selected in the invoke node is invalid or no method has been selected. Right-click the invoke node and select a method.
Invoke node:Invalid refnum class
The refnum class that is being passed into this node is not fully defined. This is because the refnum is defined using external files, and one or more of these files are missing.
Iam attaching the VI please have a look in to it.
Attachments:
PDSF_Logistics1.vi ‏75 KB

Hello dilreddy2001in:
It seems that the activex reference is not attached to an activex class.
In the front panel:
1] Right-click "refnum"
2] Go to "Select ActiveX Class"
3] Click "Browse"
If you copy/pasted it from another VI, you might as well do the same in order to determine the ActiveX Class.
I hope that this helps.
Good Luck...
PS
You also forget to attach 'PDSF_ErrorText.vi'

UAG 2010 RDS invalid method

Hi All,
would someone be so kind and post the TerminalServicesGateway rule from a working UAG install?
I'm getting invalid method errors (well, actually they're warnings) on both RPC_OUT_DATA and RPC_IN_DATA , even though the rule is there with the methods defined. My only guess is the rule is not matching because of a wrong Parameter
definition (see screenshot below: there's no value or anything defined).
Running UAG 2010 SP4
Error: Request <..> for application Remote Desktop Services of type TerminalServicesGateway failed because the method used RPC_OUT_DATA is not valid for requested URL /rpc/rpcproxy.dll?localhost:3388.
Thx in advance!
Rgds - M.

Please find below

Method Not Found Invoke Node error 1316 using Solid Works IEdm

Hi Forum members,
I have been having a problem with calling a function in a dll file. I have attached the VI as example. When I use the GetFile method I get a reference to that. I then use the Invoke node and recieve a list of methods, the first of which is ChangeState. I select this method and wire all required inputs and when I run the program I receive the error at that invoke node that the method does not exist. How is this possible? I have tried various methods to ensure the inputs are all correct and none have worked. I do not believe the fault lies in the inputs, but I cannot for the life of me find the problem... Perhaps someone has experience using Solid Works in Labview? Any help would be appreciated.!!
Cheers
Ben
Attachments:
SetFileSatus.vi ‏18 KB

I have determined that there is a problem with the Invoke node not recognising the function. This is a Labview problem as the function is listed and selectable, so when the error comes saying the function is not found, this is a problem with Labview and not the dll. The Function when selected also has the right input parameters that automatically appear. How is it then that the method is not found when the program is run?

Linq Error : Invalid 'where' condition. An entity member is invoking an invalid property or method

Hi,
I am running Linq query in CRM2013 and throwing error : Invalid 'where' condition. An entity member is invoking an invalid property or method.
My Code is as below;
var conntionRecord1Id = (from connectionBase in orgServiceContext.CreateQuery("connection")
where connectionBase["record1roleid"] != null
select connectionBase["record1id"]).Distinct();
var query = from opportunity in orgServiceContext.CreateQuery("opportunity")
where !conntionRecord1Id.Contains(opportunity["opportunityid"])
orderby opportunity["createdon"] ascending
select new
Topic = opportunity.Attributes.Contains("name") == true ? opportunity["name"] : null,
OpportunityId = opportunity.Attributes.Contains("opportunityid") == true ? opportunity["opportunityid"] : null,
PostalCode = opportunity.Attributes.Contains("new_address_postalcode") == true ? opportunity["new_address_postalcode"] : null,
Error throwing on second query.
Please help
Thanks,

Not sure I can help with that. I might debug this code and see what data resides in the first query for conntionRecord1Id.
Are you trying to get a list of opportunityId's? If so you might need to do a foreach loop on the results of conntionRecord1Id.
Something like...
foreach(var recordid in conntionRecord1Id)
(do something to the record...)

"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

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).

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 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.

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)

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: invalid method error

Similar Messages

Maybe you are looking for