Calling labview 8.2 Vi from teststand 3.5 throws an error

calling labview-8.2 vi in teststand-3.5 throws the following error.
In the development environment, where Teststand 3.5 and LabVIEW 8.2 are installed, teststand file doesnt throw any error. However when the same sequence is deployed in a machine that doesnt have teststand and labview. (Both Teststand runtime engine and Labview runtime engine) are installed in the end machine.
Trying the execute the sequence in the end machine throws the following error
"Error loading step 'Call LabVIEW measurement module for amplitude imbalance' of sequence 'MainSequence' in file 'TSG06-Amplitude Imbalance.seq'.
LabVIEW: VI version is later than the current LabVIEW version."
Attachments:
Error.JPG ‏26 KB

Hi,
Should have also asked this question before.
What is your LabVIEW Adaptor set too on the target system. Use ActiveX Runtime Server or LabVIEW RTE. If its set to use the LaBVIEW ActiveX Runtime Server which can be either the Operator Interface or the seperate ActiveX Server, then these are probably built with an early labVIEW.
If so you would need to rebuild the server you are using.
Regards
Ray Farmer
Regards
Ray Farmer

Similar Messages

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

Call Vision Builder 2014 AI from TestStand 2014.

I need info on how to run Vision Builder 2014 AI from TestStand 2014

Hello jspeedz,
I did have a look at that doc it didn't address in enough details to my needs. I figured out the process thanks.

LabVIEW Access Violation Crashes from TestStand

We've been seeing numerous LabVIEW crashes when calling VIs through the LabVIEW adapter in TestStand. I've searched the knowledge base and discussion forums without success and figured I would post here before opening a help request.
The actual error we see is:
Exception: Access violation (0xC0000005) at EIP=0x012B60E6 Version: 11.0.1f1
We see these crashes several times a day, but while calling no specific VI. They happen mostly on 2 PCs that are running Windows 7 - 64 bit, but we've seen them in the past on PCs running the 32 bit version of Windows 7. Here is the data related to those 2 problematic PCs.
OS: Windows 7 Professional SP1 64 bit
LabVIEW: 2011 SP1 (11.0.1f1) 32 bit
TestStand: 2010 SP1 (4.5.1.134) 32 bit
PC: Dell Optiplex 790 with Intel Core i5
Other significant information.
We see these crashes when we're running the batch model in TestStand with multiple threads open. Some VIs are reentrant, and some are not.
The 2 PCs that run the batch model (with multiple threads) have the 64 bit version of Win 7 Pro, and crash most often.
The 3 PCs that run the sequential model or the batch model with a single thread have the 32 bit version of Win 7 Pro and rarely if ever have crashed.
Not sure if it's related to the OS version or the multi-thread usage and switching the PCs/OS versions to isolate that isn't easy.
Has anyone else seen similar issues? Does Windows 7 Pro 64 bit work reliably with TestStand and LabVIEW 2011 32 bit versions? I posted this question in the LabVIEW discussion forum, but I don't know where the issue resides, I'm posting in the TestStand forum also.
Any information would be appreciated.
John Morrissey

I just had the same error in a LVOOP Project. First I got a crash (something with out of memory). The I got subsequent Access Violations. Could trace it down to one VI that:
a) had been working just fine before
b) wasn't changed after test mentioned in a) but got (even just running on its own) subsequent access violations every time I ran it
c) VI used a class konstant, property node (to set 2 class attributes); Inputs were a string and an integer and an error cluster; outputs: one instance of the class (initialized with string an integer) and the error cluster
d) Problem could be solved by deleting the class constant used in the VI and put the same in again (an just rewired the thing); I assume this caused a recompile that solved the prob
Maybe this helps narrowing the general problem down.
P.S: I dont have a still non working version of that VI, since I was happy to have solved this and just saved the VI before thinking about making a copy.

Call to ALDP 3.2 dataservice using Mediator API throwing validation error

Hi,
Call to ALDP 3.2 dataservice using Mediator API with request doc having xsi:type (eg: <ns1:searchBy xsi:type="ns2:ImplXXXIDType">) is throwing validation saying that it is unable to resolve the namespace ns2 .The namespace ns2 is defined at root level. If the namespace ns2 is defined at the element level like this
<ns1:searchBy xsi:type="ns2:ImplXXXIDType" xmlns:ns2="http://www.xxx.com/xyz/datastructure/1/"> it is working fine. We never had this issue with ALDSP 2.5 Mediator API.
Any suggestions or help would be most welcome!
Thanks,
Gkumar

