NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Modal message popup hangs parallel model in Teststand 4?

Hi:

I'm having a problem using the 'Make Modal' option on message popups. It is hanging the user interface.

Here is what I've done:
* created a sequence with just a message popup in it (using Teststand 4.0 editor)
* set the popup to be modal
* set the sequence to use the parallel model
* recompiled Full Featured CVI User interface for teststand 4.0 (using CVI 8.0.1)
* run sequence in the recompiled user interface
* popup is displayed
* after acknowledging the popup, the popup and the user interface freeze

If I change the sequence to use the batch model, everything works.
If I don't recompile the user interface project that came with Teststand and just run the exe, everything works.

What am I missing? Sequence file attached.

Thanks,
Dave

0 Kudos
Message 1 of 9
(4,663 Views)
Hi dseel,
 
I've been trying to reproduce what you described, but so far I haven't been able to do so...
This is what I've done:
  1. Downloaded your sequence file
  2. Tested in Sequence Editor with Parallel Process Model (worked fine)
  3. Tested in CVI Full Featured OI, prebuild executable (worked fine)
  4. Rebuilt OI in CVI 8.5 and retested (worked fine)
  5. Rebuilt OI in CVI 8.0.1 and retested (still worked fine)

Did you make any changes to the Operator Interface code?
Also, does the OI and Popup freeze momentarily or completely hang the application? Does it happen every time, or sporadically?

Jervin Justin
NI TestStand Product Manager
0 Kudos
Message 2 of 9
(4,642 Views)
Hi:

Thanks for investigating.
I did not alter the operator interface at all (for this experiment).
The OI and popup freeze and hang the application indefinitely. It happens every time.

I've attached the testexec project and the executable.

We have modified the modelsupport2 DLL used by the parallel model (and batch model). But if this is the issue, I'm confused why the original testexec.exe worked and not the recompiled one. I've attached this file as well.

Thanks,
Dave


0 Kudos
Message 3 of 9
(4,635 Views)
Hi:

I just double checked and there is one correction.
The original testexec.exe *does* hang on the popup. But only the full-featured version. The simple version works fine.
Sorry about that.

Cheers,
Dave
0 Kudos
Message 4 of 9
(4,633 Views)
Hi dseel,
 
After I copied over your version of modelsupport2.dll, I see the attached error message for every test socket, basically saying that TestStand can't find a certain function in modelsupport2.dll.
What modifications did you make to the dll?
 
One thing though, I notice the same error message even with the Simple OI... Where are you putting modelsupport2.dll? In the same folder as the CVI Executable, or in <TestStand>\Components\NI\Models\TestStandModels?
Jervin Justin
NI TestStand Product Manager
0 Kudos
Message 5 of 9
(4,624 Views)
Hi:

We are putting all modified files such as this in:
C:\Program Files\National Instruments\TestStand 4.0\Components\User\Models\

The model support file has been changed in quite a few places. I believe it was modified from the teststand 2 version. We don't use the XML report generation, only text. Try attached.

Cheers,
Dave
0 Kudos
Message 6 of 9
(4,611 Views)
Is it possible a modal dialog is getting displayed underneath your main UI window? If you can reproduce the problem it might be worth checking.
-Doug
0 Kudos
Message 7 of 9
(4,599 Views)
I don't see any other popups. I minimized all windows, and I checked in the task bar.
I see windows for the test executive, test uuts (parallel model panel), and the popup.
- Dave
0 Kudos
Message 8 of 9
(4,596 Views)
I just tried renaming my C:\Program Files\National Instruments\TestStand 4.0\Components\User directory. Teststand rebuilt the User directory defaults and I ran the full featured testexec again. Popup still hung.

I believe this means modelsupport2 and anything else we modified in the User directory can't be at fault.

What are the differences between the simple and full featured execs that could cause possibly cause this behaviour?
Is there any other information that I can provide?

Cheers,
Dave
0 Kudos
Message 9 of 9
(4,594 Views)