Using labview global in test stand sequence steps

If I have to pass data between different steps ( only labview vis) within same Main sequence, is it right using LabVIEW globals, rather than TestStand globals?
in one step, I will be writing data to the Global.
In a later step, I will be reading the global to access that data.
Example sequence:
I am more comfortable with using Labview globals than Teststand variables. Labview is the only adapter in my sequence.

If it is just within one sequence, then I would use the TestStand variables. The reason is because you are limiting your possible reuse of those VIs by using the global. If you pass in the value, you have a better chance of being able to reuse the VI.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

Is there any way I can convert a Test stand sequence and corresponding vi's to an executable?

I need some creative ideas on how I can convert a test stand sequence into an executable in the shortest possible time. I know that beats the entire purpose of using TestStand but I need to have a way to do this. Is there no other way i can accomplish this without writing a sequencer in LabVIEW and rewriting all of my code in LabVIEW??

There is no way i know or can think of to move all components from a TestStand application into a single EXE. Running TS in an application means that you should/must work highly unitized during developement and deployment.
In general:
-> Custom UI will become "The EXE" for the enduser. This involves the link for startup on desktop/start menu.
-> TS Engine, ActiveX Server, will be attached to the UI.EXE OS process when launched by the UI. Will never be part of the UI.EXE.
-> TS Compontens (e.g. process model, language files, ..). Will never be part of the UI.EXE.
-> Custom Components (e.g. modified process model components, reporting, ...). Very unlikely(never) to become part of the UI.EXE.
-> Custom Sequences. Will never be part of the UI.EXE, but extension can be changed to other than .seq.
-> Code modules called by custom sequences. Unlikely (but possible) to be part of the UI.EXE. Should be implemented and tested to run within the RTE (runtime engine) of the appropriate programming language. It is not par design, that the deployment system has the development environment of that programming language installed.
-> License information. TS requires at least the Base Deployment License installed and activated (requires NI License Manager software). RTE of modules might also include licensing and possibly activation fees.
Why is there the requirement to have a single, monolythic EXE (hard to handle!) at all? If it is about the deployment process, you know that you can provide a single MSI (Microsoft Installer) with all required components using the TestStand Deployment Utility?
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Can labview call a test stand module

Having problems with a test dll that runs in test stand, but I get errors when trying to use the wizard in labview, however I can use the call library function node to protypye it. Problem - the function openComserialPort(char* comPort, ErrStruct & err), how do you difine the parameters for the ErrStruct & err part.
next Question, since this Dll runs in Test Stand, is their anyway to export to work in LabVIEW.
Solved!
Go to Solution.

Here's a description of the dll, to start off, I have a circuit board with a microprocessor on it, that has control for a radio module. During test I need to program this board serially through its' TX and RX lines on the processor. The dll given to me, which was written for test stand, has functions to enable me to do this programming. There are basically 11 function contained is this Dll.
Initialize Dll, (no errors),
open serial port, (no errors),
getStandardTable, which sends a command for the microprocessor to send back its information-> get assertion error
WriteHardwareVersion -> Sends the version and revision number -> assertion error.
ColdStart -> Which resets board statistics variables -> assertion error. Now, this function prototype is ColdStart (errStruct & err); So I prototype like I did for the above error struct, but still got an assertion error, which leaves me to believe, that , or vendor, has a bug communicating, or sending the commands via serially, to test this, I could use the serial examples contained in LabVIEW, however I don't know the command set of the microprocessor, or could there be something else wrong, Any ideas will be appreciated.

Show LabVIEW VI Front Panel When Sequence Step Called

Hello,
By clicking on the “Show VI Front Panel When Called” checkbox in the Step Settings pane displays the LabVIEW VI Front Panel for approximately 100 milliseconds. Is there a configuration way to display the VI front panel for a longer period of time, during that step execution, and allow the user to control the duration of the front panel exposure by clicking to resume execution of the sequence file at their will?
Thank you.
Solved!
Go to Solution.

Hi,
You will need to have some sort of structure in your VI for handling front panel response, otherwise you front panel is only going to be visible for as long as it takes to execute an return back to teststand.
But remember, once you hold your step within that VI which is waiting on the operator to eventual close it, your Sequence will be held as well and if you are expecting steps to continue running after your VI then you will have to consider running it in parallel to your main test sequence.
You may also need to consider what happens if you want to terminate your Test Sequence, how do you close your VI.
Check out 'Strategies for Terminating or Breaking Sequences' in the following.
hope this is of help
Regards
Ray Farmer

