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...

Similar Messages

CALLING DLL: Labview or CVI?

I'm going to start a new project using Testand and Labview or CVI. In this project I will make a lot of calls to C++ functions packed at a DLL file. The Dll was prepared and compiled using MVC++.The function prototypes are not simple & contain structures, pointers and typdefs's.
Is it possible to call the functions from Testand,Labview,CVI?
Is it easier to call the functions from CVI compared to Labview?
Thanks,
Ofer

ofer_o wrote:
I'm going to start a
new project using Testand and Labview or CVI. In this project I will
make a lot of calls to C++ functions packed at a DLL file. The Dll was
prepared and compiled using MVC++.The function prototypes are not
simple & contain structures, pointers and typdefs's.
Is it possible to call the functions from Testand,Labview,CVI?
Is it easier to call the functions from CVI compared to Labview?
Thanks,
Ofer
Jon already mentioned that CVI will be a lot easier to deal with this than LabVIEW.
BUT!!! Make sure the DLL exports standard C functions instead of C++.
LabWindows CVI (and LabVIEW even more so) can only link to globally
exported C functions. C++ classes are completely out of reach for both
and C++ compiled global functions have both the problem of taking
sometimes C++ parameter types as well as the name decoration added by
the C++ compiler to all function names.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Model entry point 'test uuts' could not be executed error -18002

Hi,
I am running a testand(2.0.1f1) sequence of labview (7.0) steps and it is working perferctly in my computer , but when installing testand and labview in another computer and I try to run my sequence the next message appears. "model entry point 'test uuts' could not be executed error -18002"
Is anyone that has an idea of what is happening here?
Thanks =)
Eren

Hi Eren,
You might try mass compiling the TestStand folders so that all VI's are at the same Version. TestStand 2.0.1f1 installs VI's that are at ver5.1.1
When you run from the Entry Point eg "Test UUTs", before the sequence executions all VI's in all the sequence contained in the sequence file are loaded in to memory.
Look at the error message again, it should be telling you which step in which sequence of the sequence file is not executable.
Hope this helps
Ray Farmer
Regards
Ray Farmer

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"

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"

Upgrading from Labview 8.0 to Labview 8.6

