Running a teststand seqwunce from labview

HI all
I want to build a user interface in Labview to execute number of sequences in teststand.
I already had a look at the examples shipped with TS. But in my case my UI will be different that the default UI of teststand.
I want user to select number of sequences(at one time from list box or tree) and then when clicked on execute button , one by one each sequence should get executed.
For this I need provide seq file path to the invoke/property node before execution. But I am not able to find the current method/property for the same.
Can someone please help on this?

By this method you can do the following ( no need to change User interface code -- use the default one ) :
1) A (Main GUI.vi) vi when executed calls a predfined master sequence to automatically open and run in TestStand.
2) This predfined master sequence uses a vi to get sequences ( simulating user selected sequences)
3)The sequences selected are stored in a TestStand string array and run one by one.
4)TestStand is automatically closed in the end. ( no user intervention is required)
Setup :
1) Unzip the files and put it to c:\temp\LVUSER1 ( This path is hardcoded in vi and testsequences )
2) Go to TestStand menu --> configure --> station options -> user manager and enable automatically login windows user
3) Create a new user with windows credentials in TestStand using the user manager.( This is to avoid login popup)
4)Enable report in TestStand if you need a report.
Run :
Run the MAIN GUI.vi
Changes if required :
1) I have copied CVI user interface from C:\Program Files (x86)\National Instruments\TestStand 4.2.1\UserInterfaces\Full-Featured ( This is because i tested this in )TS 4.2.1
Feel free to copy any of the user interfaces that you are familiar with from the respective TestStand folder.
2) Correct the paths if required in vi and test sequences.
Hope this example will be helpful to you.
Regards,
Ravi
Attachments:
LVUSER1.zip ‏469 KB

Similar Messages

Opening TestStand Ref from LabView sometimes fails

I'm having an intermitten problem when opening a TestStand reference from LabView. The error explaination just says, "LabVIEW: (Hex 0x80004005) Unspecified error." Attached is a little vi that can reproduce the problem when set to run continuously.
Any idea on how to fix this? Thanks a lot.
Note that because of compatibility requirements I have to use TestStand 2.0 with LabView 7.1.
Attachments:
TS_Ex.vi ‏24 KB

Attached is a screen shot of the error message. This is one of at least 2 error messages. I will get the other one when I can get time on the equipment. Right now, I would like to get the error log (mentioned in the screen shot), but I can't find it. Where should it be?
Unfortunately, the equipment is being shared and I haven't received time to debug it more. But this is what I have seen.
Trying to Highlight Execution with breakpoints seemed to point the vi closing the reference to TestStand as the source of the error message. Using the Simplified TestStand Operator Interface vi that came with TestStand, and some fake tests, we did not have this error. Only when we use our customized OI with dynamic test sequence generation do we get the error. This error doesn't occur with LabView 6.1. So I think it may be another incompatibility between LV 7.1 and TS 2.0.
Thanks for your help.
Attachments:
Exit-Crash-1.doc ‏24 KB

Run DLL in C++ from Labview

Hi the world !
Ive got a pb in labview when I call my DLL or in VB6 when I build my DLL.
Join my project... what do you think about my pb ?
thanks for help !
Ben.
Attachments:
LancerDLL.zip ‏35 KB

candidus a écrit:
OK, I got your gift :-)
It's pretty useless to use new[] inside your function, static arrays will do it.
The question is, how does your caller allocate the arrays?
It's a bad idea to use operator delete[] on arrays you given as parameters:
You should allocate them, call you dllbeta1() function which shouldn't modify these parameters
and deallocate them in your caller function.
I can't look into your VI, I don't have 8.6 but since we're in a LabVIEW forum
I assume you want to call your DLL from LabVIEW.
LabVIEW has its own memory management
which doesn't just use new[]/delete[] so you shouldn't modify strings in your DLL unless
you're familiar with the memory management functions in "extcode.h".
And be careful to use the right calling convention: __cdecl or __stdcall
Calling convention is __cdecl.
My dll doesn't modify these parameters... just uses for functions.
Have you got a solution for me ?
thanks

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~

Add limits to step settings via TestStand API from LabVIEW

Dear LabVIEW and TestStand Community!
I'm trying to add FileGlobal Variables as limits to TestStand step NumericLimit programmatically, via LabVIEW, via TS API. I attach screenshot of the code, which I use (part of it - the module, which only sets values to low and high limit of the step), and also I attach, what I manage to get.
In TS, when I open sequence file, after running of the code, I can see in the description line of the test, that it accepted limits, which I set from LV - you can see it from the screenshot, it is marked with yellow. But in the Tab "Limits", there are still default numeric values, not FileGlobal Variables.
Could anyone explain, what doest it mean, and how to set up them correctly?
Thanks a lot in advance!
Solved!
Go to Solution.
Attachments:
Limits.PNG ‏33 KB
Add Limits.PNG ‏15 KB