Linking Labview Conrtrols to Test Stand Parameters

I am trying to run a Teststand sequence from Labview. I was able to link all the necessary Teststand controls like Open sequence, execution display, Test UUT using the connect command invoke node. However, I am having difficulty linking labview controls to the sequence Parameters found in the sequence context. Any help on this will be appreciated.
Thanks,
Sam

Sam,
As I mentioned before, UI Messages is how you would do this. Essentially, what you would do is send a UI Message from the sequence and then handle that UI Message in the operator interface in a callback. For instance, say that you want to know the number of loops to iterate as a setting on your operator interface. You would send a message from your sequence named say "Give_Iterations". In your operator interface, you monitor the UI Messages and when you see a message that says "Give_Iterations", you can set some value in your sequence context as a response to the message.
Here is an example of this type of callback:
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=04A24417FF0933A2E0440003BA7CCD71&p_...
For general UI Message information, you can check out our developer zone documents on UI Messages located here:
http://zone.ni.com/devzone/devzone.nsf/webcategories/5D2CDEB27E67D8378625681900729242
Hope this helps!
Message Edited by AndrewMc on 09-12-2006 01:26 PM
Thanks,
Andy McRorie
NI R&D

Test Stand Sequence Example - OverrideSerialNumForParallelModel.Seq Bug with Socket Index Report?

Hello - is there a way to have the testand sequence "OverrideSerialNumForParallelModel.Seq" give the reports correctly with the "Test Socket Index" Correctly at 0,1,2,3 instead of each window haveing 0,0,0,0
I've spent a long time trying to get it to work with my applciation -but can't seem to find the answer.
OverrideSerialNumForParallelModel can be found at:
\\Examples\ProcessModels\ParallelModel
Many Thanks
brad
Brad Whaley
LabVIEW Certified Engineer
Attachments:
parallel-bug-testsand-report-index.jpg ‏156 KB

Hi Brad,
The reason that all of the report view tabs are displaying the same socket ID is that you are currently generating a single report file for all of your test sockets (the default behavior), and this same report file is being displayed for all of the sockets. You will notice that if you scroll down in any of the reports, results for all of the other sockets will be present. If you would prefer to have a separate report file for each test socket, you can enable the New UUT Report File for Each Test Socket report options as shown below.
Let me know if this does not fix the problem for you!
Al B.
Staff Software Engineer - TestStand
CTA/CLD

Interested in finding out about using LabView in Networking Testing applications.

Networking Testing applications, such as:
- General Ethernet and POS testing
- BERT
- RFC2544 back to back, Frame loss, Throughput
- RFC2285
- IP Multicast
- QoS
- Load Balancing
- Wireless IP
- BGP
- Other Networking testing

LV provides a lot of tools which make VIs remotely communicate and control through net easily,such as VI server ,datasocket,tcp/ip,opc etc.I do not have much experiences in the environment you decribed,but in the internet and general ethernet programming with LV is very easy and interesting.

Updating the result from Labveiw to Test stand!

Hello, I
have a quick question; i am using Labview 8.5 & Test Stand. I am
develeoping Test Scripts using Labview for the design & using them in
Teststand as PASS/FAIL tests. My question is when i run the tests in teststand
its showing that the tests what i have written in labview has been passed but
when i remove the connection to UUT & run the same its showing that tests
are passed. Actually at this time it should show that the tests are failed
since the connection to UUT is not present. But on the lab view window its showing
the proper result(that the is failed due to to bad connection) but on the test
stand window side its showing erroneous results i.e. tests are passed(i.e. the
result is not being updated from lab view to test stand window). What should I do to
update the result from lab veiw to testand . I have this problem from couple of
days.
Any help
would be appreciated.
Thanks.

Hi basha,
Looking at your Sequence File and the Pass / Fail Step in MainSequence.
Although you have three connections on your VI FT_Open_Device_By_Sreial_Number.vi (one input, two outputs),
within your step, you haven't connected them to any TestStand variables.
I have attached the FileGlobals.Handle to the Handle output of your VI as an example.
You need to do something similar for Device Serial Number and FT_Status.
I am not sure where this top level vi comes in, are you hoping to replace FT_Open_Device_By_Sreial_Number.vi with this top level vi.
If you are then you need to connect on input and output to its connector pane. I would suggest the boolean result is one of the ouptut
Which you connect to Step.Result.Pass/Fail
Regards
Ray
Message Edited by Ray Farmer on 03-10-2008 10:04 PM
Regards
Ray Farmer
Attachments:
vi.PNG ‏25 KB
Specify Pass_Fail.PNG ‏24 KB
top level.PNG ‏6 KB

