make a product code map and put the report in this map when tested

[darkxceed]

Hello,

I'm new to teststand so this might me a simple question.

I want to be able to sort the report files in different directories, this way it will be easier to loopup the data.

First I want to be able to enter a product order and a serial number(now I can only enter a serial number)

Year = 2011

ordernumber = 555555

serial number = 1100012

sequence name is = 4022123456.seq

The directory must look something like this:

...reports\2011\555555\4022123456\1100012[time][date].html

So if directory 2011 is not there it has to be made by teststand

If directory 555555 is not there it has to be made by teststand.

If directory 4022123456 is not there it has to be made by teststand.

The directory 4022123456 will contain all the serial numbers from 4022123456.

gr,

Bart

[~jiggawax~]

I'll let Captain Jack answer that one.  Have you tried this yet?:

http://forums.ni.com/t5/NI-TestStand/Dynamically-changing-the-report-path/m-p/1116147

All you have to do is store your variables to FileGlobals and then insert them into the correct path location.

[darkxceed]

Hello jigga,

I think I need a good manual to understand how to use teststand because I know what locals.variables means.

But RunState.Root.Locals.ReportFilePath does not tell me anything.

I need a book of better a pdf manual to know how these work.

gr,

Bart

[~jiggawax~]

Hey Bart,

I understand... It's hard to know where to start with TestStand.  There is a lot to it at first.  Generally when you install TestStand you will get a bunch of PDFs located here: C:\Program Files\National Instruments\TestStand 4.1.1\Doc\Manuals.  Your version of TS might be different so the path might not match exactly.  Inside of that folder you will see the Reference Manual which is great for telling what is what in TestStand.  The other good manual in there is the UsingTestStand.pdf.  That one is like a course except in PDF format. 

So when it comes to Callbacks, Variables, RunState crap, TestStand API stuff.....you can refer to those manuals to see what is what.  The other great source is the TestStand help itself.  It is set up like a standard Windows help and uses index and search the same way most windows apps work.  The index is great for typing in something if you see the name and want to know what it is.

Basically in your app you will have to get that information somehow (i.e. the dates, serial numbers, sequence names....etc..). Some of it you can get through the API.  So for instance at some point you either have to read a database, file or the user has to input some of that info.  In that case you would save it off to a variable for use in the ReportOptions callback.

Hopefully this helps some!

[darkxceed]

Ok,

I got the report pathing done.

Now I need to change the UUT information dialog box.

At the moment only a serial number can be entered but I also want to enter a order number.

When searching in www.ni.com I found http://digital.ni.com/public.nsf/allkb/1E32621FC9A92CBE862577F20070A5F3

As mentioned they tell me to open it in cvi and adit it there, problem is I dont understand cvi, only labview and a bit teststand :).

Is there an easier way to do this?

gr,

[j_dodek]

Hi

You may do this in LV of course, and you have to override the PreUut Callback or do your modifcations in the model at all

if this change should affect all your Tests. All you need to do is to replace the CVI module by your LV module. 

It sounds that you are trying to enter an "intermediate" Teststand state.

You have the order number ? How you will process it further ?

I recommend to visit a TestStand basic course. It is better to spent 3 Days in school

than figure it out in 3 weeks for a task that can be done in one day with good basic knowledge.

Regards

Juergen    

[darkxceed]

J_dodek,

Thnx for the reply.

I will visit the course as soon as its available.

Problem is that I have to make a test that is ready on the end of march.

I see this step is too difficult for me now, I maybe thought there would me some example UUT dialog boxes.

gr,

Bart

[j_dodek]

Hi Bart,

Just try this simple example

Regards

Juergen

[~jiggawax~]

Bart,

I'm glad you got the reporting working! 

As a general courtesy to others searching the forums it is good practice to ask seperate questions in new threads.  That way people won't have to parse through info they don't care about. 

It's perfectly fine to start as many threads as you want.  Just try to avoid asking questions that pertain to different subject manner in the same thread.

Happy Coding!

[darkxceed]

Thnx for the example.

I also thought of something you made for me, but maybe it's better if I disable the UUT dialog and make a labview dialog.

Problem is that I have to press run every time I want to test a product.

Maybe an if statement would help, but then the report will not work good I guess.

But as mentioned I'm getting very off topic.

gr,

ps. where can I get Windows SDK for CVI? from NI or?