It's kind of sequence generator what I'm doing now...
Thank you very much for fast reply, but when I setup "UsexxxExpr" to true, it doesn't change the situation... Could you, please, check my attachment? Maybe, some mistake in syntax?
Attachments:
Add Limits.PNG ‏23 KB

Excecutable VI generating an error 222 on Keithley 2612A although its run properly when starting from labview 2009 directly

Dear all,
I have a VI which runs perfectly and I can control, a Keithley 2612A for transistor measurements.
The VI run well when I excecute it from the computer which has the platform Labview 2009 (XP OS)
The equipment (ie Keithley 2612A) is linked to another computer which don't have labview 2009.
I installed Run-time-engine 2009 (OS XP 32 bits) on this computer.
Then I create an excecutable of my VI with the "build application" option.
The excecutable VI starts normally on the computer but when I want to run it, I am getting an error message from the Keithley 2612A (which was not the case when I ran the VI directly from the computer haing Labview 2009 installed on it). The error message is 222 (ie parameter too long)
I thought that I did something wrong and I create an excecutable from an original VI from Keithley (ie without any change). I am getting the same error message.
When I create an excecutable with run time engine 2009 included (as it is possible to do it wiht LB 2009) , I am geeting the same error message.
So I need no to check step after step when the message happens but
Does anyone knows anything about such an issue ?
Thank you
Solved!
Go to Solution.

Dear all,
Just for those who might encounter a similar issue.
I found the solution after tackling all possibilities.
The source of the problem was (for unknown reason) that the country setting of the computer was wrong
and decimal numbers were written with a , instead of a point.
Since I reset correctly the country setting, the stand alone files are running normally.
Best regards
Youki

My computer is crashed after 3 hours, when am running an Executable file from LabView 6.0.2

My VI is using DAQ6025e and GPIB cards, it is countiniusly writing data to files and talking with 2 GPIB instruments and one Serial instrument. Sudenly after 3 hours of perfect working it is crash my computer.
Does any body know why ??? Help? S.O.S?

Some questions to help us troubleshoot:
1)How crashed is your computer when it crashes?
Blue Screen Of Death crashed? If you don't know about BSOD then that
is when your computer presents a blue screen (white in XP) and tells
you that the system is halted, gives you a register dump and the
memory address where it stopped (all of which is useless unless you
are an assembly language wizard) and then you have to reboot the
machine.
Application error that kills LabVIEW.exe? Usually a pop-up MSGBOX
style dialog box will appear with a such and such error occurred in
LabVIEW.exe or another application and an OK button.
VI Slows to a crawl w/hourglass in the app window? Program doesn't
stop executing, it just stops responding to user inputs.
LabVIEW error cluster error that causes the VI to quit?
2) What O/S are you running? Win 3.1, Win 95, Win 98, Win NT 3.1, Win
NT 3.5, Win NT 4.0, Win2000, WinME, WinXPHome, Win XPPro?, Linux?, Mac
O/S?
In the Microsoft family, WinNT and Win2000 are by far the most stable
and reliable of the various versions of Windows with Win95 and Win98
having a lot of problems running for long periods of time. Make sure
that you get WinNT 4.0 updated to service pack 6 if you are still
using 4.0 but haven't updated the service pack level yet. There were
quite a number of problems with it when it first came out that have
since been cured.
3) Have you run the LabVIEW VI profiler yet? This will point out
memory leaks that are due to dynamically built arrays using shift
registers etc. or appending to strings, or improper IMAQ management,
etc.
4) Have you brought up the task manager and looked at the memory
allocated for LabVIEW.exe and for the whole system as well? Is it
growing? Sometimes there can be memory leaks that don't show in the
profiler that will show in the task manager when you look. These can
be due to bugs in LabVIEW itself or some driver for some hardware you
are using, etc.
If you are not running NT or a later derivative, then you won't have
task manager available but you can get diagnostic tools that are very
similar to task manager from off the web.
5) How much memory do you have in your PC? How fast is your PC? What
does the CPU % usage look like under task manager when you first start
your app? If it is running >40% CPU usage for any significant amount
of time at the start then perhaps your PC is overloaded with work and
you need a faster PC or your code needs redesigning. I like data
acquisition systems to operate <25% generally speaking. This number
seems to improve the reliability of the code that is running on them.
6) How much H/D space is available? You say you are writing data to
files. Your h/d space isn't running out is it?
7) Is it possible to run one instrument at a time for several hours to
see if it is a particular instrument that is causing the crash? Make
sure that your GPIB cards are properly configured so that they don't
share resources with any other devices(IRQ, DMA, memory addresses,
etc.) It may be possible that they behave fine most of the time even
with shared resources but if they ever try to send a command
simultaneously and they share resources, they could "collide" and
crash your PC. You can check all this out in the control panel and/or
MAX.
8) Is it possible that your serial port is getting hung up after
running a long period of time? Serial port UARTS are notoriously
finicky especially over longer line lengths and higher data rates. It
could be that your serial instrument is locking up your app or your PC
serial port is locking up your app and causing the crash. Can you put
a serial port analyzer in between your serial instrument and your PC
to see what's going on when it crashes?
9) Are you trying to read or write to the serial port in more than one
thread or while loop or dynamically launched vi? If you are you MUST
protect the serial port access with a semaphore or a VISA resource
lock. You CANNOT use a boolean global to protect access. Regular
globals aren't atomic and you can have race conditions that result in
unintended serial port collisions between differen threads. I have
seen this lock up multi-threaded serial programs before to the point
of requiring rebooting.
This problem can be especially frustrating if you haven't done
multi-threaded before. The port won't necessarily lock up right away
or at the same time every time. You MUST make sure that serial port
access is limited to ONLY ONE execution thread at a time.
10) Is there another application or service running in the background
with your application that may be trying to access the serial port or
GPIB cards when you aren't expecting it? This could cause a collision
that could crash your system as well.
Douglas De Clue
LabVIEW developer
[email protected]
Yan wrote in message news:<[email protected]>...
> My VI is using DAQ6025e and GPIB cards, it is countiniusly writing
> data to files and talking with 2 GPIB instruments and one Serial
> instrument. Sudenly after 3 hours of perfect working it is crash my
> computer.
> Does any body know why ??? Help? S.O.S?

