From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

NI_LV_RunVIAsynchronously step starts after next step

I'm calling a VI with the NI_LV_RunVIAsynchronously step 

This vi starts AFTER I exectute the next step. Is this normal behaviour? or how can i solve this?

 

my current workaround is having a label step after the NI_LV_RunVIAsynchronously step

0 Kudos
Message 1 of 5
(112 Views)

Just tried to reproduce the behaviour you are describing, yet I didn't succeed.

 

Can you please elaborate on the setting you are using?

0 Kudos
Message 2 of 5
(60 Views)

It seemed to occur when I had a breakpoint on the NI_LV_RunVIAsynchronously step.

 

After removing the breakpoint and restarting computer it seems to work okay now...

0 Kudos
Message 3 of 5
(34 Views)

Breakpoint on step means: don't execute the step until I tell you to

 

So that makes sense

0 Kudos
Message 4 of 5
(24 Views)

The behaviour was:

 

Breakpoint on step

*Press F10 (next step) --> nothing happens but I expect that the step should execute

*Press F10 Again --? Asynch step + step after asynch step executes at the same time

0 Kudos
Message 5 of 5
(21 Views)