design a test system

[bhotu]

Hi!

Design a test system for UUT.

We have test jig which is connected to DIO. We have to put UUT on Test jig and we have all GPIB based measuring instruments. I have to design system using LabvIEW . When we connect UUT to test jig and run program, it tests all parameters and make a report. we have all instruments driver.

I am new user of LabVIEW.

if any body has any idea regarding this project please let me know

thanks

[Chris_Co]

swami1, 

If I understand you correctly, you already have a LabVIEW program that communicates,and controls external devices, acquires data from these devices and makes a report based on the data.  Is there a bug in the program?  Do you need to add features?  Does this program exists? 

If the program does not exist, I do not think you are going to have any luck convincing someone to program the entire test for you.  This board is used to communicate ideas and questions to obtain a higher level of knowlege.  From what I can tell from previous posts, you are not willing to do any searching for yourself (labview examples, knowlegebase articles, hardware manuals etc.  If you have a specific question, then by all means ask it.  Please do not take this response as an offense to you.  I will be glad to help if I can, but a posted code to answer your problem is not what you are going to get every time.  In fact you will learn better if you struggle with it for awhile. 

Now you are going to take some baby steps from the start.

Define your inputs and outputs.

Develop a flow chart.

Research,research,research.  This web service is FILLED with the information to at least get u started. And when you get stuck, post the QUESTION!

Help me help u - (someone said that somewhere)

Chris

Message Edited by Chris Co on 11-03-2006 03:10 PM

[SimonH]

swami1,

Here are some resources that may help you get started:
Resources for learning LabVIEW.
Instrument Control Fundamentals

Also the Example Finder in LabVIEW (goto Help » Example Finder) contains many examples of how to do specific tasks in LabVIEW - this is often a good place to get started.

As Chris said, there isn't much we can help you with until you start to tackle the problem.  Once issues come up during the development phase then we can help you out.

Good luck!

Simon H
Applications Engineer
National Instruments

[bhotu]

hi!

Thanks for your suggestion and I have started programming of my project.

I need some help if you can, My UUT has total 42 model numbers and each has different frequency band and because of that each has different test.

so please let me know if I enter any model number so it will go to that model number test and run all test of that model number

thanks

[Dennis_Knutson]

Didn't you ask the same question here? There are any number of ways that this could be done. You could have an Excel spreadsheet or database file or text file or even LabVIEW constants that define model number, limits, test numbers, or anything else. I becomes an excercise in array maniputlation and table lookups. Think about what you might want to define and how you want to store it before you start writing any code. You want a system that will not only work today but down the road. You need to spend a lot of time up front with basic project design. Do you have a requirements document? That would be one of the first steps.

[bhotu]

hi!

I have already created database using LabVIEW. It's not same question which I asked earlier. I have one product which has 42 model numbers and each has different test according to model number. If I enter any model number in program so that model number test VI has to open and start test.

Ex. NEHz-axxxxby - model number

z=1 or 2, a=A,B or C which indicates gain

XXXX = diifferent frequency bands

if I enter NEH1-A0435by so opens this model number VI and start test with match of this model number parameter.

thanks

[Dennis_Knutson]

So you are planning on having a VI for each model number? If that's the case, then I would assume you would be calling the VI dynamically. As long as the VI name is related to the model number, you can create the path and call it.

p.s. You might want to look at getting TestStand (http://www.ni.com/teststand/). It has all of the features you need in  a test executive so you can concentrate on writing the actual tests and not all of the management functions (test selection, limit loading, report generation, database logging, etc.)

[Chris_Co]

Hi swami,

Based on all the threads i have read and compiled to what i think you are trying to do....  I do not believe you need a VI for each model#.  The inputs to the vi are changing based on model#, however it doesnt seem the actual TEST is changing (just parameters).  For instance, if you are testing a resistor you may test for actual resistance and the current or voltage witch it fails at.  The colored strips (model #) determine the pass fail criteria and the actual voltage or current to apply during testing.  Your model #'s change the Gain, Frequency etc, but these inputs to the TEST VI seem only to change what parameters to output to the same TEST as well as pass/fail criteria.  I hope i understand you correctly, if i do the you will need a much simpler VI, namely ONE not 42.

Another example:  Controlling hydraulic solonoid to facilitate vibration.  Based on serial number the VI will determine the frequency,amplitude,and #of cycles. The machine VI I attached will do exactly that.  Now a control VI will be built to facilitate the control. In conclusion you will have two VI's that will do as required.  Maybe I am misunderstanding you, but I am trying!

Better yet please tell me exactly what it is you are going to do.  Name the component,name the test environment (Vibration,thermal cycling,pressureizing,Voltage, current), name all measurements you want to take, name the pass/fail parameters etc.  Be very specific.  It will not matter if you write 2 pages.

Please, we want to help.

Chris

[tbob]

Use a case structure.  It is similar to text programming language If-Then structure.  Create an Enum with all different model numbers.  Wire Enum into the case structure selector (?).  The title inside the case will display the first and second enum entries (model numbers).  Add cases by right clicking on the case structure border.  As you add cases, the next enum should show up in the title.  Inside each case, put the parameters for that model, such as frequency, etc...  Then wire each parameter to the right side of the case structure.  Each output of the case can then be wired to a subvi designed to accept these as inputs.  So depending on which enum is selected, the correct parameters will be passed to the subvi.

Message Edited by tbob on 11-09-2006 10:46 AM