Write teststand globals from labview

Hi all,
i just started using teststand and i am not too familiar with the program up to now.
What I want to do is, writing teststand station globals from a vi that i started asynchronously. What steps do i need to execute in teststand before starting the vi? A small example would also be great.
thanks for your help.
Walter

When using instruments in LV code modules, the code module itself presents a lock (default execution setting of LV VIs when not changed to reentrant execution).
So if the instrument is used in a single code module (which is used several times in your TS sequence(s)), there is nothing you have to worry about.
If the instrument is used in multiple (different) LV code modules (by passing its handle from module to module), you might require to include some locking.
I recommend you to provide the lock in TestStand. Use the Lock steptype in the synchronization palette to do so.
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

I get the error code -2146827284 when trying to run an Ecxel macro from LabVIEW.

I am trying to insert data in an Excel workbook and then run a macro which I recorded in Excel to produce a plot.
This worked great on a laptop running W2K + LV7 and Office 2000.
I am now trying to do the same thing on a WinXP + LV7 + Excel 2002 and I get this error.
The complete message is:
"Error -2146827284 occurred at Exception occured in Microsoft Excel, Programmatic access to Visual Basic Project is not trusted
. Help Path is C:\Program Files\Microsoft Office\Office10\1033\xlmain10.chm and context 0 in Excel Import Module.vi->LV report test1.vi
This error code is undefined. No one has provided a description for this code, or you might have wired a number that is not an
error code to the error code input."
Can anyone shed some light on this. Running a macro is the obvious and easy way to get this work done.
See the attached VI. It includes the macro and some sample data to run it on.
Attachments:
LV_report_test1.vi ‏46 KB

Hi,
I have attached a link to a document that discusses the error you are getting:
Error -2146827284 When Importing a Macro to Office 2002/XP
I hope this helps.
Sincerely,
Feroz
National Instruments

Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
ErrorCode: -17600,
Failed to load a required step's associated module.
LabVIEW Run-Time Engine version 9.0.1f3.
When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
My TestStand Engine Version is 2012 f1 (5.0.0.262).
I'd appreciate any help on this issue.
Roman

Hi Roman,
There are a couple of things you can try:
1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
Check if the simple VI is loadable and runs without errors in TestStand.
If the step generates the same error, you should try a re-install of the LabVIEW development system.
If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
    Right-click "Build Specifications" and choose "New->Application(EXE)".
    In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
    Save the properties.
    Right-click on the newly created build specification and choose Build.
Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
Regards,
TRJ

How can I pass in continuous value from labview to teststand?

Hello
I want to run a vi using teststand. I want this vi to send values to teststand. My problem is that the value is only updated at the end of the vi execution and I want to get the value before the end of the vi execution. If somebody can help me ...
Thanks
Corentine

