Break Method causing Abort dialog

[EdDickens]

I'm having an odd problem with the 'Execution.Break' method when runnning a sequence in our custom LabVIEW based GUI.

When we run from within TestStand, the Break method correctly pauses the sequence. When we run from our custom GUI, it seems to trigger the Abort method as the standard Abort dialog pops up asking how we want to handle the Abort and the sequence does not pause.

This seems to have just started happening in the last week or so. We're seeing the problem on three different machines.

Using LabVIEW and TestStand 2014 SP1 on Windows 7 Enterprise.

[ZannahBanana]

Hi EdDickens,

Have you updated anything on your computers recently? Since it was working fine only a week ago and the problem exists now on three different machines, I am wondering if updates could have caused this behavior.

[EdDickens]

No update I can think of. Definately nothing in TestStand or LabVIEW.

We see this on my personal development laptop as well as at least 2 different development machines of the customer.

Just so I'm sure, the Break method is supposed to Pause, not Abort correct?

[ZannahBanana]

Hi EdDickens,

Well that will depend how you're using the break method. Can you go into more detail about where you're trying to put the breakpoint and how you're going about doing that?

[EdDickens]

It's not a Breakpoint, it's the 'Execution.Break' method.

This is in an asynchronous VI that watches certain values and pauses the sequence to alert the operator and give them a chance to get the value back into it's limits.

This works fine running in the full development environment of TestStand, but when run from our custom GUI, it seems to trigger the Abort method instead. 

[ZannahBanana]

It sounds like this may have something to do with your custom GUI and not the method itself if it is functioning properly in the full development environment of TestStand. Are you able to give more details about your custom GUI?

[EdDickens]

The VI that calls the Break method isn't actually part of the GUI. It's launched as an asynchronous VI from TestStand and just runs in the background.

The GUI is pretty simple. It just calls a top level sequence that then calls sub sequences based on various options. The GUI just has an operator prompt area and a listing of the sequences and steps that are to be run with Pause, Abort and Resume buttons. The Pause button on the GUI uses the 'DoClick' method to an ActiveX button linked to the "CommandKind_BreakResume" command of the "ConnectCommand" method of the ExecutionViewManager.

I'm going to try to create a small example that I could post.

[EdDickens]

Turns out it wasn't the Break method that was triggering the Abort dialog.

The GUI watches the number of executions running and automatically shuts down when there are zero. The problem was the property 'NumRunning' doesn't report on Paused executions. So it would return zero and try to run the 'ShutDown' method, which was triggering the Abort dialog because there was still the active, but Paused sequence.

Changed the property to 'NumIncomplete' and all seems to be good.