Calling LabVIEW VIs

Hi All,
I am having trouble calling a vi and passing parameters to it using ActiveX calls. I used the code he found it on the website ni.com, but there is no reference to how to call vi from tcp network, as \\hostname:14000\application.vi
I try use this code:
Dim lvapp As New LabVIEW.Application
Dim vi As LabVIEW.VirtualInstrument
Dim viPath As String = ""
viPath = "\\hostname:14000"
vi = lvapp.GetVIReference(viPath)
vi.FPWinOpen = True 'show the front panel
vi.Run(True)
i tried viPath = "C:\LabView\MyFolder\Appliction.vi" and work, what is the right syntax???
Thanks!

I'm sorry,
I forgot to say that I compiled the labview project as .exe! it's possibile to extract the reference of vi from an exe? example \\hostname:14000\application.exe\application.vi or something???

Similar Messages

Some errors when calling LabVIEW VIs Interactively from DIAdem

Hi! I'm having some trouble using the "Calling LabVIEW VIs Interactively from DIAdem" found on:
http://zone.ni.com/devzone/conceptd.nsf/webmain/1A98AB48E35D913086256E23004E6A22
Following the troubleshooting section didn't resolve the issue. I
recompiled and built the exe (DIAdemLabVIEW.exe) for version 7.1.1,
which I am developing on. But still I got the same error message, after
a waiting for about a minute, on a diadem popup window:
Error in <MenuAdd...ctDo.vbs (row:1, column: 1)
Error in <addmenuentry.vbs (row:14, column: 3)
ActiveX component can't create object.: 'DIAdemLabWIEV.Application'
Using the llb's and exe's that was included with the installer worked
flawless, with the exception that LV 7.1.1 vi's didn't appear on the
popup window(DIAdemLabWiev.vi). So I tried to recompile and build for
the 7.1.1, with this result.
I'd be very grateful for fixes or solutions for this problem!
Regards
Roger Isaksson

Brad, thanks for the reply! Below is my (correct?) modification of your script. Have I got it right?
Dim lvapp, vi, viPath, paramName(1), paramVal(1)
Set lvapp = CreateObject("LabVIEW.Application")
viPath = "C:\TEMP\Test.exe"
Set vi = lvapp.GetVIReference(viPath)
vi.FPWinOpen = True
paramName(0) = "In Name"
paramVal(0) = "In Value"
paramName(1) = "Ut Name"
Call vi.Call(paramName, paramVal)
Call lvapp.Quit()
MsgBox "Parameter1 Value = " & paramVal(1)
I am not sure about the format of the <paramName(0) = "In Name">.
The control name is "In" and is a I32, the name for the indicator is
"Ut" and has the same storage type as the control.
Running the script gives an error in line 4, that is the <Set vi =
lvapp.GetVIReference(viPath)>. I'll attach the exe and the error
message.
I have another question regarding the relatively large amount of RAM
that diadem uses for export from my labview application to diadem. More
than 10 times the size of the data is required for exporting to diadem.
Since our application use relatively large files, actually up to
several GB's, this soon becomes problematic. See the attached picture
of the memory usage after exporting a 10MB segment (contains 42
channels of measurement data). Your help in these matters would be
appreciated!
Regards
Roger Isaksson, Damill AB
Message Edited by Roger Isaksson on 09-09-2005 10:22 AM
Message Edited by Roger Isaksson on 09-09-2005 10:22 AM
Attachments:
VBError.JPG ‏181 KB
Test1.vi ‏9 KB

Call LabVIEW VIs from MATLAB

Does anybody know of a simple way to call LabVIEW VIs from within a MATLAB m-file? I would like to be able to write VIs in LabVIEW and then script them (for stochastic analysis, etc.), and think MATLAB would be an awfully convenient way to do this (also useful for data analysis, etc.). I have looked at LuaVIEW, but it appears to have been largely abandoned.
Thanks!

Hello Erik,
Building it into a DLL as Altenback said is a solid way to do this, and here's a Knowledge Base article that also explains how to transfer data in binary or ASCII format, How do I Transfer Data Between The MathWorks, Inc. MATLAB® Software Development Environment and LabV...
Thank you,
Deborah Y.
LabVIEW Real-Time Product Marketing Manager
Certified LabVIEW Architect
National Instruments

Calling labview VIs from python in Linux

