Invoke Node and clipboard methods

I have encountered a very useful vi that allows me to obtain an image from the clipboard by using an invoke node with the clipboard.get image method. As I was experimenting with this, I attempted to place an invoke node and selecting the clipboard.get image method. Clicking the invoke node gives me three methods: empty (after enabling scripting), read from clipboard and write to clipboard. I could not find get image anywhere. How do I select this method on a newly placed invoke node?
Part 2: Given that this method seems to be hidden from me, how can I learn about other "hidden" methods?
- les

The block diagram is simply an Invoke node with the Clipboard.Get Image method. All inputs and outputs are routed to the front panel and connector pane, so you are not missing any functionality.
Since it is a private function, I can not release it without locking the block diagram. Private functions are just that, functions that are not exposed to our customers, usually due to insufficient development time or testing. I have crashed LabVIEW, corrupted my LabVIEW installation, and corrupted a huge hierarchy of VIs using private functions, so they must be approached with extreme caution, even internally. This particular function has been certified safe, so I was able to release an encapsulated version of it. However, you will not be able to find it in the development environment until it is officially released.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Similar Messages

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

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?

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.

Error 1172 occured at invoke node

Hello
I am new to Labview and object oriented programming. I have an already written c# code which communicates with a digital I/O card attached to a test system. I want to run those c# functions in labview. I am using .NET constructor pallett and then invoke node but I am receiving following Error:
Error 1172 occurred at Invoke Node Error calling method DmmCSharp.Handler.Reset, (System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
Inner Exception: System.Runtime.InteropServices.COMException: KtMDsr: A connection to the instrument has not been established.)
Image file of error and vi file is attached below.
Attachments:
vi file.png ‏5 KB
error.png ‏45 KB

The clue is in the 'A connection to the device has not been established'. You are trying to reset the device - presumably without having first configured the appropriate parameters or opened connection to it so the library is probably throwing that error.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

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'

Error 1039 invoke node

Hello,
I have been using the Invoke Node with RunVI method. The code was working for years. Now I get error 1039 which says the VI has been aborted. This is disturbing as nothing has changed with my code.
TommyHelter

Tommy,
Something obviously changed. Have you installed any new software recently? Moved this VI from one pc to another? Disconnected hardware?
Most likely the VI you are trying to run is popping an error and aborting because of it.. Try manually opening the targeted VI and running it. Do you get any errors? Does it run successfully?
Rob K
Measurements Mechanical Engineer (C-Series, USB X-Series)
National Instruments
CompactRIO Developers Guide
CompactRIO Out of the Box Video

How can i call a DLL file using invoke node from labview?

I cant call a DDL function using call library function.so plz tell me how to use invoke node and call DLL using invoke node
Please Mark the solution as accepted if your problem is solved and donate kudoes

Please stay in the same thread.
- Cheers, Ed

Invoke node XY graph

I have an array that is going to a XY Graph indicator. But I have to perform a certain test at 4 different temperatures, so I need a loop, but I want to save each plot in a file. So I found out that i can use the invoke node and select export image. But then I dont know how to finish the wiring to make it work. I am going to attach the idea of what im trying to do. From the VI i attached there is a bundle that has two 1D array inputs, (they are not shown in the attachment) and then an ouptut cluster of 2 elements. Now since I need 4 plots, I need to save each plot everytime 1 temperature test is done...if i do not do this by the end of the test, at the 4th temp , that is the graph that i will be getting, the other 3 are gone or overlapping
Thanks for your help
Josef
Attachments:
invoke node.vi ‏11 KB

Josef,
I’m a little confused by your question as well. However, I think the only thing you are asking for is how to keep the images from overwriting each other. This can be done by programmatically changing the input of the Path in the invoke node every time you have a new dataset.
Charlie M. CLD

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

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)

Invoke Node Method: Close FP (LV7)

LabVIEW Masters:
If an Invoke Node is used with the Close FP method, does any code remaining after the Invoke Node execute? Specifically, if you've invoked the Close FP Method (on the same top level VI that is calling the function) and then follow this function with the Close VI Reference function (for the same top level VI), does the Close VI Reference function ever execute? I'm aware that by closing the Front Panel the top level VI and all sub-routines are released from memory so is it necessary to call the Close VI Reference function as well?