Software installed in my system (Window 2000):
Testand 3.5
Labview 8.0
Cvi 8.0
Device drivers
NI-488.2 VERSION 2.46
NI-VISA VERSION 3.6
NI-DAQMX VERSION 8.1.0F1
I want to install LABVIEW 8.6 instead of LABVIEW 8.0
1.Do I have to upgrade Testand,Cvi, or one of the device drivers?
2.Do I have to uninstall labview 8.0 before installing labview 8.6
(right now Labview 8.0 is installed at directory: "c:\Program Files\National Instruments\LabVIEW"
& I want to install LABVIEW 8.6 at the same path.
Thanks Ofer

Hi ofer_o,
you have to install the device drivers for LabVIEW 8.6. You don't need to install TestStand or CVI again. You don't have to uninstall LabVIEW 8.0 to run 8.6. You can use both side by side, technically, i'm not sure about your license.
Mike

Avoid labview initial window to show up when running a sequence

Hi,
I'm running a testand sequence that calls labview Vi's (not exe not dll) and right when it starts running the main start labview window shows up right in front of testand. I mean the window that appears when you open labview. How can I avoid this? If i try to close it the sequence stops with an error , If i minimize it the popup messages that I'm sending from labview starts appearing in the left upper corner.
Can somebody help me?
Thanks
Eren

Hello Eren,
The reason the LabVIEW screen appears is that TestStand's LabVIEW code module adapter is configured to use the LabVIEW development environment to run the VIs called by your sequence.
In TestStand 3.0 or 3.1, you can change the LabVIEW adapter configuration to use the LabVIEW run-time engine, which will not display the LabVIEW screen. In the TestStand sequence editor, click the Configure menu >> Adapters, then highlight the LabVIEW adapter. Click the Configure button, then select the option "LabVIEW Run-time Engine".
David Mc.
NI Applications Engineer

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

Labview lent

Bonjour,
Je travaille sur labview 2009 et depuis quelques temps, j'ai des soucis de lenteur. En effet à partir d'un programme utilisant des taches DAQmx ( auxquelles je ne fais plus appel), j'ai ajouté des Vi d'appels a des modules XNET. jusqu'ici tout fonctionnait bien. Du coup n'utilisant plus les tâches DAQmx, je les ai mises dans des structures de diagramme désactivé. Et depuis ont commencé les problèmes. Navigation dans labview impossible. Passer d'un VI à l'autre ou tout simplement de la face avant au diagramme prend 2 min quand il ne plante pas. Impossible de lancer une execution. Rien à faire je ne peux plus l'utiliser.Et le problème ne vient pas de la cosommation de la memoire. dans le gestionnaire des taches labview ne consomme que 1 ou 2 % quand il ne repond plus. J'ai alors remis toute les taches DAQmx en "activer" mais rien ne change.
auriez vous une idée? Désolé, pour le VI je ne peux pas le partager.
Cordialement,
Cdobrazil.

Bonjour et merci de votre réponse.
Alors créer un nouveau Vi ne pose aucun problème. Tout comme le fait de lancer le "main" VI et de naviguer à travers les nombreux sous VI. Sauvegarder, naviguer ou encore modifier les VIs se fait de façon super fluide. Je peux lancer et arrêter l'exécution sans aucun souci. Et dès que je lance le projet, la ça plante. Si je lance un autre projet, pas de soucis. Le problème vient peut-être du fait qu'avec l'avancement j'ai dû faire des sauvegardes de projet et que assez souvent je suis obligé de les rouvrir pour revenir sur certaines fonctions. Le nom du projet reste le même mais le chemin change et j'ai l'impression que de temps en temps il s'emmêle un peu. J'ai déplacé mes backups, et j'ai relancé le projet pour voir si il n'allait pas chercher les VI ailleurs. Ensuite j'ai recompilé mais à priori rien de particulier.
#### Starting Mass Compile: mer. 4 avr. 2012 10:26:00
Directory: "C:\Data\....."
Skipping project already in memory: C:\Data\.......\ReadCan3.lvproj
CompileFolderCore: error 13 at C:\Data........\ReadCanXE.llb
CompileFolderCore: error 13 at C:\Data\..........\TestsLibrary with vis problems.llb
### Bad VI:    "read TestsLimits.vi" Path="C:\Data\..........\TestsLibrary.llb\read TestsLimits.vi"
### Bad VI:    "TotalOffsetMeasurement.vi" Path="C:\Data\..............\TestsLibrary.llb\TotalOffsetMeasurement.vi"
### Bad VI:    "writeTestsLimits.vi" Path="C:\Data\...............\TestsLibrary.llb\writeTestsLimits.vi"
### Bad VI:    "openCanRec.vi" Path="C:\Data\................\openCanRec.vi"
### Bad VI:    "tesat acqui RS422.vi" Path="C:\...............\tesat acqui RS422.vi"
#### Finished Mass Compile: mer. 4 avr. 2012 10:26:02
Pour les Bad VI, ils ne sont plus appelés dans le projet.
Une idée ?
Merci encore,
Cdo.

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

Can test stand execute LabVIEW executables ?

Can I refer to LabVIEW executables in testand -> I can run VIs developed in LabVIEW through Teststand with only the LabVIEW runtime engine on the host computer ?

What version of TestStand are you using and what version of LabVIEW are you using?
Scott Richardson
National Instruments

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

Open and close multisim contact with LabVIEW

Can I open and close multisim contact with labview and read the receptor estatus (p.e. lamp)?
Thanks.
Attachments:
Dibujo.JPG ‏13 KB

Hi Guddan,
I created a RFC having a query which is taking a long time to execute. So i want to close RFC connection with portals which is via java connector(JCO) before that query and open the connction again after that query.
I guess i will need to understand your requirement a little more in detail, as i understand you have an RFC which has a query within to fetch some data and is taking a long time to do so. In the meantime you don't want to keep the connection open?
My question would be, Is the role of this RFC to only execute the query and fetch the data or does it do something else?
If it does other things and these are independent of the query execution, then you can span a parallel call within the RFC to execute the query and in the meantime the RFC does the other things (or vice versa) hence reducing the overall time taken.
If the sole purpose of this RFC is to execute the query, then you will not be able(i mean to say there is no simple and direct way of doing this) to close the connection after the Query is started and re-establish the connection after its execution, for a simple reason that - how will you know if the query has completed it's execution, so that you can establish the connection back.
Alternate solutions, make this a two way asynchronous call, 1) You invoke the RFC asynchronously and close the connection, the RFC in turn will execute the query and transfer the data to JCO via another RFC call.
If this needs to be a synchronous call, then you will need to optimize the query to its best.
Regards,
Chen

LabView Exe Application file not launch Excel application for report generation

Dear All,
I created one LabVIEW application file for report generation (using Excel Template).
While I run the program in programming mode it works well and create the report file in the specified path.
After creation of the application file(exe), it gives the correct path of where the excel template is placed. The same path is given to New Report.vi, but it gives the error 'File Not Found'.
Tell me, is any other configuration required for generating Excel reports? (During exe application mode)
Give me the solution.
Thank You
Jegan.

Hello,
Most likely you are encountering a problem of stripping and/or building paths. Probably the easiest thing to do is put a couple indicators on your front panel for the path or paths you care about, build your exe, and make sure you are really using the path you'd like. If you always put the report at some deterministic place relative to the exe (that is, even it the exe is moved, it will go with the exe and remain in the same relative path location, then you can use the Current VIs Path funtion found in the ... File I/O -> File Constants palette as a start path (where you will want to strip at least the exe name off of course).
I think this will bring some clarity to the issue!
Best Regards,
JLS
Best,
JLS
Sixclear

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

Lenteur testand et labview

Similar Messages

Maybe you are looking for