S'interfacer avec NI TestStand

Bonjour, je suis débutante en TestStand et malgré avoir lu beaucoup de documentation , je n'arrive pas à résoudre mon problème. Voila  j'ai crée une IHM sous Labview (lancer le test, le test OK , le test NOK, le test en cours,voir pièce jointe) en plus j'ai crée plusieurs séquences sous TestStand qui permettent de faire le test de ces cartes . Mon besoin est d'interfacer l'IHM avec ces séquences de test et voir tout le déroulement de test. j'ai déjà vue plusieurs post mais je l'ai pas bien compris.
Merci d'avance.
Pièces jointes :
GUI.zip ‏23 KB

Bonjour,
Vous pouvez sinon regarder le pdf "UsingLabVIEWLabWindowsCVIwithTestStand" présent à l'emplacement suivant :
"C:\Program Files (x86)\National Instruments\TestStand 20XX\Doc\Manuals"
Cordialement,
Jérémy C.
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;}
Travaux Pratiques d'initiation à LabVIEW et à la mesure
Du 2 au 23 octobre, partout en France

Similar Messages

  • Open DeviceNet interface error when TestStand call VIs of NI PCI-8532

    Hello,
    We use NI PCI-8532 was used as DeviceNet master to do functionality test with a slave (AC Drive).
    But when open DeviceNet interface, it happen the error.
    We can't find the solution and hope to find help from you.
    The basic sequence in TestStand is:
    1). Call "Open DeviceNet Interface.vi" to open interface and creat interface object.
         Interface(master) setting: interface name=dnet0, MAC ID=0, baudrate=125000bps
    2). Call "Open DeviceNet IO.vi" to creat DeviceNet IO object.
         Device(slave) setting: MAC ID=63
    3). Call "Operate DeviceNet Interface.vi" and operation code=start
    4). Call "Wait For State.vi"
    5). Call "Read DeviceNet IO.vi" to read data from IO object
    6). Call "Close Object.vi" to close IO object handle
    7). Call "Close Object.vi" to close interface object handle
    Remark, these DeviceNet VIs locates at "C:\Program Files\National Instruments\LabVIEW 2012\vi.lib\DeviceNet\VIAPI".
    First time to run sequece in TestStand, it can pass to run step 1) to open DeviceNet interface.
    But once there is some error with these steps, and it will happen "Open DeviceNet Interface" error (error code=0xBFF62006) when run these steps again.
    Then even use LabVIEW DeviceNet example to test, and it happen the same error except restart computer.
    The DeviceNet example locates at "C:\Program Files\National Instruments\LabVIEW 2012\examples\NI-Industrial Communications for DeviceNet\Basic Examples\PXI & PCI\MixedCommunication.vi".
    Some information more:
    PC operate system: Windows XP SP3
    LabVIEW version: 2012 SP1
    TestStand version: 2012 SP1
    PCI 8532 driver version: 2.3.0
    Other installed PCI board: PCI 8531 CANOpen

    The following errors may be resolved by resetting the CAN, DeviceNET or LIN device:
    Error -1074388986 occurred at ...
    NI-CAN:  (Hex 0xBFF62006) The object is already open in another application.  Solutions: Ensure that only one application at a time uses an object , and that you close all objects prior to exiting your application (don't use LabVIEW toolbar's Abort button).
    Error -1074388969 occurred at ...
    NI-CAN: (Hex 0xBFF62017) This attribute's value must be provided prior to the Open. Solutions: Set the attribute using the Config function before the Open, and do not set the attribute at any later time; Do not configure multiple CAN Objects for the same ID.
    SO,you should reset the DeviceNet.
    And another similar issue can explain some points of your problem  http://digital.ni.com/public.nsf/allkb/7D9383E9BEAD0B21862571640002F687?OpenDocument

  • How is it possible to use a COM interface in the teststand?

    Hi,
    we have developed some small aplications that control our devices and we are planning to make a com interface for these applications?
    We would like to control this com (NOT the serial interface) interface from teststand. We do not have Labview.
    Is this possible and if yyes can you point me where I can read the procedure?
    Or if it is not described can you briefly describe it?
    Is there any other more suited options of controlling an application from Teststand? The answer to this question for us is extremly important because we would like to develope as little as possible beside the application and use the Teststand ablities to the maximum.
    Our application is written in C++ with VC++ .net 2005
    I already checked out the manuals and the source code but I didn't find any examples most of them use dll-s and ActiveX.
    Thank you fro your help and time,
    Dacian

    Hi,
    Maybe this will point you in the right direction.
    http://zone.ni.com/devzone/cda/epd/p/id/1219
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • Creer interface avec lien vers d'autres VI s'ouvrant dans une autre face avant

    Je crée un TP pour des élèves et je souhaiterais créer une face avant permettant aux élèves d'accéder à tous les VI dont ils auront besoin, un par étape, comme créer une icone qui nous mène comme un lien hypertexte à une autre face avant. Comment puis-je faire?
    De même, est-il possible de configurer le VI pour qu'il s'ouvre en mode Execution sans s'exécuter, pour que les élèves puissent utiliser le VI sans le modifier?
    Merci d'avance

    Bonjour,
    alors pour aller au plus simple :
    Il suffit d'aller dans les propriété du VI pour chaque sous vis, et dans la catégorie "windows appearance", sélectioner "Custom" puis sélectionner les options suivantes pour chaque sous-vis :
    "Show front panel when called"
    Cela aura pour effet de dégriser l'option suivante :
    "close afterward if originaly closed"
    à cocher également
    Cette opération est à effectuer pour chaque sous-vis dont la face avant devra être vue.
    Ensuite pour éviter des modifications des sous-vis, le plus simple sera de décocher la case "show abort button" ce qui aura pour effet d'obliger à fermer le sous-vi par un bouton "stop" placé sur la face avant, et donc, avec la case "close afterward if originaly closed" cochée, le sous vi sera ferm
    é et l'accès au source ne pourra s'effectuer qu'à partir du vi principal arrêté.
    Mais le plus simple à mon avis, est d'aller dans la catégorie "security" dans les propriété du VI et de sélectionner "password locked".
    Voilà, j'espère avoir répondu correctement à la question, bonne chance!
    Best regards,
    G Liagre

  • Comment interfacer Labview avec JSON (JavaScript Object Notation) or AMF (Action Message Format) ?

    Bonjour,
    Comment interfacer Labview avec JSON (JavaScript Object Notation) or AMF (Action Message Format) en envoi et réception ?
    Pourriez vous m'indiquer la procédure ?
    Si vous avez des exemples ?
    Merci d'avance et bon week-end.
    Seb 

    Bonjour,
    Pour vos post en français, je vous invites à poster sur cette rubrique du forum:
    Discussions de produit de NI.
    Pouvez vous décrire pourquoi vous voulez vous interfacer avec du JSON ou du AMF?
    Cordialement
    Yann C.
    France

  • TestStand : génération automatique de steps et problème de référence VeriStand

    Bonjour,
    je développe actuellement un générateur automatique de séquences TestStand en LabVIEW.
    Certains de mes steps devant s'interfacer avec VeriStand, j'ai donc créé un premier step codé en LabVIEW qui se connecte à VeriStand et qui stocke la référence obtenue dans une variable TS de type Object.
    Le problème vient lorsque je souhaite transmettre cette référence à d'autres steps LabVIEW qui doivent interagir avec VeriStand. En effet, j'ai l'erreur suivante qui apparaît dans TS lorsque j'ouvre la séquence que j'ai généré :
    Le problème disparaît lorsque je clique sur le bouton "Reload VI prototype".
    J'ai constaté que ce problème n'apparaissaît qu'avec les steps LabVIEW qui nécessitent une référence vers VeriStand sur leur connecteur (que ce soit en direct sur le connecteur ou via un cluster).
    Une de mes hypothèses serait que cela vient du fait que ma référence vers VS n'a pas de valeur par défaut.
    Qu'en pensez vous ?
    Benoît

    Bonjour Benoît,
    Avez-vous bien en sortie de votre VI une sortie de type référence ?
    Si oui l'envoyez-vous bien aux step suivant ?
    Voici deux liens qui vous permettrons de simplifier votre utilisation. Il existe des steps VeriStand créés spécialement pour faciliter leurs utilisation.
    https://decibel.ni.com/content/docs/DOC-40123
    https://decibel.ni.com/content/docs/DOC-25218
    Cordialement,
    Alexis JUBIN

  • I am trying to use the T. S. operator interface I need to add pass fail and error

    Hello:
    I  am using Labview 6.1 and Test Stand 2.0
    I have made some modification to a copy of the T.S. Labview operator interface. How do I get the pass/fail or error from test stand to be pass to LabView so I can tell the operator that the unit pass or fail the test. I do not want to use the Test UUTs. I want this to be very low operator response.
    Message Edited by Toro on 02-28-2006 01:52 PM

    Not sure if this is available in the earlier versions of TestStand, but I think so.
    You could post a UI Message, from your execution entry point in the process model, to your User Interface indicating the pass/fail/error status when a test run is complete.  You will need to handle the UI Message in your Operator Interface.  See TestStand II Customisation course notes for handling UI Messages.
    The data passed in the UI Message can be anything you like, the UI Message handler in the User Interface will have to process the message and update the display as required.
    Hope this helps
    Steve
    Message Edited by SercoSteve on 03-01-2006 10:02 AM
    There are 10 types of people in the world that understand binary, those that do and those that don't.

  • Runtime error in TestStand 4.1

    Hi!
    I installed TestStand 4.1 and tried to run the C# user interface provided by TestStand. When I click on Sequence view control in sequence editor tab, I get a run time error and the application closes by iteslf. Im attaching a screen shot of this.
    My OS is windows xp with visual studio 2008.
    Please provide some solution to this.
    Thanks & Regards
    Sgy
    Attachments:
    RunTIme Error.PNG ‏63 KB

    Sgy1,
    The best way to debug a crash like this where we can't reproduce it here on one of our machines is going to be to get a crash dump from the application.  To do this, please follow these steps: 
    Install Win Debug from here: http://www.microsoft.com/whdc/devtools/debugging/i​nstallx86.Mspx
    Launch WinDbg and go to File»Symbol File Path and enter this:http://msdl.microsoft.com/download/symbols
    Start your program that crashes
    Now in WinDbg, go to File»Attach to a Process and select your running program (probably TestExec.exe)
    Hit F5 so the process will resume
    Now perform whatever action makes the program crash.  During the crash, focus should automatically transfer back to WinDbg, and its window should come to the front.
    Back in WinDbg create a crash dump file. Do this by entering in the command at the bottom of the command window. The syntax for the command is:
    .dump /ma "c:\AFileName"
    Then send us that dump file. We will be able to debug it and hopefully get some more information from it.  Since the dump file is generally very large (100-400 MB) you can post it on the ni FTP site at ftp://ftp.ni.com/incoming.  When you do this, post back to this forum with the name of the file so that I can download it.
    Alternatively, if you would like to handle this directly by e-mail or phone, please post back to this forum that you wish to do so, and I can ask the forum administrator for your e-mail address.  The admin will not give out this information without your express permission.
    Josh W.
    Certified TestStand Architect
    Formerly blue

  • TestStand 4.1.1 vi search path

        This is so low-level I'm almost embarassed to ask.  I'm using TestStand 4.1.1 over LabView 8.6, both of which are licensed as full development systems.
        In order for our organization to make better use of (non-NI or Labview) source control, we've created a common directory structure for several developers over several large TestStand/LabView projects.  This includes areas for "common VIs" that are reused across projects.  So I'm in the process of migrating a rather complex project into a new directory structure.  The sequences and VIs in question were working perfectly under TestStand 4.0/LabView 8.5 prior to this attempted migration.
       My test sequences (and sub-sequences) can't seem to find needed VIs, even though they exist in directories that are included in the search paths I configured.  (An annoying sub-problem is that TestStand appears to "hang" while the LabView interface underneath the TestStand window is prompting for a VI's location.  I have to click the LabView item in the Windows menu bar to get LabView "on top" and see what the problem is.)
       I've already added several paths to both the LabView and TestStand VI search paths, and I've even checked the "search subdirectories" box, but the items are not being found.  It's going to take weeks to lead TestStand and LabView by the nose to find all this stuff.
       I can't believe this would really be a bug.  I tried searching the forums for an answer and had no luck.  I can't be the first one with such a problem, so help me out with some search terms so I don't have to clutter the forum with such basic stuff.  Thanks.
    -M

    trosier, Neurotika,
    It appears as if LabVIEW is having trouble finding your VIs, not TestStand.  When TestStand loads the VI you have designated as a code module into memory, if you have the LabVIEW development environment designated in the LabVIEW adapter settings, we tell LabVIEW to load the VI via its ActiveX interface. 
    If TestStand is unable to find the top-level VI, you will see a dialog like this:
    If LabVIEW is unable to find a sub-VI, you will see a dialog like this:
    Notice that the TestStand dialog has an additional checkbox at the bottom that allows you to select an absolute path.  Also notice that TestStand specifies what file its looking for in the Files of Type box while LabVIEW allows you to choose All LabVIEW Files. Which dialog are you seeing?
    Another way to test this is to try to open one of your VIs from disk (by double-clicking on it).  If you get a Searching for SubVIs dialog, then it is LabVIEW that can not find the dependencies. 
    Or if you open the specify module pane of the sequence editor, if TestStand cannot find the top-level VI, you will see a file not found warning like this: 
    If TestStand can find the file, but LabVIEW cannot find a sub-VI, then you will not get a warning or error until the VI is loaded.
    The reason that this matters is that TestStand and LabVIEW do not share their search directory lists.  If you have moved files, you will need to know which application cannot find its files. 
    Message Edited by Josh W. on 04-23-2009 11:27 AM
    Josh W.
    Certified TestStand Architect
    Formerly blue
    Attachments:
    subVI not found by LabVIEW.JPG ‏31 KB
    TestStand file not found.JPG ‏7 KB
    VI not found by TestStand.JPG ‏31 KB

  • How to create Labview User Interface with buttons?

    Hello,
    I try to create a user interface, where the TestStand sequencies can be selected one by one not only Test UUT, Single run and run Mainsequence (about 20 buttons needed).
    I'm playing with the simple UI shipped with TS and can load the sequence file and run automatically a sequence (Main or another).
    How can I create and assign buttons to all sequence files in my TS project?
    Any help would be appreciated.
    Thanks. (TS 4.0, LV 8.0)

    I've modified my main VI with the below steps.
    I still don't know how to create and assign front panel buttons to the user interface.
    Anybody could explain to me how do I need to modify the attached part of my main vi and how to assign buttons.
    Thanks.
    Attachments:
    InteractiveArgs_2.png ‏12 KB

  • Sequence file path programmed in operator interface

    Hello,
    I do not want to load the sequence file with the button OPEN_FILE etc.. for example how it is done in th Simple Operator Interface. I want to programm the path and the sequence file name in the Operator Interface. How can I do this that the correct file will be loaded
    regards
    samuel

    I try to explain what you have to do without an example, because it is realy simple, and so we have no version dependency ;-)
    I used the "simple operator interface" installed with TestStand (..\National Instruments\TestStand 3.x\Operator\Interfaces\NI\Simple\LabVIEW\TestExec​.llb\Simple OI - Top-Level.vi). I added the method mentioned above in front of the Event-Structure (See attached picture)  and added a path-constant, to define which Sequence should be loaded automatically.
    Try this out. It works fine on my machine (LabVIEW 8.2.1, TestStand 3.5, but should be independent of Versions as long as you have TestStand 3 and LabVIEW 7 at least).
    Hope this helps!
    André
    Message Edited by Andre_Saller on 04-25-2007 11:34 AM
    Attachments:
    Autoload.jpg ‏167 KB

  • Using TestStand Engine API in LabVIEW

    Hi all,
    I am currently working for a proejct where automation of testing is involved, For which NI LabVIEW and TestStand are used. My previous experience is in LabVIEW only and not in TestStand. In the current project I have to develop a UI where user can select the test sequences and execute them  automatically with a simple start command. So I thought to develop a UI in LabVIEW where I will call TestStand APIs in LabVIEW. I have a developed a code by calling the TestStand APIs and able to execute the sequence, but unable to generate the report. Does  any have stuff where in TestStand APIs are called in LabVIEW and test report is generated.
    As I mentioned earlier I haven't worked much in TestStand. I have gone through the TestStand examples like Simple UI. But it didn't helped me much.
    To put our project requirement in simple.
    1.It should  have the UI to select the TestCases (Test Sequences) and an option to select the no.of times the test cases needd to be executed.
    2. It should generate the reports for all the test cases.
    3. UI should support localization.
    Considering the above requirements I have thought to develop UI in LabVIEW calling the TestStand APIs. I also got to know that UI can be developed using TestStand, but I am not sure whether the above mentioned requirments can be fullfilled or not.
    I am attaching the VI what I have developed in the LabVIEW with which I am able to execute the sequences, but unable to generate the report. Kindly look into the VI and let me know what need to be corrected to generate the report using the same VI.
    Thanks and Regards
    Giridhar
    Attachments:
    TestStand_Enginevi.vi ‏21 KB

    If you want to generate a report you'll have to choose an entry point. You should have a look at the LabVIEW OI (operator Interface) shipped with TestStand
    Rodéric L
    Certified LabVIEW Architect

  • Why are my LabView Dialog Boxes no longer modal when using the Example LabVIEW Operator Interfaces?

    Hello,
    I have a step in my sequence that pops up a modal LabVIEW dialog box. My LabVIEW vi uses the TestStand - Start Modal Dialog.vi and TestStand - Stop Modal Dialog.vi as described in the example and it works as advertised when I'm using the TestStand Development environment however when I use the sample Operator Interfaces distributed with TestStand the Dialog boxes lose focus. I have the VI Properties->Window Appearance set to Dialog and have followed all of the instructions I could find for making a dialog modal. I've also reviewed all the documentation I could get my hands on including previous posts on this board and didn't see anything obvious.
    Does anyone have any suggestions as to what I may be missing? Has anyone else experienced this problem and come up with the solution?
    I am using LabVIEW 8.0 along with TestStand 3.5.
    Thanks,
    RG

    Hi RG,
    Running the example modal dialog in the teststand3.5 examples folder and using labVIEW8.0, I notice that when  the Dialog is displayed its not active, but it is modal to the OI. Clicking on the Dialog panel makes it active. If you try to click on the OI panel behind, you can not. Is this what you are seeing?
    I am using the Full labVIEW IO as supplied with TestStand and the example VI in the modal dialog folder is as supplied.
    The LabVIEW Adapter is still configured to use the active labVIEW developement environment.
    If I run the same example, only this time using LabVIEW7.1, the Dialog panel is active.
    There is a patch to take it to labVIEW8.01, at this moment in time I am not sure what the update fixes.
    There does seem to be a problem with TestStand3.5 (engine) and LabVIEW 8.0.
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • TestStand API terminate all notification

    I've developed a LabWindows based user interface using the TestStand UI controls and the TestStand API. I have a sequence file that has several cleanup steps, some of which take a while to finish. One function of the user interface is an Emergency Stop button. When this is pressed, an Engine.TerminateAll is issued via the API. The test fixture has 8 sockets which are using the Batch Model TestUUts entry point. Is there any easy way via callback or other means of knowing when all the terminations have completed. I would like to display a popup telling the operator to wait while the cleanup steps are being carried out. I also want to disable the START button and reenable it when the terminations are complete.
    I am launching the execution with TS_EngineNewExecution and I can get the id. I tried to wait until I saw this execution end with the ApplicationMgr  EndExecution event or the Execution VIew Manager EndExecution event but I saw a bunch of exection id's except the one that I was looking for. It may be my fault but I wanted to ask and see what is the best approach for what I am trying to accomplish.
    John

    Hey John,
    Your method will work, and your assumptions are partially
    correct.  If you look in the Batch Process Model, inside of the
    Cleanup Step Group of Test UUTs there are steps that tell all
    TestSocket executions to stop.  There is also a wait step that
    forces the Process Model execution to wait until all of the TestSocket
    executions have terminated. There are going to be multiple EndExecution
    events because it is going to occur for each execution that finishes
    whether it is the Process Model execution or one of the TestSocket
    executions. However, the Process Model will always be after all of the
    TestSocket executions have completed. 
    Another thing to keep in mind is that this is only happening because it
    is built into the process model.  Normally if you spawn off a new
    execution it is separate from your original execution, and the new
    execution would not terminate by calling the terminate method on your
    original execution.  You would have to either do a terminate on
    each execution or use the terminate all method of the application
    manager. Hope this helps to clear things up a little.
    Pat P.
    Software Engineer
    National Instruments

  • Programatically Loading Several Sequences Using LV Simple Operator Interface

    I am playing around with the supplied LV(2009) Simple Operator Interface for running TestStand (4.2) and hoping that someone can point me in the right direction.  I know this may be too generic for a concise solution, but hopefully I can get some suggestions on the best approach for this. Here is a short description of what I am trying to accomplish. 
    I am testing 2 unique UUTs on a single test fixture that is controlled by a PCI-7831R DAQ.  Each UUT will have a unique serial number and report generated.  Therefore, I am using 2 unique sequence files created using TestStand.  Basically, I want to be able to read in a barcode on the test fixture and have the operator interface load the 2 unique sequence files based on information contained in the barcode.  The operator will then hit a button to start the sequence file executions.  I want the first sequence file to run and test the first UUT.  Once the first sequence file is finished, I want the second sequence file to load and run on the second UUT.
    I can use the simple operator interface to load both sequence files.  I then have to select the combo box to select which one I want to run.  This works fine, however, I am trying to automate this so that the operator doesn't have to open the files and continually use the combo box to select sequence files.
    Any ideas or suggestions would be greatly appreciated.

    I have figured out a solution (for my initial application at least) of programmatically loading the sequence files.  When the operator interface first starts, there is a prompt where the user will scan a barcode that is loaded on the front of the fixture.  For all of our product lines, we will have a unique format for the fixture barcode.  Included in this barcode is a product specific software ID number.  I create a folder with the same software ID number and store the sequence files there.  I then parse the barcode and open all *.seq files in that folder.  I have this working correctly now. 
    Once the sequence files are opened, the user must scan each UUT ID barcode before installing them on the fixture.  The intent is to have both UUTs installed on the fixture at the same time so they can be tested serially.  If, however, they do not scan one of the UUTs, it will not be tested.  Basically this is due to the fact that they may want to run only a single board.  Once all of the UUT barcode scanning has been completed, I have another button that will execute the sequence files using the 'Single Pass' execution entry point.  I agree that the 'Single Pass' and 'Test UUTs' points should be hidden from the user.  Once the execute test(s) button is pressed, it will check each UUT barcode to make sure that it is valid.  If both UUT's have valid barcodes, it will run the first UUT and then the second using the 2 sequence files that were previously loaded, otherwise, it will run only one or the other.  The UUT(s) will then be removed and the process starts over again from the UUT ID barcode scanning.  They will not have to scan the fixture barcode again since the correct sequence files have already been loaded.
    Currently I have the UUT/Sequence File associations hard-coded in the UI.  I will need to put my thinking cap on so that as we increase the product lines (several are already in the pipeline) we can use the same UI without any modifications.  Scalability is King!

Maybe you are looking for