Gather UUT serial number, later in sequence, and skip UUT dialog at the beginning

[david_feo]

Hi all,

what is the best way to gather the UUT serialnumber later in the test sequence (our UUT has the serialnumber stored, and we want to gather it via a DLL call later in the sequence) and skip the UUT serialnumber input dialogue?

Database and report should be in accordance to the serial number that is read from the device from within the sequence.

Looking forward to your hints!

Kind Regards

David

[mavimi]

Hi

Make a callback sequence that overrides the PreUUT sequence in the model.

You can call your dll in your custom PreUUT, and store the serialnumber in the Parameters.UUT.SerialNumber.

By making the callback yourself, you avoid the dialog, but the data is stored as it would be using the dialog.

Regards

[~jiggawax~ · Accepted solution]

Why wouldn't you just override the PreUUT callback and put your own dialog in there?  Why does the Serial Number collection have to happen later? If it's a matter of having the UUT on then you can override the Process Setup callback and turn the UUT on.  Or you could even turn it on in the PreUUT or PreUUT Loop callbacks.

Typically what people do is override the PreUUT callback and put their own VI/DLL calls in there to do barcode scanning or other serial number entry.

You will have to be aware of the Continue flag.  That's what stops execution.

More info on Callbacks: http://zone.ni.com/devzone/cda/tut/p/id/6605

Using the Process Model correctly: http://zone.ni.com/devzone/cda/tut/p/id/7958  Pay special attention to the part pertaining to callbacks.

Another one with a callbacks section: http://zone.ni.com/devzone/cda/tut/p/id/2694

Check out my first post here: http://ni.lithium.com/t5/NI-TestStand/Intercept-the-PreUUT-callback/td-p/998605

Hope this helps,

[RayFarmer]

If you have to get the serial number later in the process then beware that you will have to change the ProcessModel, because the path to the Report is generated before the MainSequence of the Client SequenceFile is called. So you would have to move this to after the point where you enter the serial number.

Also if you are going to use on the On the Fly reporting then you will have to start a temporary file so your report can be generated, that is if you dont get your serial number until after your test have been run.

[david_feo]

Jigg thank you for your reply.

Yes we need to power it up with several sequenced steps, but we could put this in the pre UUT Callback sequence then.

I was aware that the UUT serial number will influence later behaviour of the model / reporting and so on.

Kind Regards

David

[david_feo]

Ray,

thank you for the hint, that was what we where afraid of ....

Kind Regards

David

[mavimi]

Where I work, in my most recent project we do a couple in things in the PreUUT

We scan a barcode marked on the UUT, and check against a database, if its valid and so forth.

So imho its perfectly valid to power up the device in PreUUT in order to gather the serialnumber in the place where its intended in the model.

This means though, that you will not get statistics of failing devices - that fail because there is no communication. You could probably work around this with dummy numbers, but when it comes to tracebility you will not record 'failed' UUT's at this point.

This is why we chose to use a serial number marked on the uut and scan this before testing. We could have chosen to power up the device - check if there is a stored number, and use this if present - or generate a new if there was no number (first time tested).

But we went with marked serialnumbers, they do not depend on functionality of the device, merely upon barcode quality. Thus it will give a more correct statistics. (Especially if you have a lot of failing devices - which we of course do not hope for 🙂

Sorry if I twisted the subject a bit - but these were some of our considerations about the serialnumber gathering at my workplace.

Regards