Hi Steve,
Sorry no master, just Ben.
Interesting question. I put together the attached VI to see if I could answer this Q for myself.
The bottom line depends...
If you want your VI to play nice and be usable as a dynamic VI called from a bigger badder VI TestStand, etc. you should close the reference.
When you invoke the close FP method that closes the FP, Yes.
If that VI is the only VI in memory and you exit LV, then get cleaned-up in your behalf when LV exits. In this case it is not required to lose the reference, but,
"Flame suit on"
It is concidered bad style.
"flame suit off"
If you trying running the LV7 demo I posted and open another new VI, then look at the VI hiarchy screen you will see what I mean.
The demo I posted uses an event structure with a case structure in the timeout event case. This case lets you determine from a front panel boolean if the code executes an invoke node close FP. After the invoke node there is a seq structure that drives a boolean indicator to let you know the code following the invoke node does execute.
The example also lets you experiment with close the VI ref. If you run the example and allow all of the references to be closed, then a front panel close event will close the VI and un-load it from memory. Closing a VI ref can be thought of as being an official way of telling LV "I do not care about this VI any more, unload it no no else cares either". If you le tthe demo loop a couple of times opening ref to itself and then start shutting down the refs, you will see that VI will say in memory.
The example also shows that you can set up an event case that will fire on the close FP event giving you the ability to abort the operation programaticly. This demonstrates that the can run well beyond the close FP.
The demo also illustrates DR VI's rule "if the refnum changes, close it" by type casting the ref's as an array of I32's.
Summarizing:
IF this is a top level "quicky" VI you do not HAVE to close the reference. You can get away with just the invoke node close FP.
If you want to write re-usable code that will load and unload in a predictable manner, close the ref.
Sorry about the rambling, I hope this makes sense,
Ben
Ben Rayner
Certified LabVIEW Developer
www.DSAutomation.com
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction
Attachments:
Demo_close.vi ‏48 KB

How to Create Instances in the Transient Root Node and Sub Nodes from Root Node Query Method ?

Hi All,
I am Creating a BOPF BO with 3 Nodes,
Node 1) ROOT -- > contains a query,
using Root Node I have created Search UIBB Configuration in FBI.
In testing -- > when i enter Data in the Search Criteria Fields am able to get the details in to the query method
from Imporing parameter : 'IT_SELECTION_PARAMETERS'.
HERE I am fetching data from a standard table and trying to fill the data in the Node : 'MNR_SEARCH_RESULT'.
How to Append data to the Sub node 'MNR_SEARCH_RESULT' when there is no Node instance created in the ROOT Node ?
For This I have created an instance in the ROOT Node and Using that I tried to create Instance in the Sub Node 'MNR_SEARCH_RESULT'.
Below is my code which i have placed in the Query method ..
DATA : LR_DATA TYPE REF TO ZBO_S_ROOT1.
DATA : LR_SEARCH_RES TYPE REF TO ZBO_S_MNR_SEARCH_RESULT.
DATA : LO_CI_SERVICE_MANAGER TYPE REF TO /BOBF/IF_TRA_SERVICE_MANAGER,
        LO_TRANSACTION_MANAGER TYPE REF TO /BOBF/IF_TRA_TRANSACTION_MGR.
   LO_CI_SERVICE_MANAGER = /BOBF/CL_TRA_SERV_MGR_FACTORY=>GET_SERVICE_MANAGER( IV_BO_KEY = ZIF_BO_TEST_PO_C=>SC_BO_KEY ).
   LO_TRANSACTION_MANAGER = /BOBF/CL_TRA_TRANS_MGR_FACTORY=>GET_TRANSACTION_MANAGER( ).
CREATE DATA LR_DATA.
LR_DATA->KEY = LO_CI_SERVICE_MANAGER->GET_NEW_KEY( ).
LR_DATA->ROOT_KEY   = IS_CTX-ROOT_NODE_KEY.
LR_DATA->PIPO_MAT_ID = '100100'.
LR_DATA->PIPO_MAT_DESC = 'MATERIAL'.
LR_DATA->PIPO_SPRAS = 'E'.
LR_DATA->PIPO_MATL_TYPE = 'ZPMI'.
LR_DATA->PIPO_MATL_GROUP = 'ZKK'.
     DATA lt_mod      TYPE /bobf/t_frw_modification.
     DATA lo_change   TYPE REF TO /bobf/if_tra_change.
     DATA lo_message TYPE REF TO /bobf/if_frw_message.
     FIELD-SYMBOLS: <ls_mod> LIKE LINE OF lt_mod.
    APPEND INITIAL LINE TO lt_mod ASSIGNING <ls_mod> .
    <ls_mod>-node        =   ZIF_BO_TEST_PO_C=>sc_node-ROOT.
    <ls_mod>-change_mode = /bobf/if_frw_c=>sc_modify_create.
    <ls_mod>-key         = LR_DATA->KEY.
    <ls_mod>-data        = LR_DATA.