Can I use NI TestStand for testing ZigBee and Bluetooth transceivers and processors

Hi , I should create , maintain snd excute software test plans for testing low power wireless networks such as ZigBee, Bluetooth using Python scripts and QA Methodology .The test design includes testing
RF transceivers, RF transmitters, RF receivers, System-on-Chips, Front Ends, ZigBee Processors, Bluetooth LE Processors, and RFID reader
I am a LabVIEW Developer and familiar with testing RF Components using NI Hardware such as PXIe system but I am new to TestStand and Python. Can I use Teststand to develop and deploy the tests for this purpose and also LabVIEW instead of Python
If it is possible could you please let me know that are the advantage and disadvantage of using LabVIEW and NI Test Stand for these kind of test design and implementation.
I greatly appercaite your help and advice on this matter .Many thanks.

Hi en99,
I am unsure what you mean by usign LabVIEW instead of Python - what part of the system would LabVIEW replace? Usually if you were using Python in automated test, it would be to handle the test processing, which in this case is done by TestStand.
As for advantages of TestStand over LabVIEW, the main one which SunRS mentioned is that TestStand has a test management engine, which covers result logging and passing test parameters to the various test modules, which can be written in many languages. As I mentioned above, it is Python which is commonly used to write alternative test managament engines. It is possible to write one in LabVIEW, but for good results it must be carefully architected and is typically a very time-consuming task if you want to keep it modular and use it for other applications. TestStand also has a number of built in tools which help to monitor various aspects of the test sequences, as well as provide multithreading optimisations.
I hope this helps

How to test cloned VI file from Test-Stand

Hi All,
I am having one doubt in Test - Stand.
I am having VI file which is having four controls and four indicators. I am just connecting one control with one indicator like one - one mapping. I have created connector pane for this. Say save this file as dummy1.vi.
In another VI file I have taken four controls. These controls are connected with dummy1.vi file. Save this file with test1.vi file. Now run the test1.vi file with highlight execution on. While it is continuosly running, double click on the sub vi files. You can see different files with clone, clone1, clone2 ...etc...
Now I will pass values to test1.vi file from Test - Stand sequence step. In second step I want check the result from dummy1.vi file. But I am unable to do it.
Can anybody tell me how to achieve it?
Regards,
Nagaraju

Hey NagRaj,
The reason you see the clones is because your VI is reentrant. You can change that in the VI Properties in the Execution section. Also, you may want to read more about that in the LabVIEW help to understand it better.
You should have no problem testing these VIs from TestStand if you set your Step result to the value you are testing against. I've attached an image that shows how to set the outputs of your VI to the step results. What kind of test are you doing? (i.e. NumericLimit, StringLimit, Pass/Fail etc..)
Is dummy1.VI a subvi of test1.VI? If so do you have the output terminals of dummy1.vi connected to the output terminals of test1.vi to propogate the values back to TestStand. This is assuming you only have one step in TestStand calling test1.vi which has dummy1.vi as a subvi.
If you want two steps where one step calls test1.vi and the other calls dummy1.vi then you have to call them seperately. They can't be tested in the same step this way.
If this is confusing you can always post your simple example (seq and vis) and I could look and see how to better assist you.
Regards,
Message Edited by Sam R on 02-28-2007 09:06 AM
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~
Attachments:
stepresult.JPG ‏56 KB

Can I open the (.squ) sequence files using NI test stand 4.0 version?

I have the sequence files created using ATETool Kit test Executive. But I have NI 4.0 test stand. I want to open the sequence files using NI 4.0 test stand. Can i do that?

Hi,
I am not familiar with ATETool kit Test Executive, but I doubt NI TestStand will open this. As you have both, have you tried it?
TestStand does have a conversion tool for converting NI TestExecutive sequence files into TestStand sequence files.
Maybe you could write a conversion tool to make the conversion for you if you have many ATETool kit Test Executive files.
Regards
Ray Farmer
Regards
Ray Farmer

How to call test Sequences developed by using CVI Test Execuitve toolkit in Test Stand?