Corentine,
you can think of TestStand calls to LabVIEW-VIs just like functioncalls in C/C++. The main continues running only if the subroutine is fully executed. Furthermore, LV returns values to the parameters (connector block) only at the end of the execution of the VI.
So you cannot use "simple VI calls" in your sequence if you need datatransfer during execution from steps. If you like to do something like this, the easiest way would be to create a VI which runs continuously in the background and supplies data via mechanisms like Queues (if executed in the same instance) or TCP/IP. In the stepmodules you can retrieve the data when needed.
hope this helps,
Norbert B.
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

How do I return a Boolean array from LabView to TestStand?

I am trying to return a Boolean array from Labview to TestStand and have TS evaluate the results. I can do this for arrays of integers or reals but booleans do not work. I tried copying the PassFailTest step type and adding an array of Bool but I couldn't get it to evaluate the array. It simply always passed. How can this be done?
Bob A.

I have thought about evaluating the Boolean data in TestStand but, as you say, this is a lot of work. What I have been doing is to map the boolean data to integers in LV (very easy) and then use the multiple numeric step type to evaluate the integer array automatically. This feels kludgy and I have tried a couple of times to create a "multiple boolean" step type with little success. I'm surprised TS hasn't anticipated a test returning multiple pass/fail results. I do this all the time for production code.
What I have tried is to copy MultipleNumericLimitsTest data type to a custom type and add a BooleanArray with a data type Array of Boolean[0..empty]. Then when I specify module, I select Step.BooleanArray as the value. The last step (that I know of) is to select Step.BooleanArray as the data source in the edit limits window. At this point if I run the test, I get the error "expect numeric, found boolean" (or something similar). When I look at the properties of my custom step type, the Substeps has DoMultiNumericMeasEvaluation as the Post-Step. I believe this is the root of my problem but I can't figure out how to change this to "DoMultiBooleanMeasEvaluation" or similar. Any Ideas?

Change teststand post actions from labview

Hi,
Is there a way to change the post action of a test in teststand from Labview.
At the moment, if one of the tests fail out of limits then the post action is set to 'ON FAIL - GO TO NEXT STEP' but if the unit does not run then a diagnostics labview routine runs and at the end of that I would like to change the teststand post actions to 'ON FAIL - GO TO CLEANUP'
Can you tell me if this is possible
Thanks
Chris

Hi
Yes it should possible.
Step step = m_SequenceContext.Step; if(nValue == 0) {
step.FailAction = "Next";step.FailActionTarget = ""; }
else{step.FailAction = "Goto"; step.FailActionTarget = "<End>";
Regards
Juergen
EDIT: This example Goto Endgroup --Sorry!
Message Edited by j_dodek on 04-21-2010 01:51 PM
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=
Attachments:
DotNet.zip ‏17 KB

Display "About NI TestStand..." from LabVIEW

I'm creating a LabVIEW UI that calls TestStand to run sequence files and I want to include a menu Item to display the "About NI TestStand..." window, but I can seem to figure out to tell TestStand to launch the window from LabVIEW.
Can anyone direct me to the appropriate API call or example?
Ryan Podsim, CLA
BEI Precision Systems and Space Company
www.beiprecision.com
Solved!
Go to Solution.

The Example you mentioned was informative, but I see can't seem to find a way to display the "About NI TestStand..." dialog. The list of commands to bind to menu itemsm via Insert Command into Menu.vi, has just about every item in the TestStand help except the About item.
This is the dialog I'm looking for.
Ryan Podsim, CLA
BEI Precision Systems and Space Company
www.beiprecision.com

I would like to build I data base in teststand which collect data from labview , if you have example (sequence) that give me some way to build sequence

I would like to build a data base in teststand which collect data from labview program , if you have example (sequence) that give me some way to build sequence that have step of action for labview and step
data base

There is an example in the \TestStand\Examples\Database directory. Basically there are two ways to connect to your database.
1. You can use the TestStand database step types. There are steps for opening/closing a database connection, opening/closing an SQL statement, and a step for performing a data operation.
2. The other way is to use the TestStand database logging capability to write your results to the database. This is the way I would recommend. With database logging, you use the step results container to record all your results as the sequence runs. (This is done automatically by TestStand). When the sequence is complete, the process model calls a "Log to Database" sequence that will write the results to the database. You must define your datab
ase schema using Configure->Database Options. There are some default (or example) schema definitions already defined. Refer to chapter 18 of your TestStand manual.
Another way to log the data as the sequence is running is shown in the \TestStand\Examples\OnTheFlyReports. This has the advantage of recording data as it is obtained, but it is not as efficient in terms of using a database connection. I don't recommend using this method.
Please post again if you have any more questions. If you are using stored procedures with your database, I can probably give you some tips.
Mark

Running a teststand seqwunce from labview

Similar Messages

Maybe you are looking for