Hello.
I've spent some time searching for this but I haven't found exactly what I was hoping for.
I'm involved in a project that we're starting now and it involves creating a complex software architecture in order to control a robot. This software will need to perform multiple tasks such as interfacing with hardware (which LabView is perfect for) as well as planning and high performance image processing (which LabView isn't as great for).
I was hoping to be able to use a scripting language like python to manage high level stuff (planning, behavior, etc) by calling "subroutines" in other languages such as C++ for the high performance stuff and LabView VIs for the hardware interfacing. I would also like this to run on Linux.
I've found a lot of suggestions on how to call Python scripts from within LabView but this is not what I want. I want exactly the opposite, invoke VIs from Python. I found some information on how to do this on Windows (http://zone.ni.com/devzone/cda/tut/p/id/5719) but this article seems to assume that Windows is being used.
Does anybody have an idea on how to do this?

Unfortunately that's not an option. This is an interdisciplinary school project involving students from engineering (mechanical, electrical and more), computer science and more fields. Some of these students have gotten used to using Labview and this is the main reason I'm trying to accomplish this. I want to have the higher level architecture done in a scripting language such as python which will enable us to create modules in various different environments such as C++ for tasks requiring high performance (image processing for example), Labview for tasks that the people used to using that and even something running on the GPU if there's use for that. Python would make it easy to glue all these components together while maintaining an environment that would make it very easy to configure the whole software system in different ways.
I'd also prefer that this all run on Linux.
The more I look for this the more hopeless I get I'll find anything which is very frustrating. It's a bit hard to believe that Labview doesn't have "python bindings" for running the VIs from within python :-(

Call labview vi interactively from diadem 10

Hi, I am trying to run a LabVIEW VI from DIAdem. I have LabVIEW 7.1 loaded on my machine and got Diadem 10. I have downloaded the tool for calling LabVIEW VIs interactively from DIAdem but am unable to run my VI. Only VIs from library DIAdem_selectVIs executes. Is there any solution to call LabVIEW VI from DIAdem 10.
This is the link. Plz Check it out.
http://zone.ni.com/devzone/conceptd.nsf/webmain/1A98AB48E35D913086256E23004E6A22?opendocument&node=5050_US
Regards,
Peter.
Pizza

Hi Brad,
Thanks for your quick response. I worked on that example You have sent. It's working fine. I find little hard to pass my channels from Diadem to Labview and vice-versa. Can You please help me. I have attached a simple array addition Labview VI.
Cheers,
Peter
Pizza
Attachments:
pressure 2.vi ‏10 KB

How do I search all LabVIEW VIs in a TestStand sequence?

I have a TestStand sequence that calls a hierarch of other TestStand sequences, and many of these call LabVIEW VIs. I want to perform a LabVIEW search on all VIs in this hierarchy.
If I could programmatically list all these VIs, I could take it from there by opening all the VIs then performing the search. Is there a way to do this?

This may help.
Lemme know if you have questions.
Cheers,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~
Attachments:
ExtractVIPathsFromSeqFile.vi ‏31 KB

Find names of all open windows including other applications besides LabView VIs

Hi All, I have researched this subject, i.e., to find names of all open windows including other applications besides LabView VIs, but found no solution. Could someone suggest a solution to this? Thanks.

Hi,
Certainly! The Windows API Function Utilities (32-bit) for LabVIEW includes set of LabVIEW libraries (llb) with VIs that make calls to the Windows Application Programming Interface (API) for managing and controlling windows (minimize, maximize, move, resize, rename, close, and so on) including task list with names of windows application running. The Readme.doc contains information on running these VIs.
Attached below is a zipped file with a VI that list the names of all opened windows.
Tunde
Message Edited by Tunde A on 04-18-2007 02:28 PM
Attachments:
List Windows Application LV8.0.zip ‏55 KB

How to call Labview-VIs in a AgilentVee-function?

Hello,
i have some good running Labview-Vis and want to use them in a Agilent-Vee-function (*.vee).
Is there a way to make a DLL from the VIs?
Or is it possible to run a VI from a C++-DLL? Then i could create this DLL and call the DLL in VEE.
But i would be easier if i could call the VIs direct in VEE, so if any VEE-users are reading this... perhaps someone has an idea.
Thx for any
ideas.
best
regards
J.

Or you could use the VI server ActiveX interface to do this.
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!

How to read and write data from Excel to TestStand without using LabVIEW VIs

Hi,
How can I read in columns of data from Excel into a TestStand array and write columns of data to Excel from TestStand without using LabVIEW VIs?
I don't think the Property Loader custom step type in TestStand will work because the data I would like to read in from Excel is in a column that is thousands of rows long and the data has to be in the proper format to use the Property Loader to load in an array from Excel.
Thanks for your help.

That example does not use LabVIEW and it does about 40% of what you need to do by calling Excel through ActiveX. If you don't know how to use Excel through ActiveX then you'll need to brush up on that.
http://www.microsoft.com/en-us/download/details.aspx?id=16250
http://support.microsoft.com/kb/141759
http://support.microsoft.com/kb/302084
CTA, CLA, MTFBWY

Can we call LabVIEW VI's (saved at shared location say server)from two different test stations?

Hello All,
My question is related to calling and execution of LabVIEW Vis from two or more different teststation(Test System) using NI TestStand.
Following are some definitions to understand the question better
A Test Station:is a independent sytem.different instruments(Multimeter,Function generator etc) are connected to this Station.Teststaion using NI TestStand for Test managment.
A LabVIEW :LabVIEW vis are saved at share location(server).These vis are responsible for communicating with different instruments connected to TestStation.
Execution:TestStand calls these Vis in sequene to perform particular test.
My query is to know ....Can we call and execute shared labVIEW vis from two or more TestStation simulatneously and cummunicate with connected instrument on each teststation.
Is there any possiblity of conflict as using same vis but on different station?
My concern is to avoid duplicacy of similar vis.Is there any better option to implement the same concern?
Thanks in advance
Regards:
Vaibhav Kanchan
Sr. Engineer
NI Certified LabVIEW Developer(CLD)
NI Certified TestStand Developer(CTD}

I suggest you to try adding the shared vi to the labview project(.lvproj) running in same or different stations which is connected to the instrument. Adding the vi to a project will open it in the project instance instead of default application instance. Hence there won't be any conflict in execution.
Anand kumar SP
Senior Project Engineer
Soliton Technologies Pvt Ltd

Problems calling LabVIEW VI through ActiveX inside another LabVIEW VI

Hi everybody,
basically I would like to create an ActiveX to be inserted in a LabVIEW VI which at its turn would call another LabVIEW VI.
I have choosen Visual Basic to create this ActiveX, being the main section code:
Dim lv As LabVIEW.Application
Dim vi As LabVIEW.VirtualInstrument
Dim names(0 To 1) As String, values(0 To 1) As Variant
'Assign an object reference to VI
Set lv = New LabVIEW.Application
'Assign an object reference to VI
Set vi = lv.GetVIReference(lv.ApplicationDirectory & "\Examples\General\Strings.llb\Parse Arithmetic Expression.vi")
vi.ShowFPOnCall = False 'Open front panel if requested
'Initialize the variables & define the strings corresponding to the VI connector labels.
names(0) = "Arithmetic Expression": values(0) = "1+1"
names(1) = "Result"
'Call the VI
vi.Call names, values
So, when this ActiveX executes this code sequence it locks when creating the "LabVIEW. Application" object. I have tested this ActiveX from another client application (Internet Explorer) and it works perfectly, so the problem is located in the creation of ActiveX from LabVIEW. Do I need to do anything special in my code or simple it cannot be done what I want to do?
Thanks !!!
Jesus Valero
Plataforma Solar de Almeria.

Exactly, but really the code of above it's only an example that I want to do. I'm trying something more sophisticated.
I want to create an ActiveX control that could work as stand alone executation with the ability of directly get some indicator values from its LabVIEW VI container and depending of those values, set the control values of others LABVIEW VIs. I really know that within LabVIEW itself I can get/set those indicators/controls, but with this method I think that the diagram block of the LabVIEW VI container can be more simple.

How To: Reference LabVIEW VIs in Memory from a Compiled Application?

Hello all! This is my first post on these boards despite the fact that I have been doing LabVIEW for almost 8 years...so go easy on me!
Basically my issue is this: I want to write a compiled application for my team to use to help us have a standardized tool to push VI help tip information. So I created a nice front panel, gave it memory storage via XML to remember info you might want to not have to type over and over again. I also gave it some formatting options, etc. Overall, a nice tool to speed up a repetitive task.
However, it runs great as a VI, but compiled does not work at all and I am sure many of you can see where this is going. I have cobbled together some snippets of code found on these boards to collect a list of references and names of all the VIs in memory that are not currently running. Then I use a ring control to parse which VI I want to target and then push the parsed and formatted help tip to that VI. But the reality is apparently that LabVIEW and a compiled application do not share the same memory allocation, because they are separate application instances.
Is there ANY way around this?
I tried one thing that seemed to make sense, but so far has resulted in the same thing. I tried to do a type def call by reference with an asynchronous call and a wait on asynchronous call function to return the reference list. However, even though this bit of code is still a VI and NOT part of the compiled code, it still somehow picks up the application instance of the owning app, and therefore does not see any of the open VIs in memory that LabVIEW controls.
Any help would be immense, as I am going nuts trying to figure this out!
Info: LabVIEW 2012.f3
I am also attaching a screen cap of the block diagram of the VI that collects the references.
Thanks in advance!
South West Applied Technologies
Senior LabVIEW Developer

Well you run into a security limitation of VI server here. Many methods and properties are not possible to be accessed through a remote application instance. Any Application instance that is opened with an address is considered a remote instance. Basically if you leave the address open in the Open Application, LabVIEW shortcuts to the internal instance. If you connect some address even if it is "localhost", LabVIEW goes through the TCP/IP socket for any and all methods and proeprties and the application instance is considered a remote instance.
Open your floating help window, and place your cursor above your property. Notice the text in there: Remote Access disallowed: Yes.
The reason for this is, that if this method was available over remote connections, anyone with access to your network could connect to that LabVIEW instance and basically discover any and every VI you have currently loaded and even download them to their own computer. And this can not be fixed. This security is not possible to circumvent other than hacking into LabVIEW itself.
I guess this kills your entire idea. An executable can't connect to another executable or the LabVIEW development environment other than through a remote connection! That is due to strict process isolation rules in all modern OSes. The only possible workaround I could think is to create VIs for all remote access protected methods and properties, copying them to every LabVIEW installation you want to access with your shell (and that likely would have to be done through the network as the according methods in the VI server interface are also remote access protected) and then call those VIs through VI server.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

TestStand - Call Package VIs for Distribusion.vi is not executable

I am trying to assemble my VIs for Run-Time distribution using the TestStand tool. How ever on selecting the Run-Time distribution option, the following error is displayed
"An error occurred in the 'Package VIs' step of the 'Package VIs' sequence in 'VI Packager.seq'.
LabVIEW : VI is not executable.
An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001"
On oppening the vi (TestStand - Call Package VIs for Distribusion.vi)it was seen to have brken arrows. The problem appears to be located in the sub vi, TestStand - Build dist for TestStand.vi which is password protected. Could this be a problem with my ActiveX connection(TestStand is using the LabView standard prototype Ada
pter with the LabView Development environment serving as the ActiveX server.The sequence I am trying to package runs successfully under these condisions)?

Hi,
One of the things you need to do is to ensure all your vi's are at the same version of labview. All TestStand assoicated llb's and Vi's are at version 5.1.1 when you first install it.
Therefore, if you have updated your labview, you will need to mass compile the TestStands folders.
Also, check the Updates for TestStand, http://digital.ni.com/softlib.nsf/954feaeea92d90918625674b00658b83/e047ebba4b45a98786256949007bc2a7?OpenDocument this may or may not affect depending on what TestStand and LabVIEW versions you are using.
Regards
Ray Farmer
Regards
Ray Farmer

Where can I get an example of how to call Labview.exe (Active X Server) from Visual C++

I would like to Call Labview application (as Active X Server) from Visual C++. I need any type of exemple on how to do this, any input will be greatly apriciated.

In the summer there has been an example in the Developer Zone, but i can't find it again. I can send you the attached zipfile from that example. The example is resricted to single threaded applications. In multi threaded applications you must initialise OLE in the thread where you communicate with the active-X server.
If you need more information contact me at [email protected]
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions
Attachments:
VCandLabVIEW.zip ‏91 KB

Labview VIs for HP 35670A

The link to the labview VIs for the HP 35670A is no longer valid and the search for the same returns nothing. Does anyone have the Labview VIs for that instrument?
The last post was back in 2004(see below)
The instrument driver for the HP 35670A is only
supported under LabVIEW 6 and 7. You should upgrade to the latest
version of LabVIEW in order to use the HP 35670A driver or any of the
newer drivers that we release in the future.
The instrument
driver for the HP 35670A can be found on our web site at
http://zone.ni.com/idnet97.nsf/9b2b33e1993d877786256436006ec498/61f1c707c2f10906862568ab005fb9ff?Ope...
Solved!
Go to Solution.

Why don't you go to the Instrument Driver Network? I don't know what kind of search you did but the driver is certainly still available and can be found by using the search option there.

Calling LabVIEW VIs

Similar Messages

Maybe you are looking for