Batch FileGlobals data for each UUT seperate

[kosist90]

Thanks, Bill, for the provided sequence...

Could you show code module, or block diagram of the step "Read Recipe File.vi"?

Also, I have broken PropertyLoader step. I noticed, that you have to cases for it based on socket number. Are you sure, that it does not cause problem? What values do you load, and can they influence on later assigning of FG variables values?

Thanks,

[Bill_Lewis]

Here is the block diagram that sends the user interactions to the output cluster. This cluster is then passed to the TS seqence and then assigned to fileglobals.

I added the property loader to load in from a spread sheet some default values. I would expect it is because you don't have the spreadsheets. What do you think?

[kosist90]

Yes, you're right - PropertyLoader step is broken b/c of missing spreadsheet...

I have some thoughts regarding your code

• I did small test, created similar VI, and checked, whether values in sequence will be changed, or not. 

So, if I was changing Cluster In values, then from Cluster Out to FileGlobals were stored different values, based on inputs:

But, if I do not change Cluster In (and you have for such a case boolean output from Message Dialog "Yes, I changed it"), and just pass it out - all the values are default. Although, they are set up from the test sequence, as you can see:

The point is, that while you do DefaultValues.ReinitAll, it will reinit values of your cluster. And if you will just pass wire from it via Event Structure, on the output will be cluster with default values. Moreover, if you will update cluster value, but not read its value via LocalVariable, or PropertyNode inside of Event structure, then on the output of the wire will default values.

• Do you change values for Socket1 and Socket2 during sequence run? If just for Socket1, and for Socket2 you do not change value, then upper described situation appears.
• I see, that one case of EventStructure passes default values of cluster wire (there is dot inside). Is there a chance, that for 2nd socket, that Event Case is executed?
• What do you have on the False page of Case structure? Is there is just passing thought the cluster data, it'll be empty on the output (if, of course, you do not modify it somewhere else inside of the Event Structure, and write it to shift register from Local Variable, or Property Node of the cluster.
• Cosmetic advise: do not close references from VI Server. You don't have to do it, LabVIEW will take care about it, and it's completely OK not to close it.

I would recommend you just to play a bit with your VI (or create something simplified, as I did), and debug its behaviour. It'll help you a lot.

Looking forward for news from you,

Sincrerely, kosist90