Add indicator to TS-Execution Display

[trout00]

I read the TS Simple OI with Yield Info. I am still confused.
My goal is to have a simple indicator on the TestStand-Execution Display. Vi front panel. So I place a numeric indicator on the front panel.
In Sequence editor, I use the API method and passing in the NumericDataParam = locals.testdata
with the UIMsg_UserMessageBase+0. So far, I understand this part. The next part is to have TestStand -UIMessage Handler.VI, inside the "No Event" case, add a case structure with a number 10000. Inside this 10000 case add a UI Message property with Numeric Data. Here I wire a numeric Indicator to the output of the property node. Here my confusion. The indicator on the TestStand -Execution Display (the one I just added) does not
have anything to do with the TestStand- UIMessage Handler.VI. Should I modify the TestStand- Excecution Display.VI with the "No Event" case or the TestStand- UI Message Handler.VI.
Please clarify.

[Ryan Ramcharan]

Hi trout00,

You have 1/2 of it 🙂 The UIMessageHandler.vi is only responsible for checking the UIMessage event code and then "expediting" the UIMessage to the correct Execution Display VI. Remember that there may be multiple execution display VIs each corresponding to a particular execution. The TestStand engine just fires UIMessages and does not group them by execution. The UIMessageHandler VI picks all of these up and then checks which execution posted the message and sends it to that execution display. If you look at the other cases, you will notice that the UIMessage object is bundled with the execution display name and sent through a queue to the corresponding execution display VI. Everytime you start a new execution, a copy of the execution display V
I is created and titled tempexecVI# (where # is a unique idetifier for each execution). If you open the execution display VI you will see that there is another loop that monitors for incoming messages. It is in here that you must add a case for your custom message and update the numeric inidicator as you were doing in the UIMessageHandler. This is quite a complicated process, and I am sure the folks over at NI support will be happy to explain this in further detail should you require. Hope this short and brief explaination somewhat helps.

Bob