Testand CloseAllSequenceFiles

Hi,
I try to use the CloseAllSequenceFiles method but I have a problem.
When I close the Operator Interface of TestStand, it keep in memory the sequence loaded and re open it at next execution of the Operator Interface. (I'd like the interface to be empty at opening!)
So I try to use the CloseAllSequenceFiles, CloseAllExecutions and Shutdown methods when I close the Interface. But the sequence is re opened anyway...
Somebody can help me?
my source code :
// The ApplicationMgr sends this event when it is ok to exit the application
HRESULT CVICALLBACK ApplicationMgr_OnExitApplication(CAObjHandle caServerObjHandle, void *caCallbackData)
VBOOL bShutdownReturn;
int error = 0;
TSUI_ApplicationMgrCloseAllExecutions(gMainWindow.applicationMgr, &errorInfo);
TSUI_ApplicationMgrCloseAllSequenceFiles(gMainWindow.applicationMgr, &errorInfo);
TSUI_ApplicationMgrShutdown(gMainWindow.applicationMgr, &errorInfo, &bShutdownReturn );
return S_OK;
Solved!
Go to Solution.

Hi,
The OperatorInterface doesn't open a sequence file upon launching unless
1) You have Customised the Operator Interface
2) You are passing a command Line argument to testexec.exe or seqeditor.exe (see table 8-6 of the Reference Manual)
What Teststand are you using.
Regards
Ray Farmer
Regards
Ray Farmer

Similar Messages

What is a String in Testand

I need to pass Strings to and from a dot net dll from testand.
The String could be a Testand "String" or a dot net "String",
Or a proper string (array of char).
It doesnt matter.
I require some mechanism for getting an array of chars from my dll to a result "String".
Cheers

Hi,
If you are needing to pass an array of chars from a dll to TestStand. you can retrieve this array as a string in TestStand. The example located at: C:\Program Files\National Instruments\TestStand 3.5\Examples\AccessingArrays has a step called "Get String Array" that shows how to retrieve this array of chars in TestStand. Take a look at this example and let me know if you have any questions.
Thanks,
Terry S.
Staff Software Engineer
National Instruments

Testand : Database Options : Schemas for Multilple Numérique Limite Test

I'm looking for a Testand Schemas (Database Options)
which store at each step (MultiNumeric) multi values
on multi lignes on the modele of STEP_NUMERICLIMIT
ex : N mesures -> N NUMERICLIMIT lignes in BDD

To PMR Christoff -
The default schemas for TestStand 2.x and 3.0 already log generic step result information to the STEP_RESULT table and individual measurement results for the MultiNumeric Limit Test to the MEAS_NUMERICLIMIT table. Can you explain how the default schema is different than what you would like the database logging feature to do?
Scott Richardson
Scott Richardson
National Instruments

Lenteur testand et labview

Bonjour,
Voilà mon pb, j'utilise le séquenceur testand pour mes tests, codé en labview (vi)
Mes tests sont très rapide et tout va bien
J'ai donc installé ce soft avec une ihm pour les utilisateurs
Le pb c'est qu'au lancement d'une séquence de test, teststand lance labview et c'est long, plus long que mes tests....
donc il faudrait pouvoir lancer le moteur d'execution de labview (pas l'environnement de développement) a l'ouverture du pc
je ne veux pas que les utilisateurs puissent modifier mes vi donc aucun accès à l'environnement de développement
je suis sûr que je suis passé à côté de quelque chose...
D'avance merci
Résolu !
Accéder à la solution.

Bonjour melkior,
La réponse à votre question se situe dans la partie 3 du document suivant : http://www.ni.com/white-paper/9923/en
Il suffit de modifier la configuration de l'adaptateur LabVIEW en allant dans Configure >> Adapters sous TestStand - cela vous permettra de choisir le moteur d'exécution LabVIEW au lieu de l'environnement de développement.
Cordialement,
Celine
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées Techniques LabVIEW
Du 15 octobre au 7 novembre : Strasbourg - Lyon - Lille - Toulouse - Mar...

Pilotage d'une carte PCI par Testand

