Passing teststand sequence context to labview

hi,
i want to access teststand sequence context from labview , can i know how to do that ?
-giri

Hi,
This is cross posted here: http://forums.ni.com/t5/LabVIEW/mapping-labview-variables-to-teststand-sequence-context/td-p/1928835
There is another method:
Rodéric L
Certified LabVIEW Architect

Similar Messages

Mapping labview variables to teststand sequence context variables

hi,
how can i map variables from a vi (which is loaded in a test sequence in teststand) to teststand sequence context variables ?
if my question is not clear enough then plz let me know.

Sure I can help!
You can use either method:
Rodéric L
Certified LabVIEW Architect

How can I programatically modify a teststand sequence global in Labview ?

Hello,
I am automating some tasks using Labiew to modify data in a Teststand sequence file. How can I programatically modify the value of a Sequence Global from labview ?
Thanks,
Sam

You have to pass in the TestStand variable RunState.ThisContext to the vi through the connector pane. I'm not sure about the exact variable name because I don't have TestStand loaded at this time. But there is a variable for the sequence context in TestStand and this has to be passed to the vi. Note that you cannot run the vi stand alone. You must run it from TestStand in order to get the proper sequence context.
- tbob
Inventor of the WORM Global

How do I find the path to a TestStand sequence file using LabVIEW

My LabVIEW application launches a bunch of teststand sequences, provided it has the complete path to each of them. I want to make it more flexible by providing it just the name of the TestStand sequence so that it will go and find the path to the sequence by searching a directory structure. TestStand has a neat FindFile() function that can do this, but I need to do this from within LabVIEW. Is there a way to do it?

There are a few ways to do this depending on how you are getting the sequence files. If you are calling the GetSequenceFileEx method, you can just pass the GetSeqFile_FindFile (0x20) flag in the SequenceFileFlags property. If you are using the ApplicationMgr.OpenSequenceFile method, this is automatically done for you.
If you want to use the FindFile function in general, you can use the Engine.FindFile method.
Allen P.
NI

How to make labview real time understand sequence context

Does anyone know how to make Labview RT to understand teststand sequence context? My sequence context is defined as "TS.SequenceContext" as the screenshot in the attachment.
If we need to point a VI for this Sequence Context then which VI from teststand to use? and do we need to add this VI to the Labview Projectr Explorer in RT System to build the project?
I'm using Labview 2009 and teststand 4.2.1.
Thank you very much
Solved!
Go to Solution.
Attachments:
LVRT_TS.SequenceContext error.doc ‏132 KB

LabVIEW RT does not support ActiveX which is required for TestStand.

TS Sequence Context and Invoke Node problems

