LV producer consumer and TestStand

[mrbean]

In the TestStand process model, I've replaced the original Get UUT Serial Number dialog with a custom dialog that has some additional fields, and will (eventually) allow the operator to BarCode scan the serial number.

I'm thinking about using LabVIEW's template for Producer/Consumer.  I basically want to allow the user to hang out at this dialog until the click on either "START" or "CANCEL".  They can tab to the different fields, and Scan in the serial number if desired.  What types of 'events' would I want to capture?  Is this even the right design pattern for this situation?

Also, this dialog needs to be modal (in front of TestStand executive). 

Thoughts?

[GovBob]

mrBean,

 By custom dialog do you mean a seperate VI that you open and show the front panel when the step executes?

If that is the case the producer consumer might be overkill. From what I've seen one of the main reasons one would use this pattern is to seperate the acquisition loop from the data record loop. In that manner the data recording doesn't slow down the data acquisition. I've used a wedge type barcode scanner in the past and it is pretty easy to impliment.

On a side note I really enjoy reading your posts on both of the forum boards. I too at some later date will be creating a custom operator interface using LabView and your questions have been really helpful in my formulation of a plan. Thanks

[Dennis_Knutson]

I agree that it sounds like it's overkill. I've written custom TestStand dialog screens with multiple entries besides the serial number and a basic event structure with Value Change events is about all that you would need. To automatically go to the next field after a data entry, you set the key focus of the next field.

Assuming a hand held wedge or usb bar code scanner, all you need is a string control for it.