Good NI Test Stand Examples For a Beginner (Using LabVIEW)

Hi everyone, I am new to using NI Test Stand.  I have gone through the "Getting Started with NI Test Stand" and "Using LabVIEW with Test Stand" documents.
I know in the NI Test Stand Example folder there are many examples.  Are there any examples that cater to new users to Test Stand?
Where can I find good examples (demos) for developing test sequences, local variables, parameters, etc...in Test Stand?
Thanks so much!

If you have the SSP you could access online training an do the exercises on the training.
but the examples is a good way to getting started. just play around with all the options you have.

Similar Messages

  • Making another counter VI for usb-6008 using Labview 8.5

    I want to create another counter for usb-6008 using Labview 8.5 as it is needed to calculate two speeds simultaneously.
    Solved!
    Go to Solution.

    The best way to do this is to use the counter.  The counter counts
    signals without having to interrupt the system or use the USB bus. 
    When you request the number of ticks that the counter has seen, a
    request is thrown from the CPU to the USB line to the 6008, which then
    asks the counter "How many ticks have you seen?"  That number is
    returned over the USB bus, goes to the CPU, and then displays on your
    screen.  Since the DIO lines on the 6008 are software timed, there is
    no way to guarantee that the data returning to the CPU is
    deterministic.  The conceptual difference between software-controlled
    DIO (which nondeterministically returns an entire data stream) and a
    software-tick-request-controlled counter (which returns a single number
    with the number of ticks) prevents us from using the DIO lines on the
    6008.  The cheapest way to count more edges is to purchase more 6008s. 
    Another possibility would be to purchase a PCI counter board such as
    the PCI-6602, which has 8 counters. The most counters we offer in the
    USB form factor is 2 per device.
    -John Sullivan
    Analog Engineer

  • Test stand design for high speed brushless dc servo motor efficiency testing

    We are in the process of designing two test stands around the brushless dc servo motor in the attached specifications.  The first we would like to operate using Labview and a PXI-7352 controller.  The second will be a real time configuration.  The motor will need to run in the 25-50,000 RPM range.  We want to bring the hall sensors back to the controller and do PID and other control there.  The sinusoidal commutation from the controller would then go to an as yet unselected servo amplifier.  When the motor is under test we want to be able to measure accurately the power that is being used by the motor - not the motor and controller / amplifier.
    Can the PXI-7353 handle this motor speed range?
    Will Labview and the PID toolkit be sufficient software to program the first test stand?
    Any example VI's available for this approach (I could not locate any)?
    What is the appropriate controller for a real time system?
    What is the best way to instrument the motor to determine power required at a given test point?
    Any suggestion on a servo amplifier?
    Thanks in advance,
    David
    Attachments:
    B0912-050 Brushless Motor.pdf ‏91 KB

    Mr. Zaatari,
    As you will note, there are six questions posted above.  As you also know, I have been waiting for your response for 5 days and decided to use this alternate method in hope of getting my questions answered.  As you further know you have not answered these questions.   It is a shame that you will  not post your "answers" here so that the rest of this wonderful NI community might have the benefit of your knowledge as well.
    I will respond further to you by email.
    David

  • What is test stand ? Why is it used, how to get going ?

    Hello All,
    I am LabVIEW user and very new to test stand, have few basic questions,
    1. Why teststand was introduced ?
    2. In LabVIEW we write VI's and build a project to execute a big task, how is this done in teststand?
    3. I did download some of the pdf from NI website, but not able to visualise what needs to be done,
    Pls do share if you have more insight to Teststand.
    Thanks

    Hey systemcrash,
    I will try and answer your questions the best I can:
    1. http://www.ni.com/teststand/whatis/
    TestStand is an automated test executive (ATE).  It is an off the shelf solution which makes your life easier.  It handles report generation, user management, sequencing (i.e. test flow), result collection, pass/fail analysis, common User Interface, database logging, etc...  Basically, all the crap you don't want to develop in LabVIEW.  But it gives you consistency and commonality for all your tests.  If you look at the layers of the test system TestStand would be at the top like this:
    TestStand
    LabVIEW (or other software)
    Hardware Drivers
    Instruments
    UUT (unit under test)
    2. In TestStand you have the development environment (Sequence Editor) and the User Interface.  They can both execute tests.  The User Interface is an application written in LabVIEW (or other programming languages, ships with TestStand) which gets deployed to a test station so that testers can execute your test.  It does not have the ability to edit the test (in TestStand tests are called Sequence Files).  However, the Sequence Editor can edit the tests and would be used on the development machine.  There is a deployment utility in TestStand which allows you to create an installer.  In that installer you would include the TestStand Engine, the User Interface and all the dependencies for your test (Sequence File).  Then the user just opens the User Interface and runs it.
    3. NI does offer TestStand courses which can be helpful.  I recommend going through these PDFs though first:
    http://www.ni.com/pdf/manuals/373200c.pdf
    http://www.ni.com/pdf/manuals/323436a.pdf
    You will get more out of the classes if you have starting playing around with it first.
    Hope this helps.
    Regards,
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~

  • Labview example for data capture using 5102 scope card

    How can I program a Labview Vi to control, and capture a waveform using the 5102 scope card. I need to be able to set it up to continually capture a waveform (Channel 1 and Channel 2) when triggered on a rising edge of channel 1 and then store the data on disk automatically, then wait for the next trigger.
    Any help or tips as to how I could do it would be helpful.
    Thanks
    Allan

    Allan,
    Please find the attached zip file that has some useful LabVIEW examples with scope 5102
    Zvezdana S.
    National Instruments
    Attachments:
    scope.zip ‏181 KB

  • Which operating system is best for computer control using LabVIEW

    I am using LabVIEW 7.1 and want to write a program to control a system of pumps, heaters, and  compressors.  I am wondering if using Windows XP is a bad thing, given how many background processes computers tend to use these days.  I don't want my computer to slow down for intermittant checking for updates, or any other sort of routine maintenance computers are set up to do.  I have heard mixed things about windows reliability and computer control, most of which is people saying windows could crash and completely ruin my tests.  Does anyone have any advice on the best operating system to use for continuous computer control of my system? 

    If you plan on using a desktop PC for control type applications, then your best option in terms of performance will be with a Real-Time operating system. Windows is not deterministic for many reasons. Determinism involves the ability to respond to an event within a specified amount of time with an acceptable amount of error (jitter). First of all, Windows is not deterministic because it has to service mouse and keyboard events, as well as anti-virus software, automatic updates, etc.
    You can, however, convert an existing desktop PC to a Real-Time target with a Real-Time OS and use it for your control type application with the deterministic behavior of PXI, Compact FieldPoint, and other Real-Time targets. Check out this link for more information.
    On a side note to a previous reply, using the LabVIEW Real-Time module on Windows XP won't make your application deterministic. Your best bet, as others have noted, is to use the LabVIEW RT Module on an RT OS with good RT programming practices (avoiding memory allocations, etc.).
    Jarrod S.
    National Instruments

  • Any LabWindows/CVI examples for SPI communication using DAQmx?

    I have a PXIe-6363 module in a PXI running as a real time target, and I'm trying to talk to an accelerometer that communicates with SPI.  I know the 6363 isn't one of the special modules built for SPI, but my understanding is it should be capable; the issue is just the programming.  I've seen examples of this for LabVIEW using DAQmx.  Are there any examples out there for doing it in LabWindows/CVI?
    I'm looking to save time and avoid reinventing the wheel here.  SPI is easy on an Arduino, so it should be doable in LabWindows/CVI, right?  
    Thanks,
    Matt

    Hey Matt,
    I was unable to find any full examples of SPI communication with DAQmx in C. My best suggestion would be to use the LabVIEW examples and implement the same series of function calls to implement the LabVIEW code in C. The DAQmx C API is good about keeping a standard with naming conventions to map with the function names in LabVIEW.

  • New to Mac and I am looking for a good app to process labels for envelopes. Used to use the Printmaster program on the PC side.  Wondering if "Pages" Iis the correct program to buy of is there another option. Thank you.

    New to Mac and used to use a program called print master for making all kinds of labels etc. I am looking for a good app to do the same.  I was wondering if the Pages app was the right choice to do the labels etc.  I understand that pages I'd a word processing app but I was unable to tell if it could do what I was looking for. Any suggestions would be greatly appreciated

    The Contacts application will print envelopes and is already on your iMac. See this Apple article for information on how to do it.
    Best of luck.

  • Example for Tagging API using EJB3.0 on Jboss Application Server

    Hello Friends
    In EJB 3.0 development I am searching for Taging API implementation using JBOSS application server and Netbeans 5.
    If anyone has tutorial to do so please post the link.
    Thanks in advance.
    Ravi Phulari

    Hello Friends
    In EJB 3.0 development I am searching for Taging API implementation using JBOSS application server and Netbeans 5.
    If anyone has tutorial to do so please post the link.
    Thanks in advance.
    Ravi Phulari

  • Need an Example for Enterprise Services using PI

    Hi
      I have been trying to configure and execute the demo - Cancel Flight Booking, but have been facing some issues on the configuration front. So if any of you had done any simpler examples, i would like to go through them. I'm very new to SAP and I want to learn about looking up,invoking enterprise services using PI. So kindly help with providing any custom made simple example with the configuration steps.
    Thanks & Regards
    Vijay

    Hi,
    habve you see this demo:
    /people/jitender.chauhan/blog/2009/04/20/service-enabling-in-abap
    Regards,
    Michal Krawczyk

  • RS232 programmin​g for Sartorius scales using LabView

    Has anyone written a any code to control and read in data for a Sartorius scale with RS232

    Hi,
    Unfortunately, I was unable to locate a driver for your instrument at www.ni.com/idnet or at the Sartorius website. I would like you to submit a request for this driver at: http://zone.ni.com/idnet97.nsf/instrumentdriverreq​uest/ and with the instrument manufacturer. We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
    If you would like to try developing your own instrument driver (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at :
    http://www.ni.com/devzone/idnet/development.htm
    We also have a syndicate of third party vendors that specialize in National Instruments' products and services. Some of the vendors specialize in driver development. I would suggest contacting one of the Alliance members at:
    http://www.ni.com/alliance
    An instrument driver is a collection of functions that implement the commands necessary to perform the instrument�s operations. In short, someone read the instrument user manual and implemented some of the functionality in a program for the end user. Instrument drivers are not necessary to use your instrument. They are merely time savers to help you develop your project so you do not need to study the manual before writing a program.
    There are example VI's in LV on Instrument Connectivity. If you go to the Help menu >> Examples.. >> I/O, you will see a couple and Examples.. >> Fundamentals for File and String manipulation. I would suggest tweaking them to suit your application. Also the specific command that your instrument responds to can be found from it's manual.
    Some useful resources for your application are
    ni.com > NI Developer Zone > Development Library > Instrument Connectivity
    http://search.ni.com/?col=alldocs&layout=TechResou​rces&ql=a , to search examples and knowledge bases
    Hope this helps!
    Best Regards,
    Aaron K.
    Application Engineer
    National Instruments

  • Is there an ILX LDC-3916 Laser Diode driver for windows NT using Labview 5.0?

    Or will it be necessary to upgrade to the 6 version? I have searched for a while now but this is the only verion that I could find. Also is there any where to learn how to communicate using a GPIB board?

    Here are the drivers. They may work with LabVIEW 5.0, but may be compiled in LV 5.1.
    LDC-3908 8-Channel Laser Diode Controller Mainframe 39XX.LLB
    LDC-3916 16-Channel Laser Diode Controller Mainframe 39XX.LLB
    LDC-3916371 Controller Module 391637X.LLB
    LDC-3916372 Controller Module 391637X.LLB
    LDC-3916374 Controller Module 391637X.LLB
    LDC-3916376 Controller Module 391637X.LLB
    LDC-3916332 Dual Current Source Modules 391633X.LLB
    LDC-3916334 Dual Current Source Modules 391633X.LLB
    LDC-3916550 Dual Temperature (TEC) Control Module 391655X.LLB
    LDC-3916338 3 Amp Current Source 3916338.LLB
    -Jim
    Attachments:
    ilx39xx.zip ‏1501 KB

  • Software enable for Kollmorgen AKD using LabVIEW

    Hey all, I'm relatively new to motion control, and feel like I must be missing something...
    I have a PXI chassis with a 7350 card connected to a Kollmorgen AKD as described in the Getting Started guide.  I can get the system to move through MAX, and I can enable the hardware through the LabVIEW Enable Axes.flx vi from the NI 73xx palette.  But, I haven't found any way to do a software enable from LabVIEW... it only works through the Kollmorgen software.
    Is there a way to do the software enable from LabVIEW?  I haven't found anything in my searches so far.
    Thanks,
    Joe Z.
    (trying to quit LabVIEW, I swear)

    The only way to software enable the drive from LabVIEW is via a digital bus (EtherCAT, Modbus, etc). In general, you only want to use either the hardware enable OR the software enable, not both. In your situation, you should be using the hardware enable and you should use Kollmorgen WorkBench to set the drive to be software enabled at startup (on the Enable/Disable menu).
    Thanks,
    Paul B.
    Motion Control R&D

  • Passing arrays with Test Stand to DIO 96

    Does anyone know the easiest way of sending data arrays from Test Stand to a DIO 96 using a LabView dll? I have a Test Stand sequence where I will need to set bits and read bits from a DIO 96 and am going to make a LabView dll. I guess I will need to pass either arrays to and from each port or numeric data to and from each port to a dll and also figure out how the status of the bits in the DIO 96 will be remembered.
    What is the best strategy for dealing with Test Stand and a DIO 96?
    Has anyone any ideas or example code?

    Hi Steve,
       either approach is perfectly valid, and as you say, the activeX approach does remove some of the flexability of where you get the data from, however, what you've really described is two separate things, rather than two separate styles of approach.
    ActiveX or direct passing are simply the means of getting data from and to your TestStand data space.
    Step types are a convenient way of wrapping up particular layouts and functionalilty into a very easily re-usable TestStand development item. You would still need some sort of code module to put with a step type, so you're not necessarily limiting your developed code to the Teststand environment.
    Making links through ActiveX allows you to make a solid definition on configuration type items, and allow for edit substeps. For example, the NumericLimitTest step type has step.limits.high and step.limits.low. Rather than pass those to the edit substep as a dll call (which is perfectly valid), passing the sequence context (which also allows you to run the termination monitor etc) allows for the fixed references to the fixed data layout of the step. Self containment like this works when the data sources are fixed as you get with a step type to use the edit substep, or the pre/post substeps.
    Working on a dll call allows more re-use because then you concentrate on the data, rather than where it's come from, however, for large amounts of different sources, the dll prototype can become very complex and difficult to document. You end up having to pass lots of parameters and some of them you might not use.
    The question you're ultimately trying to answer is "what does it do to my architecture?"
    The holy grail of TestStand architectures is any step type can be used in any sequence in any sequence file with any process model under any operator interface. Now this isn't always practical, but the closer you get to it, the more flexibility your system as a whole contains, and the easier it becomes to add in or change the layout / functionality of the system
    With this comes code re-use, but the extra development time it takes to make good re-usable maintainable code isn't re-couped until the 4th or 5th re-use.
    If you want in this case your passing of the array to occur from many different places in your sequences, and you're building up lots of sequences to use them, then making a step type, and passing through the most convenient method you decide upon will make the implementation of the sequences easier to do.
    If you only need it in a couple of ways, then you can do without the step type, and if it's not many different data sources, then pass by parameter to the dll through the function prototype directly, and use a regular DLL adapter to acheive it.
    Mostly my 2-cents worth.
    Thanks
    Sacha Emery
    National Instruments
    // it takes almost no time to rate an answer

  • Configure Event Callbacks in test stand using labview

    Hi,
    I was going through Full OI - Configure Event Callbacks.vi in the test stand example. Can you please explain me how the vi works and what is techniwue behind it?
    When i open the individual VI's in the reference, I could see more that 1 control in the front panel. But Only the user parameter is wired in the vi? Why is it so?
    Regards
    Gopal

    Hi Gopal,
    When the TestStand Engine fires events, this VI specifies how your Operator Interface will respond.  For example, let's examine the first event callback registered in Full OI - Configure Event Callbacks.vi , Exit Application.   When the TestStand Engine receives the message to shutdown, and then finishes its neccessary shutdown procedures, it will send a message to the Operator Interface.  For the Operator Interface to receive this message, it must "listen" for it.  In LabVIEW, this is done by Registering an Event Callback.  See the links below for details on how to implement this. 
    The answer to your specific question is in step 7 of the first link below.  When TestStand sends the message to LabVIEW, there is information that is always passed.  The other input controls contain this information.  To create a VI that always includes these controls, right-click on the VI Ref input to the Reg Event Callback Property Node, and then select Create Callback VI.
    Here are two references that talk about handling ActiveX callbacks in LabVIEW in general:
    Registering and Handling .NET and ActiveX Events
    Register Event Callback (Not in Base Package)
    Cheers,
    David Goldberg
    National Instruments
    Software R&D

Maybe you are looking for