Ok. Now you need to put enough information on the case for someone to investigate. Please attach instructions on how to create a data space that will show this problem. Since customer support will not have your database etc. , if you just create an empty ds function in the same ds as the one that has the problem, like so...
function dummyFunction() as element(....)* {
and then replace the () with the output from the Test View so it looks like...
function dummyFunction() as element(....)* {
<myElement ....>
<otherElement ...>
</myElement>
Once you have a dummy function like that which demonstrates the problem, export your dataspace and attach it to the case.
If you anticipate some of the questions that customer support is going ot ask you (including providing a reproducer), you will save yourself many days (or weeks) of time.

Problem calling a LabVIEW VI from TestStand

I'm am currently migrating my companies test scripts from TestStand 3.0 to TestStand 4.1.1 and VI's from LabVIEW 7.0 to LabVIEW 8.6. I have re-saved all of the sequence files to the new version as well as performed the 'Mass Compile' operation on all of our custom VI's. During the execution of one of the sequence files a call is made to a VI (through a LabVIEW library). If I run this sequence file on a machine with the development software and have the Adapter for LabVIEW set to use the development system the VI executes as expected. If I have the adapter set to use the Run-time engine (in this case 8.6, the same as the development version) I get an error:
"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."
I noticed that in the library file there are sub VI's that are called from "C:\Program Files\National Instruments\LabVIEW 7.0\vi.lib" This directory only exists on machines that have the development system installed. Perhaps this is why the VI does not execute using the runtime engine

Ray is right. Development environments are backwards compatible (you can run VIs compiled in LabVIEW 7.1 or 8.5 in LabVIEW 8.6). That's why you can run your sequence just fine on the development system, but on the target machines you are using the LabVIEW Run-Time engine, which is not backwards compatible. With the Run-Time engine, ALL VIs need to be in the same version as the Run-Time engine (including VIs in vi.lib, tools.lib, instr.lib, etc.).
The first thing I would check is make sure everything has been mass compiled to 8.6, including vi.lib. If you are still getting the error you should be able to tell at what point the error occurs so you can look at that specific VI. Open it and confirm there isn't a broken run arrow and check to see what subVIs that VI is using and confirm they all have been compiled in version 8.6 too.
This should get you going, but if not just let us know.
Message Edited by CorbinH on 05-07-2009 08:24 AM

Passing telnet session between LabVIEW calls from TestStand

From TestStand I am calling VI's from telnet.llb.
In one TestStand step am opening a telnet session to an IP address and collecting the telnet connection (U32). In the next TestStand step I pass the telnet connection to a telnet write VI but get this error.
"Dequeue Element in Acquire Semaphore.vi:1->Telnet Write.vi:1->Telnet Write.vi.ProxyCaller"
The telnet open, write, read, and close work great if I pass the telnet session number within the same VI. But I need to keep the session open between calls from TestStand because one huge VI is not feasible.
thank you
josh
Solved!
Go to Solution.

Hi,
Maybe the following link can help
http://forums.ni.com/t5/NI-TestStand/Can-a-Telnet-session-be-passed-from-1-vi-to-the-next-in-test/m-...
Regards
Ray Farmer

How can I convert a Database Handle from TestStand to LabVIEW?

I want to use a Database Handle (already created in TestStand by an Open Database step) in a LabVIEW-VI (called from TestStand) to connect it with the "Connection Reference" input of the "Easy SQL.vi"? If I use a directly connection via the "TestStand - Get Property Value (Number).vi" I get back the error message 4101 in LabVIEW. How can I convert the Database Handle?
Test Engineering
digades GmbH
www.digades.com

The TestStand database step types use the CVI SQL Toolkit to talk to databases. The handle that you are referencing is an internal memory location and not a actual handle that you can directly use. Currently as implemented the handle that is stored in a numeric TestStand property for the connection and the SQL statement are the handle values returned from the CVI SQL Toolkit. So for the connection handle, you could call the CVI SQL Toolkit function
DBGetConnectionAttribute (
int Connection_Handle,
tDBConnectionAttr Attribute,
void *Value);
and get the CVI CAObjHandle reference. With this you could then call the CVI ActiveX function
CA_GetInterfaceFromObjHandle(
CAObjHandle Object_Handle,
const IID *Interface_Id,
int Force_AddRef,
void *Inte
rface_Ptr,
int *Did_AddRef);
to get the actual ActiveX interface reference. This would have to be converted into a LabVIEW reference.
You may want to consider just using LabVIEW to open a new parallel reference only using the toolkit.
Scott Richardson
National Instruments

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

When I call VI on Linux from Teststand on Windows using TCP/IP I get "file not found error".any sugeestions?

I am trying to execute a VI running on Linux from Teststand running on windows 2000 prof ,both running on two different machines.I used TCP/IP for the interface using the following steps on Labview VI:tools>options>VIserver>TCP/IP and gave the ip address of both the machines.When I gave the file path as c:\home\test.vi in Edit labview Vi call window(the Vi in linux is stored in /home/test.vi)and also in remote vi path:/home/test.vi,I get a file not found error.The teststand version is 3.0 and labview is 7.0.Any idea why this is happening and any solutions?

priya guru,
Here is a knowledge base that addresses your question: �How do I call test VIs that reside on a non-Windows platform from TestStand?�
You also need to set TCP/IP Access found in Tools->Options->'VI Server: TCP/IP Access'. Make sure that you list the IP address in the Access List to allow TCP/IP access to that machine. Finally you need to specify which VIs are accessible to remote applications. Open up Tools->Options->'VI Server: Exported VIs' and provide paths to the VIs you wish to be remotely accessible.
I have attached an example VI that demonstrates VI Server in action. Please post back if you are still having problems. Good luck!
Cr
aig H.
National Instruments
Attachments:
Remote_Run_--_VI_Server.zip ‏88 KB

User event from TestStand to Labview

Hello all,
I have some question regarding Labview-TestStand
We have a large application written in Labview, user interface separated from the actual
core using User Events. Now we consider to automate some repeated actions with slightly
different parameters. Is the TestStand sutable option for thi case? Can it send the "User event" to
Labview?
Thanks
Michael.
LV 8.2 at Windows & Linux

Hi mishklyar,
tbob makes a good point, and I will try to elaborate a little bit. TestStand is test executive software. It works by executing a set of predefined steps in sequence. These steps can be LabVIEW code, C code, etc. You can pass parameters into the LabVIEW code that you call, but you cannot directly send "user events" the same way that user events are created in LabVIEW by interacting with front panel controls. The traditional design with TestStand is to create a LabVIEW code module that does a particular thing, and have other modules (VIs) that do other things. Then, call each module from TestStand as needed. As the name implies, TestStand is often used for testing products, but could be used for other purposes as well. If your application could be modified to fit this model, then TestStand could probably be used. However, you would probably want to architect your LabVIEW application differently than it is right now.
Best Regards,
John M
National Instruments
Applications Engineer

Is it possible to call a LabVIEW VI by reference from a CIN?

I am calling by reference in my LabVIEW program and would like to do the same from a CIN, if possible.

> I am calling by reference in my LabVIEW program and would like to do
> the same from a CIN, if possible.
>
It is not possible to directly call a VI by reference from a CIN.
There are a couple approaches that are similar that will work. If you
have the professional version, you can build a DLL from VIs and can call
the DLL entrypoints from your CIN.
It is also possible to signal a LV occurrence from a CIN, and a LV
diagram could run a VI or perform an operation when the occurrence is
set. You will not be able to pass parameters with the occurrence though.
Finally, the approach that will be easiest to debug is to change the CIN
so that it returns to the diagram more often. Call the CIN and have it
return with an action. The actions can be -- run
a particular VI, delay
for x ms and call the CIN again, end the program, etc.
This last approach will be slightly less efficient at runtime, but in my
experience they are much more flexible and much easier to debug.
Greg McKaskle

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

How do I call Vee functions from TestStand ?

I wish to call Vee functions from TestStand steps.
I am using Vee 6.01 and TestStand 2.0.

Hi Gerry,
Sorry about that. Below is a sequence file created in 2.0.1f1. Please copy the contents of the zip file (previous attachment) into the folder \Examples\VEE\Using ActiveX (VEE 6.0). Please create this directory if it does not exist. The next thing you will need to do, is register the TestStand VEE server located in \Examples\VEE\Using ActiveX (VEE 6.0)\VEE_StepType.dll. To do this:
1) Select Start>>Run.
2) Type regsvr32 "C:\TestStand\Examples\VEE\Using ActiveX (VEE 6.0)\VEE_StepType.dll"
You should get a message saying that the registration was successful. You should now be able to run the example. Please let me know if you encounter any further problems. Thanks!
Attachments:
Computer.seq ‏66 KB