Bonjour.
Dans le cadre de mon travail, on me demande de lire les entrées et de piloter les sorties d'une carte NI PCI 6514 par Testand.
Or, je n'ai aucune connaissance sur ce sujet (je connais un peu
testand mais pas la manière de réaliser le pilotage) et personne dans
mon entourage professionel ne semble être à même de m'aider, m'expliquer
ou me former.
Serait-il possible d'avoir ne serait-ce qu'une marche à suivre, ou n'importe quelle direction à suivre.
Merci
Cordialement.
PS. Ce sujet a déjà été posté dans le fil de discussion sur "Testand". Merci ausx modérateurs/administrateur de le supprimer.

Bonjour,
L'appel de DLL est très facile avec TestStand et les fonctions DAQmx assez simples a utiliser. J'ai deja programmé une acquisition continue via les macros Excel en appellant les fonctions des DLLs DAQmx donc rien ne vous empeche de le faire sous TestStand.
Démarrer » Programmes » National Instruments » NI-DAQ » Text Based Support » NI-DAQmx C Reference Help
Voir meme avec les assembly .NET
Cordialement,
Da Helmut

Pilotage carte PCI 6514 avec Testand

Bonjour.
Dans le cadre de mon travail, on me demande de lire les entrées et de piloter les sorties d'une carte NI PCI 6514 par Testand.
Or, je n'ai aucune connaissance sur ce sujet (je connais un peu testand maias pas la manière de réaliser le pilotage) et personne dans mon entourage professionel ne semble être à même de m'aider, m'expliquer ou me former.
Serait-il possible d'avoir ne serait-ce qu'une marche à suivre, ou n'importe quelle direction à suivre.
Merci
Cordialement.

Hi,
You will not be able to drive your NI PCI 6514 directly from TestStand.
You will need to write some code modules in either LabVIEW or LabWindows/CVI or one of the other supported languages by TestStand.
You should beable to find examples provided in the language of your choice which will get you going to drive the card.
Hope this helps
Regards
Ray Farmer

Listing Step Fields of a Testand application.

In my Testand application I created my own step type. This step type has several containers (see picture1).
Using LabVIEW I would like to launch a VI as a substep pointing on the
step and listing the containers ( and controls inside thesecontainers)
using an ActivX pointer on the Testand API.
This basically works : This Context reference is passed to my VI as a
sequence context and I can then have a refrence on my step and have its
properties (see picture2)... But I can't find a way to list its
containers (Params in my app).
Can somebody help me ?
Attachments:
picture11.jpg ‏13 KB
picture21.jpg ‏11 KB

Hi man,
Why not using the VI get property value or the property object class to recover the properties of step...
You have to use the Lookup string to specify which property you want to recover...
Kamal
NIF

Testand will not convert my labWindows CVI sequence file to a TestStand sequence file.

Testand will not convert my labWindows CVI sequence file to a TestStand sequence file.
Attachments:
ACC3.squ ‏3 KB

If you are using an older version of the CVI Test Exec toolkit, check with your local Field Sales rep to see about getting the necessary software to use for temporarily upgrading your existing Test Exec sequences to version 2.0 for migrating to TestStand.

Hide Label step icon using Testand API and LabVIEW

Hi,
can anyone tell me how it is possible to hide the icon of a label step using Testand API and LabVIEW?
In the Teststand Sequence Editor, on the Label Edit Tab there is a Checkbox called "Hide Icon". Is there something similar in the API?
Thanks
Solved!
Go to Solution.

Yes you can, you will have to set the IconName property of the step to "ni_blank.ico"

Testand: Vitesse d'exécution de NI-Testand

Bonjour,
Voilà depuis que je suis passé à la version 4.5.1 de NI-Testand, mais séquences s'exécutent lentement, pas à la vitesse voulue. J'ai donc la plus part de mes tests qui se retrouvent Fail à cause ça.
J'aimerais savoir comment augmenter la vitesse d'exécution d'une séquence sur NI-Testand ?
Merci d'avance.

Bonjour,
L'option Disable tracing (désactiver la trace) va augmenter significativemment la vitesse d'exécution.
Cette partie du forum est en Anglais au passage...
Cordialement,
Rodéric L
Certified LabVIEW Architect

Webservice using Testand.Engine

Hello,
I would like to write a Webservice that monitors my Teststand on demand.
The service should be done in C#
Here is my Question:
Is it possible to access the running Engine ?
greetings
Juergen
=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=

