running step "message popup" with image make the test jammed

[Roy81]

Hi Master, I need your help.

I am a beginner of TS. I installed TS2010.

When I first want to try message popup step with a pic, I found my TS jammed.

attached pic 1.jpg shows the setting of the step.

Normally when the first time running the step, the popup message with image could be shown.

But after push OK button, test jammed. At that moment, I can do anything but let the sequence continue.

The status is not stopped, not break.

attahced pic 2.jpg shows the status when I run the step.

Running normal popup message could work. 

I ever try start windows in safe mode. It works. pic can be shown

[Norbert_B]

Does pressing the debug buttons like "step over" have effect once you enter the state you have captured in screenshot 3?

If yes, you probable have configured TestStand to automatically enter single stepping mode.

Norbert

[Roy81]

Hi Norbert,

Thanks for prompt reply.

But the “step over” button is gray and can't be operated.

The general status seems like something is running, but actually the arrow stop at the step.

[Roy81]

I ever tried stop any services and startup items of Windows. But it does not work.

[Roy81]

update

I just try "single pass". It works.

why? what can I do for next? always use single pass?

[Roy81]

update

find the root cause, but still a question

skip one step in "test uuts" like the attached pic, the problem solved.

But why?

Anyone know the function and influence of the step?

[Norbert_B]

Ok, i cannot reproduce the issue at all. Therefore, it would be good if you can attach the example showing this (seq+image files).

I am thinking about possible sources:

- Windows 7 and user desktop: I have seen strange issues in the past if using Windows 7 and placing sources on the desktop. This could be a reason.

- The sources for the dialogs in the PreUUT callback as well as the message popup step is stored in the "modelsupport2.dll". Is it possible that you meddled in there in the past?

- You seem to alter the default process models supplied by NI directly. This is not suggested. Maybe you have done changes which create the issue. This bullet is obsolete if you made changes to copies of the original process model files. But you might want to go back to the default ones if this applies.

Norbert