Calling LabView ActiveX Server from TCL?

Does anyone have experience calling a LabView ActiveX server vi from
TCL? I created a simple VI with one control (labeled "A") and one
indicator (labeled "B") and a +1 adder between them. I can load and
open the VI from TCL:
package require tcom
set lv [::tcom::ref createobject "LabView.Application"]
set viPath "D:\\National Instruments\\LabView\\Activity\\a.vi"
set vi [$lv GetVIReference $viPath]
$vi FPWinOpen True
But when I try to send in data:
$vi -namedarg Call A 1
I get the error message "unknown parameter A".
I have also attempted to duplicate the "ActiveX Server" example
from the LabView help file, calling "Frequency Response.vi". This
approach encounters the same error message:
% package require t
com
3.0
% set lv [::tcom::ref createobject "LabView.Application"]
::tcom::handle0x013202F4
% set viPath "D:\\National
Instruments\\LabView\\examples\\apps\\freqresp.llb\\frequency
Response.vi"
D:\National Instruments\LabView\examples\apps\freqresp.llb\frequency
Response.vi
% set vi [$lv GetVIReference $viPath]
::tcom::handle0x01335AE8
% $vi FPWinOpen True
% $vi -namedarg Call Amplitude 10
unknown parameter Amplitude
If anyone can point me in the right direction, or give me an
example of how to do this I would greatly appreciate it.
TIA.
Leslie

