Creation of step (by Teststand) with LabView

I created a sequence with TestStand, I would like to insert a step in it but with labview.
The problem occurs on the level from the NewStep method and its StepTypeName parameter.
This parameter is of type String, I tried to enter several string but unless result.
The error appearing is "Step type not found in type list".
In the help file of TestStand, it is said that "the step type must already be in memory",
but I don't more understand it.
Can you help me?
Thanks
Attachments:
TS_test1.vi ‏83 KB

Hi,
I think you have to load the TypePaletteFiles first.
Please take a look at the example from the link below.
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3DEA556A4E034080020E74861&p_node=DZ52238
This is what you need. Tested it, works fine.
Regards.
JorisV

Similar Messages

  • How to use ExpressionEdit Control in teststand with labview

    Hi
    I am trying to get the ExpressionEdit Control to work in a labview custom step in teststand, but i have no idea how it works and cant find a solution.
    What I need is a simple example.

    Hi,
      that would really depend on how you want to use it. Do you just want the text from it? In which case there's a property of Text you can get from the control. Architect your code so that when you hit your OK button etc, it grabs the "text" information from the control.
    All of the properties and methods are documents (right click the control's fpterm on the block diagram, create >> property (so it created a property node for the activeX control, not a property for the LV control it's buried in) and select things like Text, or an invoke node, and things like DisplayBrowseExprDialog.
    You can then right click those, and go to "help for ...." for that property or method.
    Unless we know what you propose to use it for, then we can't really help with sample code, since it might not be applicable to your setup. (i.e. text out versus evaluation of the expression, versus displaying the browse expression dialog etc).
    You'll probably need to write to the context property to get the correct sequence context to browse with (pass in the "thiscontext" to your vi, and write to the context property of the dialog box.)
    Hope that helps
    Thanks
    Sacha.
    // it takes almost no time to rate an answer

  • Deploy teststand with labview ui

    Hi,
    I'm using teststand now since 9 months and now I have to distribute my application to a testing machine. I have some questions about this process. But first I discribe my application:
    I have a labview ui, which has 3 main tasks:
    1.) Start selected teststand sequences for automatic testing.
    2.) Give operator the possibility to manually control the testing environment (purely written in labview)
    3.) Run continous data aquisition, which provides data for teststand and manual testing.
    Sharing data between labview and teststand is done mainly via global variables (e.g. reference to tdms file). Because of 1.) and 2.) above teststand and labview share a lot of VIs for communicating with the testing environment.
    OK, now my questions:
    I'm searching for the best way to deploy this application via an installer. I know, that there is a teststand deployment tool (which I havn't used, yet) and I know how to build installers with the labview project manager.
    1.) What about sharing of VIs and global variables between my teststand sequences and my generated labview exe? When I place my sequences in the workspace file for the teststand deployment tool, all referenced VIs are included in teststand. But Some of these VIs are also included in my generated labview ui. Will this generate a conflict?
    2.) I was thinking about to create a teststand deployment without a workspace file. The sequences and all required VIs would be placed in the generated labview ui instead. Will the teststand sequences find the VIs inside of the ui exe?
    3.) What about required drivers (e.g. daq-mx)? Should I create a labview installer of my ui with the required drives and install this, then create a teststand installer (perhaps including the ui, too) and install this, too?
    Thanks for any help in advance.
    Marc
    CLD

    Hi,
    I would recommend the Deployment Tool for your TestStand and OI. I would also keep your Test Sequence files seperate from your TestStand Engine amd UI deployment.
    [1.) What about sharing of VIs and global variables between my teststand sequences and my generated labview exe? When I place my sequences in the workspace file for the teststand deployment tool, all referenced VIs are included in teststand. But Some of these VIs are also included in my generated labview ui. Will this generate a conflict?}
    This is going to cause you a problem because LabVIEW doesn't like / will not load the same VI into memory from two different locations.
    The Deployment Tool will probably object as well therefore you will not beable to create a deployment package.
    The Deployment Tool will place all the VIs that are called directly from TestStand Sequence Files as seperate VI's (not in a LLB) into the target folder. It will then create a support LLB containing all the subVI's used by the directly called VI's. If you have VI's that are called directly from TestStand and are also used as subVI's you will again have problems because the same VI can be loaded from two different locations. 
    2.) I was thinking about to create a teststand deployment without a workspace file. The sequences and all required VIs would be placed in the generated labview ui instead. Will the teststand sequences find the VIs inside of the ui exe?
    No Teststand will not beable to find your VI's in the EXE. If you need to use the same VI's in both your OI and TestStand sequence file then create a DLL.
    But I would recommend you keep the OI code seperate from your Test Code.
    3.) What about required drivers (e.g. daq-mx)? Should I create a labview installer of my ui with the required drives and install this, then create a teststand installer (perhaps including the ui, too) and install this, too?
    Install your drivers first. The IO should be installed as part of the TestStand deployment as this will register the various components correctly.
    Regards
    Ray Farmer
    Message Edited by Ray Farmer on 08-06-2008 01:02 PM
    Regards
    Ray Farmer

  • How do you effectively use if,for, type loops in TestStand. Do you have to use the goto command or is there a way of writing actual c type code (perhaps using the statement step in teststand) with the variables allready declared.

    Thank you
    Arik

    I assume your loop is more than just one step. You should use the 'Loop Options' for a single step.
    For looping on a group of steps, you can place them all in a sub sequence and then set the 'Loop Options' for the 'SequenceCall' step to set up your looping conditions. Pass values to and from the sub-sequence by Parameters.
    You can keep the loop inline with the rest of your sequence by using 'Goto' or using 'Goto destination' in the Post Actions tab of the condition step.
    Using a sub sequence will keep it easier to read and maintain.

  • I need a step motor and controller compatible with LabView Can you recommend any

    I need a step motor compatible with LabView and I thought i would check with you before i moved forward in my experiment

    Dear chapbs,
    I've attached a sample cart below to show you the components for a possible setup of your system. Keep in mind that whatever stepper drive you purchased would power your motor. If you go ahead with the purchase of a controller & drive, I would highly recommend contacting NI to insure that you purchased the correct accessory components and cables to connect & power the components. I hope the  sample cart is helpful. I created it  by browsing ni.com, adding items to my cart, and then saving the cart to an excel file. Please post back if you have additional questions.
    Best Regards,
    ~NH
    Attachments:
    SampleCart.pdf ‏145 KB

  • Reading teststand variables with labview??

    I'm trying to create a vi that will read the uut serial number from teststand and compare it to a second scan from the operator. Is there a function I can put on the block diagram to read the teststand variable? I've read the using teststand with labview but it's still unclear how to do this. Could I just pull the serial number from the UUT dialog that the user starts the test with instead? The other problem is this is a 4 uut test panel so I need to make sure I compare the correct uut serial number info. Any ideas?

    The name of the variable is RunState.Root.Locals.UUT.SerialNumber. When you create your VI, have a string control that you pass this in. This is done when do the Specify Module as shown below. Here's an example sequence and VI as well. You can also make it a bit more complicated by using the sequence context and the TestStand Get Property Value function.
    Message Edited by Dennis Knutson on 05-01-2007 04:16 PM
    Attachments:
    Specify Module.PNG ‏29 KB
    TestStand Example.zip ‏9 KB

  • Add a substep (Edit Mode) with LabVIEW

    Hello,
    My supplier has delivered a library of steps in TestStand (with a TypePalette and associated Ini Files).
    I'd like to custom the INI file with LabVIEW to add a module as "Edit Substeps" on the differents Steps Types.
    With "GetTypePaletteFileList" and "PropertyObjectFile", I can see the differents Type Palettes and the associated paths but I can modify it (add a substep module ... etc) ?
    Is it possible ? Someone has an idea ?
    Thank you for your help
    YR42

    Hello,
    Here you can find a post, with an example:
     http://forums.ni.com/ni/board/message?board.id=330​&requireLogin=False&thread.id=5599
    I hope that this link will help.
    Regards
    Nacer M. | Certified LabVIEW Architecte

  • Calling a VI which uses "system exec.vi" with LabVIEW run-time engine as adapter

    Hi,
    My TestStand sequence calls a VI which includes a call to "system exec.vi". When I try to load it in TestStand and if LabVIEW adapter is set to run-time engine, I get an error message "Unable to load Vi...". If I switch the adapter to "Development system", then it works fine.
    Is there any way to use "system exec.vi" in a VI which is called in TestStand with LabVIEW run-time ?
    Thanks,
    Alex
    Solved!
    Go to Solution.

    Hi Alex,
    In you case, you are getting a -18002 error.
    The reason is explained in the following link:
    -18002 Errors in TestStand
    http://digital.ni.com/public.nsf/allkb/D82FEAF0B4BA293A862575710053E252?OpenDocument
    Please have a look at the 2nd reason. This is your case.
    Hope it helps,
    Regrads
    Julien De Freitas / Applications Engineer / Certified LabVIEW Developer (CLD)
    National Instruments Switzerland

  • Interfacin​g Siemens Desigo PXC Building Automation controller with LabVIEW

    Hello everyone,
    I am currently trying to interface Siemens building Automation controller Desigo PXC100-E.D http://www.buildingtechnologies.siemens.com/bt/glo​bal/en/buildingautomation-hvac/building-automation​...
    with LabVIEW using OPC servers. I had once interfaced the S7-300 PLC of Siemens with simatic step-7 software with LabVIEW but in this case I don't which driver should I select and don't know is it possible or not. If any one of you have similar sort of expierence please I need advice..
    Thanks
    Naqqash.
    Naqqash

    Hi,
    As you have described I've done the whole configuration. I am using MatrikonOPC for BACnet and as I've checked my device and the software are working properly. Now what I am trying to is that I am connecting the BACnet OPC server with LabVIEW so that the MatrikonOPC act as a connection layer between my device and LabVIEW. So that I will be able to change values directly from my LV vi. Now when I connect that Bacnet OPC with LabVIEW using the same procedure for PLC it gets connected because it is showing all the tags from the device. But after doing the whole procedure which is the same according to the tutorial 'connecting LV to any PLC using OPC' when I deploy the variables I am getting some error. I am attaching the screenshot of the error. Please let me know if I am doing any thing wrong.
    PS: I am using a virtual machine and I've tried the whole thing with the NI OPC servers as well according to the tutorial but still when i deploy variables I am getting this error.
    Naqqash
    Attachments:
    OPC_error.JPG ‏22 KB

  • How to locate the path of ExpressVI associated with a step in TestStand 3.1??

    When I associate an ExpressVI with a Step in Teststand 3.1 by using SpecifyModule, its Path is not available in any of the Teststand Variables
    unlike Standard VI's whose path is located in "Step.TS.SData.VIPath". 
    Is there any way I can find out the ExpressVI's absolute path??
    Pavithra,
    Delphi, TCI

    I am not sure about TestStand, but in LabVIEW the Express VIs are in a separate file, they are part of the VI in which they have been dropped.  In other words, they are unique in that they are embedded in the VI diagram.  Perhaps something similar is done in TestStand and they are saved as part of the seq.  I don't see how, as they would show up in the xml that is a sequence, and I have never noticed one there, but then again, I have never tried to look.
    Hope that helps,
    Bob Young
    Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
    DISTek Integration, Inc. - NI Alliance Member
    mailto:[email protected]

  • A problem was encountered with one of the files in TestStand\AdapterSupport\LabVIEW directory

    When looking at the module for a LabVIEW VI being called from TestStand, I get the following message:
    A problem was encountered with one of the files in TestStand\AdapterSupport\LabVIEW directory.  Please reinstall it or repair it.
    I made the mistake of cleaning up C: in my computer.  Cleaning C:\National Instruments Downloads
    Why would someone put bits of applications or modules, etc in such a directory?
    I am not too crazy about restoring 11GB back into that folder.  That's just insane!
    Has anyone encountered this before?  Any "easy" solutions? apart from re-installing TS...
    Side note:  I did not touch anything in the \Program Files|National Instruments\TestStand\AdapterSupport\LabVIEW
    Solved!
    Go to Solution.

    Thanks PH,
    I also had that.  Fixed it. 
    I will not remove the ones in the NI downloads folder.
    I will eventually need to remap everything to the appropriate drive. 
    I partition the drives into:
    C:\     Windows and associated folders.  Mostly OS stuff
    E:\     Applications (this is where it will end up)
    F:\     Files
    G:\    Storage
    H:\    Backups
    I try to do what I normally implement in Linux.  I hate sharing the OS with everything else.
    Cheers,
    RayR

  • TestStand Queue with LabVIEW (replacing Batch Dialog)

    Hi,
    I want to replace the default Batch dialog UI with one made in LabVIEW with as little change as possible in the original processmodel (BatchModel.seq).
    To accomplish this, I want to use the "Create Dialog Request Queue" in the process model. I've attached a small example.
    There are 2 issues I'm struggling with:
    1: The process model use a type named "NI_BatchControllerRequest" and name the container "ControllerRequest" in the "ProcessDialogRequests" sub sequence. Can I pass this as a LV Cluster and Variant (see example).?
    2: I can't seem to get the Queue reference in LabVIEW (see LabVIEW example). It works fine if I use a name (string) instead, but the Queue in the process model use Object Reference, and I would like to keep this setting. 
    TestStand version: 4.2.1
    LabVIEW version: 2009
    (I would also like to implement this in TS 4.0 and LV 8.0)
    I'd appreciate any help on this.
    Regards
    Tom Andres Lomsdalen, CTD
    Attachments:
    TS Queue with LabVIEW.zip ‏23 KB

    I am getting the property object from Locals.ModelData.DialogRequestQueue from the sequence context of the top-level thread of the execution.  The problem with GetSyncManager is that it requires the name of an object (for which there is none).  I have the object itself.
    I have also tried to convert the object directly to a queue or a sync manager, but the conversion fails.

  • Dequeue a teststand queue with labview

    Hello,
    I'm trying to dequeue elements since a VI that is running in a Thread independent of the mainsequence (Teststand).
    I :
    1.- Create a Queue.
    2.- Launch the VI in a new trhead (Is a states machine controlated by the queue ).
    3.- Now in TESTStand mainsequence i will like enqueue elements to give orders at VI. Any idea how to do this?
    egards,
    Oriol

    Hi,
    First, the best way is to enqueue a close message so you know it has to close.
    Second, it returns an error when the queue ref is destroyed =>you just need to handle the error! Maybe the easiest way would be to add a failure post step action to your step (in TestStand) and do whatever exit code you need to perform!
    BR,
    Rodéric L
    Certified LabVIEW Architect

  • Crane Aerospace and electronics is looking for Test Engineers with LabVIEW experience - please disregard previous post.

    Here is the correct post:
    Are you detail-oriented, creative, and technically skilled at Engineering design and development?  Come to Crane Aerospace & Electronics and use your excellent Engineering skills to design, improve, and deliver the next generation of products in the aerospace and electronics Industry!
    We have a unique and exciting career opportunity for Engineer II, Test.
    You will be responsible for maximizing new product development and manufacturing performance through the creation and deployment of test strategies, tools, and plans.  Design and implement high performance hardware and software for test equipment.  Authoring test procedures and performing Qualification test activities.  Ensure high product quality.
    Responsibilities:
    Collaborate with customers and multi-disciplined engineers to establish/clarify test, qualification, verification and validation requirements.
    Write test plans, procedures, requirements and reports in a highly structured environment.
    Analyze, develop and deploy complex and high performance test hardware and software solutions for automated test equipment. 
    Design, develop, debug, validate & verify the fabrication of manual and automated test equipment at the circuit board and system level, and specify and procure COTS test equipment.
    Develop/maintain hardware documentation including block diagrams, schematics, BOMs, wiring diagrams and wiring lists, software documentation, and configuration control of initial release and updates. 
    Perform detailed calculations to establish test equipment specifications and design margins.
    Maintain existing test systems through bug fixes, improvements and modifications.
    Support the estimation of costs and schedules to develop or upgrade test platforms.
    To perform a number of the above responsibilities with limited supervision.
    Minimum Requirements:
    Experience: 2-5 years.  Previous work experience in aerospace, space or medical electronics industry preferred.
    Knowledge: Microprocessor / Microcontroller hardware and firmware design; Analog Circuit and power supply design; Digital Circuit Design including high-speed serial communication design; Firmware programming in c; Schematic Capture, PADS Logic preferred; Circuit Simulation; Fundamentals of magnetic proximity, temperature, and pressure sensing electronics; ESD; Familiarity with testing standards (MIL-810, MIL-704, and DO-160 preferred).  Basic laboratory test equipment; LabVIEW experience, certification preferred; Developing hardware per DO-254 and software per DO-178 preferred; Experience with Adobe FrameMaker, IBM Rational tools, TestStand, Microsoft Project preferred.
    Skills: Good interpersonal and communication skills (verbal and written)- effectively lead and/or participate in multifunctional teams in a dynamic work environment. Ability to manage multiple tasks, flexibility to switch between tasks and prioritize tasks. 
    Education/Certification: Bachelors Degree in electrical engineering, computer science, physics or related technical discipline.
    Eligibility Requirement: Must be a US Person (under ITAR rules) to be eligible.
    Working Conditions:
    Working conditions are normal for an office/manufacturing environment. Machinery operation requires the use of safety equipment to include but not limited to safety glasses, heel straps, and shop coats.
    Requires lifting 25 lbs
    Apply online today: http://ch.tbe.taleo.net/CH06/ats/careers/requisition.jsp?org=CRANEAE&cws=5&rid=3170
    Crane Aerospace & Electronics offers competitive salaries and outstanding opportunities for career growth and development.  Visit our website at CraneAE.com for more information on our company, benefits and great opportunities.
    In our efforts to maintain a safe and drug-free workplace, Crane Aerospace & Electronics requires that candidates complete a satisfactory background check and pass a drug screen prior to employment.  FAA sensitive positions require employees to participate in a random drug test pool.

    How can you say you are hiring test engineers with LabVIEW, yet the job description doesn't even mention LabVIEW.  All I see in there is CAD design.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Acces FilesGlobals of Teststand from LabVIEW?

    Hi,
    What happens, when you try to get the value of a Teststand variable (FileGlobals) with the Get Property in LabVIEw and at the same time, Teststand whant to access the same variable. Is there some conflicts?
    Regards,
    Risotto

    This could be, even though this is rare, but it could happen, that right in the moment when TestStand writes to the global variable, the thread changing happens, and labView might see strange data (for example if the variable is a array, that not all values had been updated, so LabView would see a mi of old and new data). This is a general problem, when working with multiple threads, and is not TestStand specific. The solution is using synchronisation step types, for example the lock steps to secure the access of global variables, files or devices. You place a lock step before and after the step that works with the variable. before the step you "lock" the step, after the step you can "early unlock" it again. When you do the same on some other position, but with the same lock-reference, you can garantuee, that as long as one thread "locked" the lock, no other can do the same, and so your steps following the lock-step are secure.
    Hope that was good to understand. Here you can find some more Information concerning parallel tests:
    http://zone.ni.com/devzone/devzone.nsf/webcategories/F255EBD2FF79B055862567B3006BE376

Maybe you are looking for