Non-Zero Socket Indexing in Executions

[Taylorh140]

So The Team Has voted and I must use non-zero indexing for my test sockets

I followed the guide to change the index in the Batch Dialog  

http://digital.ni.com/public.nsf/allkb/A6D0EF1F4FE5EC94862570AE000CE374

which doesn't matter so much anymore since I replaced the dialog. What does matter is the name of the executions and that they match the physical socket number.

here is a more visual example.

I did note the NOTE on the 

How Do I Change My Test Socket Numbers to be Non Zero Based? 

guide.

Note: This procedure will not change the numbering of the Testsockets in the process model, as doing this would take more emultiple modifications.

I only want to change the Executions Sockets above so they match the non Zero Test socket number in the dialog above. Any help would be appreciated.

[timtamslam]

Hey Taylor,

This is a really good question. I'm able to locate where the batch model creates Test Socket (BatchModel>Initialize Test Socket>Create Test Socket Execution), I'm just not clear on the appropriate action to take in modifying this to alter the appearance correctly. I'm not sure if this is as simple as modifying the process model either. We may need to modify the calling .dll (as described in the KB you mentioned) but I definitely need to look into this. I will get back to you as soon as I find more information.

[timtamslam]

Hey Taylor,

From what I can see, it looks like the Allow Test Socket Threads to Continue - Initialize Step is responsible for appending the indices for the execution sockets.

The .NET step mentioned above calls into the ManagedModelSupport.dll. I'm wondering if we should be able to use a similar step to the KB you listed and modify the ManagedModelSupport.dll. Were you able to find anything else useful up to this point?

Another question I have is, how important is this modification for your system? I'm just concerned with the feasibility of accomplishing this task, as it is not a simple modification it seems. 

[Taylorh140]

Well Timothy,

First I must say that I greatly appreciate your work looking into this. 

The importance of this is strictly related to providing less confusion to the test operator once sequence development is finished.

I am using a limited operator interface so they can look at executions and see how the test are following along. My concern is that they will look an see that execution socket 1 has failed and then remove the UUT execution socket 0 to troubleshoot. Little things like this can cost time and money. But given that the operators are somewhat intelligent. I shouldn't have to worry about this... I hope.

A solution that might be more helpful is say a floating message box that is periodically updated with the test status for each of the UUT? Perhaps you would have some knowledge in doing something like that?

[D-Cubed · Accepted solution]

Hi Taylor,

In order to change the way the index is displayed, you can modify the Configure ListBar VI in TS Full LabVIEW UI Dependencies.lvlib. The specific modification is to change the string input of the ExecutionListConnection property node's DisplayExpression property. The input has the default value:

"%CurrentExecution%\n" + ("%UUTSerialNumber%" == "" ? "" : (ResStr("TSUI_OI_MAIN_PANEL", "SERIAL_NUMBER") + " %UUTSerialNumber%\n")) + ("%TestSocketIndex%" == "" ? "" : ResStr("TSUI_OI_MAIN_PANEL", "SOCKET_NUMBER") + " %TestSocketIndex%\n") + "%ModelState%"

You can replace this with the following code:

"%CurrentExecution%\n" + ("%UUTSerialNumber%" == "" ? "" : (ResStr("TSUI_OI_MAIN_PANEL", "SERIAL_NUMBER") + " %UUTSerialNumber%\n")) + ("%TestSocketIndex%" == "" ? "" : ResStr("TSUI_OI_MAIN_PANEL", "SOCKET_NUMBER") + "str(val(%TestSocketIndex%)+1)\n") + "%ModelState%"

The tag of interest is specifically: "str(val(%TestSocketIndex%)+1)\n".

Let me know if you have any questions.

Warm Regards,