As the TestStand Engine is always loaded only once, there is no expicit method in the API to attach to a running instance, but if you create a new instance of the Engine class, it should be connected to a already running instance of TestStand.
If you ar using TestStand 3.0 or later, you could use the "Application Manager" Object, and call the method "GetEngine" method. this will give you a Refereence to thr running TestStand Engine as well.
Hope this helps!
André

User Interface on Testand

Hello everybody,
I'm new to teststand and have been reading through "Using Labview with Teststand". I want to create a user interace using a Labview VI, specifically I'm trying to use the dialog box. It should ask the user for a number of inputs, e.g. checkboxes and buttons
The manual states " for a demo of how to use these functions refer to <Teststand>\Examples\ModalDialogs\Labview.". There is a teststand project called modal dialogs in this folder. Does anyone know how to use it.
Also is this the correct approach or should I use labwindows. The manual is pretty much useless after chapter 5 to a beginner like me!
TIA
Sean

Hi Sean,
Try opening the TestStand Sequence Editor (Start»Programs»National Instruments»TestStand x.x»Sequence Editor). From here you can open the sequence located in the examples directory (<TestStand Examples>\ModalDialogs\LabVIEW\LabVIEWModalDialog.seq). Upon opening this sequence file, you will see a dialog that pops up, explaining the purpose of that example. From here, you can execute the sequence (Execute»Single Pass) to see the behavior of using a LabVIEW VI as a modal dialog to a TestStand execution.
Creating a user interface that allows your user to determine the flow of execution is a good use case for a modal dialog. Another good example to see is the Computer Motherboard Test Example (<TestStand Examples>\Demo\LabVIEW\Computer Motherboard Test Sequence.seq). This more advanced example shows a testing sequence whose execution flow is determined by user input on a LabVIEW dialog.
I would also highly recommend looking at this post for good information to new users. Also, keep in mind that the best way to learn TestStand is through an NI TestStand Course.
I hope this helps you get started!
Evan Prothro
RF Systems Engineer | NI

Vision Builder 2010 Active time not working when calling Vision inspection from testand 2010

I have an issue where I am timing a flashing light using the active time variable, when I run the inspection from the inspection view everything works, however when I run it from the configuration view or by calling it through teststand 2010 with the Vision Vi's the Active Time never changes from 0.00000.
I do not need precides timings so I am NOT worried about the +/- 20ms from the windows system clock.

Hi Ryan,
Can you read any of the other variables using the Get Inspection statistics VI? Is it only the Active Timer that doesn't change?
Cole R.
National Instruments
Applications Engineer

References permanents labview 7.1 testand 3.1

Hi everybody:
I want to syncronize Test Stand 3.1 with Labview 7.1 by the use of queue et notification.
I have a VI that executes differents process in agreement with the queue value enter in TestStand and when it executes the methode of dequeue it also generates a notification in order to inform Test Stand that it has finished its task and TESTstand could continue with the next step.
I open the Labview in one step of the setup main sequence and I want to use this VI in the steps of main part, the problem is that I couldn't finish the first step while my VI is opened(the VI has a boucle that finishes when TESTSTAND send a queue "CLOSE VI"). If I close the VI, I lose the sequence context reference.
What I should do, since I need that the VI would be shown during the test execution and also that the VI should be an exe that could be called and controlled directly by an user?
Thanks so much
Vanessa

Thanks,
I find the solution
Vanessa
PS: I've just to configure the call step sequence which opens the VI , in edit sequence call- the Multithreading and Remote execution option as "Run Sequence in a New Thread"

Testand write to database only with 'On the Fly'

I'm writing all results to an Access database.
But results are written only if 'On the Fly' is set.
Why?
Ofer

Hi Ofer,
When writing to a database, as I'm sure you know, on the fly will write all of your results during sequence execution. That said, all of your results should be written at the end of the execution at the LogToDatabase callback if you do not have on the fly checked. This behavior is built-in to TestStand, so if it is not working, it generally means that something on your TestStand system was changed.
Have you altered your sequence file or added any callbacks to your sequence file? What process model are you using?
I would suggest setting a breakpoint at the LogToDatabase callback and stepping through the code to see what is called. I believe this will put us on the track towards a solution.
Regards,
Matt M.
NI

Testand CloseAllSequenceFiles

Similar Messages

Maybe you are looking for