I have a Vi that was developed in 7.1 and TS 3.1. I inherited this design from a past developer. The Invoke node works fine when loaded with LV 7.1 but not when I load the Vi with LV 8.2.1. I have gone through everything I can think of to correct the problem. Help would be appreciated. [email protected] (contact address to let me know you posted or you can do it directly. Thanks in advance.
Attachments:
TestStand - Dist LabVIEW Test - Sequence Context.ctl ‏6 KB
TestStand - Get Property Value (Number).vi ‏42 KB

I just loaded this vi in 7.1, 8.2 and 8.5 and it works just fine for me. Although my TS version is 4.0. Can you expalin what you mean by it doe not work in 8.2. Does it load correctly? Have you reinstalled teststand into LV 8.2 so that you can open the TS pallette in LV 8.2? Are you running this inside of a sequence and passing the sequence context to it. It will not run correctly if a sequnce context is not passed to it from TS.
Also you should post this in the teststand forum and not the LV forum
Joe.
"NOTHING IS EVER EASY"

Deployment teststand error (labview test - sequence context)

Hello,
I need help by deploying my workspace to the deployment(target)computer. That is what I have done:
- i create a workspace, in this workspace are different sequence files and the vi´s which i have created.
- then i use the deployment tool (teststand) and deploy the workspace to a directory in the network.
- after that i copy the modified SequentialModel.seq to the target maschine.
- now if i want start the sequence file an error occured. Teststand can`t start my vi´s because it can`t find files like LabVIEW Test - Sequence Context, TestStand - Set Property Value (Boolean Array). Choosing the path of the file in the search directory doesn`t help.
Maybe i have made an error with the deployment tool?! How is the right way to deploy in a network without using an installer. Iám using teststand 3.0.
thankyou
Schwede

Hi Schwede
If you want to deploy your Sequence File and the Processmodell you have to copy first your original Processmodell from the NI folder to the user folder.
Than open the deploy-tool and load your workspacefile. Mark the point "deploy files in Teststand user directories" and define the image path. Don't mark the "create installer" field.
You will get and image folder with several subfolder.
In the target subfolder you can find your sequencefile. In the Teststand subfolder you can find your customized Processmodell or Operator Interfaces. Attention, please use relative paths when you create your workspacefile.
hope this helps
Manuel Wielander
National Instruments

Control LabVIEW GUI via TestStand sequence

Hello,
I have a VI with several buttons(controls) that the user can change during the test.
How can I associate these buttons(controls) with TestStand sequence so that during the sequence depending on a variable I set In TestStand the buttons(controls) in the VI will be activated.
Thank you,
Lev Kolomiets

Lev,
Are you talking about your User Interface? Or is it just a VI that you call from your test sequence?
If it's the User Interface then you should use UI Messages.... (Google or Bing: TestStand UI Messages. let me know if you have more questions on that).
If it's a VI you call in a different thread from your test sequence then you will want to pass in the sequence context. Then you can use the VIs on the TestStand palette (specifically TestStand - Get Property Value.vi).
Hope this helps some,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

I am trying to have some LabVIEW code called in a New thread exit when the testStand sequence terminates

I have a Sequence that launches a sequence in a New Thread that happens to launch some LabVIEW code. The problem is when the LabVIEW code finishes, it will not close even when the TestStand sequence terminates. Is there a way to tell this LabVIEW code to Exit, I've tried the Quit LabVIEW function, but that causes a C++ RunTime Error. The LabVIEW code does end though, and it is set in the VI properties to:
Checked - Show Front Panel When Called
Checked - Close Afterwardds if originally closed
The sequence call that the LabVIEW code is launched from has the following options:
- New Thread
Unchecked - Automatically wait for the thread to complete at the end of the current sequence
Unchecked - Initially Suspended
Unchecked - Use single threaded apartment
Any clues on this would be appreciated.

Hi ADL,
Everything should close correctly if you check the checkbox "Automatically wait for the thread to complete at the end of the current sequence" in the thread settings.
With it unchecked, I am seeing the behavior you are.
Gavin Fox
Systems Software
National Instruments

LabVIEW VI with Report Generation Toolkit elements in a TestStand sequence does not run with a LabVIEW 8.5 Run-Time Engine

Hi all,
I am using LabVIEW 8.5.1 and TestStand 4.1. I have done a TestStand sequence with a VI in it, which uses Report Generation Toolkit elements. On my machine I am using LabVIEW and TestStand with a Development System license. On the other machine I am using TestStand with a Base Deployment license and I have chosen the LabVIEW 8.5 Run-Time Engine in the Adapter Configuration. Everything is running well except of this VI with Report Generation Toolkit elements. The error message is showing that the VI is not executable. It works well only after I have installed LabVIEW with an Evaluation license and chosen LabVIEW 8.5 Development System in the Adapter Configuration.
I have found other posts and a document in the KnowledgeBase with a similar problem: http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402?OpenDocument But I am not using EXE files in my sequence, so I don't know how to solve mine. Anybody has an idea?
Solved!
Go to Solution.

Hello guys,
thank you very much for your answers!
@Ruediger:
I tried to follow the instruction for Method 2 in the mentioned document: http://digital.ni.com/public.nsf/allkb/F3DC40A6E3F3B25B862570AD005D1D3D?OpenDocument, but the steps on my machine are different starting from step 4. After I click "Continue..." in step 3, I dont get a window, the system just makes a new folder with the same VI.
To be honest, I am new to LabVIEW and have some difficulties at this time. What I understood from your reply is, that I need to make a LLB-File, where the files from Report Generation Toolkit are in!?
@GovBob:
I was following the instruction in the document: http://digital.ni.com/public.nsf/allkb/9E00E7EFE0635E678625734600779EFE, but it wasnt working. Can you please tell me how I can check if the VI Server is installed and running on the machine?
I am using LabVIEW 8.5.1 and TestStand 4.1 on my machine, on the deploy machine there is TestStand 4.1.1. The version of my Report Generation Toolkit is 1.1.2.
Kind regards, Roman

Is it possible to call a VI that is inside a LabVIEW executable from a TestStand sequence?

I have created a custom TestStand operator interface and have modified the default sequential process model to display a UUT information dialog that prompts for more information than just the UUT serial number. This UUT information dialog is a LabVIEW VI. To distribute the operator interface, I build it into an executable. As part of the build process, I make a copy of the UUT information dialog VI (which is part of my operator interface project) and place it in the same folder as the executable. I have then configured the sequential process model to call the dialog VI from this location. It would be really nice if I could embed the UUT information dialog VI inside the operator interface executable so that I could distribute just an executable instead of an executable and separate VIs. Is this possible? In other words, is it possible to call a VI that is inside a LabVIEW executable from a TestStand sequence just like a standard LabVIEW VI call?

Ryan,
The dialog that you've created isn't being directly called by the OI at all and shouldn't need to be included in the same directory as the OI for distribution. Since you are modifying the PreUUT of the default process model, you will give the path to the VI in that step, create a deployment and then manually copy the VI to the directory referenced in the step. The VI is considered a support file for the process model and is not related to the OI at all.
Test Engineer - CTA

How do i read the Shift register value of a vi which is written in the teststand sequence from labview exe

Dear All..
My Qusetion is ... I have a VI in which I can writ the data to shift register and I can read( Differenent cases). I am Running the VI in write mode to write SAY '100' in the shiftreg( VI will be In teststand Sequence) . And I am reading the VI in read mode using Labview. I am getting the data in labview.
When i conver my Reading Vi which is having that Read/Write vi in to EXE even then the test stand is writing the data to VI is Unable to reflect in labview.
Please Help me out with some solution.
Thanks
bhargav

I'm confused by your question:
Are you trying to transfer data from an Exe to TestStand and vice versa?
Or are you changing existing, working VIs into EXEs and then wondering why they won't behave the same?
Can you clarify some what your goal is?
There may be a better way to do what you want.
Thanks,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Execution of TestStand-Sequence in LabVIEW via TS-API: Different Execution times for same sequence

Hello Forum-Members,
I have a problem concerning the execution of an TestStand-Sequence in LabVIEW. I have created a VI that offers the ability to choose a TestStand-Sequence-File and then executes the sequence using the TestStand-API. The implementation is based on an example in C++-Application found following this link:
http://forums.ni.com/t5/NI-TestStand/Unreleased-references-using-engine-API-in-C/m-p/2927314#M46034
The implementation works quite solid in case the VI is executed the first time. The VI processes the chosen sequence in a acceptable duration.
But in case the execution is started a second time, the execution of the sequence takes ca. 30sec more than in the first case.
Until now I have not found a solution and hope someones got a hint concerning this problem...
I am using LabVIEW 2013 and TestStand 2013.
I have attached my own VI, a sample sequence with a small sample VI, so you can reproduce the problem.
Kind regards,
TobiKi
Solved!
Go to Solution.
Attachments:
Exe-TestStand-Sequence.vi ‏25 KB
Sequenz.vi ‏8 KB
Test-Sequenz.seq ‏5 KB

Hi Norbert,
first thanks for your answer.
What would be a reasonable way to replace the "Execution.WaitForEndEx"? My first idea is to get the respective thread of the execution and use the "Thread.WaitForEnd".
To clarify my problem:
The execution of the sequence itself takes longer time and so the execution of the calling VI. I have attached pictures of the log file of the first and second execution.
Further I don't get any dialog popups during the shutdown of TestStand. (I have activated the "ReportObjectLeaks" using the "DebugOptions") While developing the attached VI I've gotten several popups. But these popups disappeared after closing all references.
Maybe you have another hint how to locate the problem.
TobiKi
Attachments:
FirstExecution_20-08-2014.png ‏16 KB
SecondExecution_20-08-2014.png ‏16 KB

TestStand sequence launchs Labview Window

When I open a sequence in TestStand 3.5 consequently Labview is opened. But I have a test bench where this doesn't happen. (note: the bench are software and hardware identical, but assemblied in different moment). Moreover, when I launch my testing application (that recalls a teststand sequence), on the first bench appears always the labview window, while on the second bench none labview window is opened.
I'd like to reproduce the second behaviuor: none labview window is opened.
There is a particular setting in teststand to block the labview window?
Note: the testing application and sequences are the same on the two benchs. The bench setting are identical. I controlled every setting between the two benchs.
Solved!
Go to Solution.

There is a setting that I just found out about in the LabVIEW.ini file. It disables the Getting Started Window dialog on LabVIEW 8.6. It might work on LabVIEW 7.1 and may be present on one of your two test computers.
Can I Disable the LabVIEW Getting Started Window On A Macintosh?
The setting is "showNoNavDialog". Look on your computer that is behaving as desired and see if this setting was added (would be set to TRUE).
\Program Files\National Instruments\LabVIEW x.x\LabVIEW.ini
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

How to Run teststand sequence file using the LabVIEW

Hi
I want the execute the Teststand Sequence file using the LabVIEW .Net containers.I didnt find out the Execution Parameter in the .Net Container.Do you any suggestion regarding this question.Please let me know.
Jayavel

TestStand comes with loads of Operator Interface examples some simple, some full fledged. You can find it in teststand public folder win7 path here:C:\Users\Public\Documents\National Instruments\TestStand 2010 SP1\UserInterfaces
You can take these examples or use ideas from here, also read the teststand reference manual. It has a section about Operator Interfaces.
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

Passing teststand sequence context to labview

Similar Messages

Maybe you are looking for