In article ,
Leslie Brooks wrote:
>"Bruce Hartweg" wrote in message
>news:...
>> "Chin Huang" wrote in message
>news:[email protected]...
>> >
>> > I don't use LabView, but from the Visual Basic example I saw, it seems
>> > the Call method takes two arguments. The first is an array of parameter
>> > names and the second is an array of parameter values. Try to send in
>> > data with the Tcl command
>> >
>> > $vi Call [list A] [list 1]
>>
>> I'm unable to help the original question (don't know LAbView or VB stuff) but
>> just want to point out that [list A] is equal to A and [list 1] is the
>same as 1.
>>
>> Bruce
>
> I know what is supposed to be passed to the 'Call' method. Doing
>this:
>
>set inst [::tcom::info interface $vi]
>$inst methods
>
> produces (among other things):
>
>{1015 VOID Call {{{in out} {VARIANT *} paramNames} {{in out} {VARIANT
>*} paramVals}}}
>
> So the 'Call' method is expecting two parameters, both pointers
>to variants. TCOM appears to be passing the correct parameter type
>because the TCOM documentation says that a TCL List maps to a
>one-dimensional array of VT_VARIANT. However, the results are
>INvariant (bad pun intended):
>
>% $vi -namedarg Call Amplitude 10
>unknown parameter Amplitude
>% $vi -namedarg Call [list Amplitude] [list 10]
>unknown parameter Amplitude
>% $vi -namedarg Call [list Amplitude] [list [::tcom::na]]
>unknown parameter Amplitude
>% set i 5
>5
>% $vi -namedarg Call [list Amplitude] {incr i}
>unknown parameter Amplitude
>% $vi -namedarg Call [list Amplitude] [list [incr i]]
>unknown parameter Amplitude
>% $vi -namedarg Call Amplitude [incr i]
>unknown parameter Amplitude
>
> Who can help me with this? Who is the LabView Guru?
Try invoking the Call method without the -namedarg option. The
-namedarg option doesn't work the way you seem to think it works. The
-namedarg option provides a way to specify arguments named from the
method's parameter specification. For example, you discovered that the
Call method take two parameters named "paramNames" and "paramVals".
Tcom returns the error "unknown parameter Amplitude" because "Amplitude"
doesn't match either parameter name.

Calling labview 8.2 Vi from teststand 3.5 throws an error

Similar Messages

Maybe you are looking for