DATA : LT_CHG_FIELDS TYPE /BOBF/T_FRW_NAME.
DATA : LS_CHG_FIELDS LIKE LINE OF LT_CHG_FIELDS.
DATA : LV_KEY TYPE /BOBF/CONF_KEY.
CALL METHOD IO_MODIFY->CREATE
   EXPORTING
     IV_NODE            = ZIF_BO_TEST_PO_C=>sc_node-ROOT
     IV_KEY             = LR_DATA->KEY
     IS_DATA            = LR_DATA
     IV_ROOT_KEY        = IS_CTX-ROOT_NODE_KEY
   IMPORTING
     EV_KEY             = LV_KEY .
CREATE DATA LR_SEARCH_RES.
LR_SEARCH_RES->KEY           = LO_CI_SERVICE_MANAGER->GET_NEW_KEY( )..
LR_SEARCH_RES->PARENT_KEY    = LV_KEY.
LR_SEARCH_RES->ROOT_KEY    = LV_KEY.
LR_SEARCH_RES->MATNR    = '123'.
LR_SEARCH_RES->ERSDA    = SY-DATUM.
LR_SEARCH_RES->ERNAM    = SY-UNAME.
**LR_SEARCH_RES->LAEDA    = .
**LR_SEARCH_RES->AENAM    = .
**LR_SEARCH_RES->VPSTA    = .
*LR_SEARCH_RES->LVORM    = .
LR_SEARCH_RES->MTART    = 'ZPI'.
LR_SEARCH_RES->MBRSH    = 'ZTP' .
LR_SEARCH_RES->MATKL    = 'MAT'.
**LR_SEARCH_RES->BISMT    = ''
**LR_SEARCH_RES->MEINS    =
CALL METHOD io_modify->create
           EXPORTING
             iv_node            = ZIF_BO_TEST_PO_C=>sc_node-MNR_SEARCH_RESULT
             is_data            = LR_SEARCH_RES
             iv_assoc_key       = ZIF_BO_TEST_PO_C=>sc_association-root-MNR_SEARCH_RESULT
             iv_source_node_key = ZIF_BO_TEST_PO_C=>sc_node-root
             iv_source_key      = LV_KEY
             iv_root_key        = LV_KEY.
I am Unable to set data to the Node . I did not get any error message or Dump while executing . when i tried to retrive data I got the details from the node but am unable to view those details in the FBI UI and BOBT UI while testing .
Please provide your valuable Suggestions.
Thanks in Adv.
Thanks ,
Kranthi Kumar M.

Hi Kranthi,
For your requirement you need only two nodes. Root Node and Result node. Use the same structure for both.
To create Instance while search.
Create Query method with input type which has the required fields for selection criteria.
Fetch the data and create instance in the root node.
Pass the new instance key as exporting parameter form Query Method.
To Move data from ROOT to Result.
Create a action at root node.
Write a code to create new entries in Result node.
Then configure the Search UIBB and display result in List UIBB. Add button and assign the action MOVE_MAT_2_RESULT.
Create another List uibb to display data from Result node.
Connect the UIBBs using wire schema. SEARCH -> LIST(ROOT) ---> LIST(RESULT).
Give src node association for ROOT to RESULT Configuration.
Regards,
Sunil

I am using the NI application note "Calling IVI-COM drivers from LabVIEW" I created an Automation Open and an Invoke Node, after wiring

the 2, the AN asked to right click the Invoke Node(this is step9) and choose initialize. However there is no intialize option on the pop up menu. Anything am I doing wrong? I am using Labview6 and I did add the "enableCustomInterface=True" in the INI-fileThank you for your help.
T Tall

the 2, the AN asked to right click the Invoke Node(this is step9) and choose initialize. However there is no intialize option on the pop up menu. Anything am I doing wrong? I am using Labview6 and I did add the "enableCustomInterface=True" in the INI-fileT Tall,
What's the number of the application note "Calling IVI-COM drivers from LabVIEW"? I'm unable to find what you're looking at.
Thanks,
--Bankim

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

Invoke Node and clipboard methods

Similar Messages

Maybe you are looking for