There is a feature in TestSatnd which can convert CVI sequence to test Stand Sequences. But test stand is not recognising these sequences saying " not a valid CVI test sequence". Is there any version Issues, while converting these sequences to TestStand?

Hi Scott
In continuation of previous question..
As per the suggestion, when I am trying opening one sequence(.SQU) file,developed in CVI Test Executive V 1.0.1., in CVI Test Execcuitve V 2.0.1, Executive is throwing error.
The Pop Error is " Section [Sequence] missing from sequence file c:\xxx.squ"..
and when I am trying opening these sequence file in sequence editor, the tool it self is crashing.
Please suggest!!
Is there any specific tokens which we need to add in .SQU files of V 1.0.1, so that V 2.0.1 can understand them? Just to check the possibility of manual updation of .SQU files.
Regards
Amit

Type List Order Numbers (typelistordernum) change when opening a sequence file in Test Stand

Could you please shed light on the reasons a sequence file changes upon opening in the Test Stand development environment?
Comparing the file before and after, I see that the typelistordernum changed on a few custom types that we defined for the program. .
To clarify the environment, I am using two work stations running the same version of Test Stand. The workstations are kept in sync using Sugar Sync. One would expect that a file saved on one workstation could be loaded on the other work station with no change.
This also happens on files that we pull from version control (GIT). Once opened, they change, which presents a serious problem in avoiding version conflicts and keeping track of real changes.
Test Stand Version: 4.5.1

ATE Coder wrote:
In fact it turns out that conflict resolution is fairly hard to resolve.
For instance, changing a type (add a comment) changes its time stamp. As a result, all sequence files referring to this type are now in conflict.
On testing, Test Stand does not seem to flag these. So, they could be pushed into the repositories as is.
Opening the sequence files on another machine (after pulling to code from repositories), Test Stand detects a conflict that in fact is no conflict at all. Now all these files need to be checked in and pushed up and then pulled down. This increases the chances of code conflicts many folds and seems to be totally superfluous.
Turning off automatic conflict resolution does not seem to resolve this issue.
It would seem that for some reason (inertia?), NI pulled into Test Stand the same tight versioning it uses in LabVIEW. While in LabVIEW, where, in fact, one is editing compiled code, thins might add some value, Test Stand sequences are actually XML file -- source code, which call for a much more relaxed code versioning or none at all as making sure the code works as part of the debugging process and cannot be handled properly by 'versioning'.
I think you might not be using automatic conflict resolution the way it is intended.
Are you using type palette files? If not, I highly recommend you do so. If you put the highest version of your types in a type palette file, use the default automatic conflict resolution settings, and distribute or deploy the type palette file to everywhere where the type is being used, you do not have to resave all of your sequence files everytime the type changes. Sequence files with older versions of the type will be automatically updated when they are loaded on machines that have the latest version in a type palette. This is what automatic conflict resolution does, it automatically/silently updates the types in the sequence files when they are loaded. No need to resave everything before hand. If you have trouble getting this working, let me know exactly what you are doing and what problems you are having and I will hopefully be able to suggest an alternative way of managing types that will not have those problems.
Hope this helps,
-Doug

Using Testexec user interface with test stand

Hi,
I want to use the testexec UIR (from cvi) with my Test Stand sequence. My goal is when this operator interface is opened directly, the specified sequence opens automatically.
Any suggestion!
Best Regards,

You can approach this 2 ways:
1- Hard code the name and path of the sequence file into the CVI code and rebuild testexec.exe.
2- Associate .seq files with testexec.exe such that when someone clicks on an .seq file it opens in the UI. Then place a shortcut to your sequence file on the desktop and have users start it by clicking on that.
I recommend 2.
As a side note: By default a UI will open the last sequence file that was opened.
Regards,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Creating TestStand GOTO step programatically using LabView. Problems.

Hi
I am trying to programatically create and configure a TestStand GOTO step, using LabView. I can create the step fine, but I cannot work out how to specify the GOTO Destination.
Has anybodt got any ideas?
Regards
Steve
There are 10 types of people in the world that understand binary, those that do and those that don't.

Managed to solve this one myself by setting the CustomActionExpr to 'True' and the CustomTrueActionTargetByExpr to the name of the step I wanted to jump to.
Steve
Message Edited by SercoSteve on 01-24-2006 02:13 AM
There are 10 types of people in the world that understand binary, those that do and those that don't.

Using labview global in test stand sequence steps

Similar Messages

Maybe you are looking for