NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

persistbreakpoints does not work as expected

Hi,

I am launching TestStand through a LabVIEW VI using a customized Full-Featured UI.  I am trying to set the "PersistentBreakPoints" property on the Engine, but it seems to work only sporadically.

Sometimes, the sequence file view shows the breakpoints, sometimes it doesn't.  

However, when I start the execution, the breakpoints are *always* there.

Does anyone have any ideas as to what I'm doing wrong?

Cheers.

0 Kudos
Message 1 of 6
(3,738 Views)

Hi,

 

I have a few questions for you: 

What behavior do you experience when you open and run your sequence from the TestStand sequence editor?  Do you see the sporadic appearance of the breakpoints only in the LabVIEW VI or also in the TestStand sequence editor?

Is this behavior with multiple sequence files or just one?  

When you say the breakpoints are always there, do you mean that you see them in the step list AND execution breaks at each of them? 

 

For information on the PersistBreakpoints property, I recommend looking at the TestStand help for the PersistBreakpoints property.

Also, I recommend the knowledge base article Changing the Default Behavior of TestStand Breakpoints

 

 

Mark E.

Applications Engineer

National Instruments


Mark E.
National Instruments

0 Kudos
Message 2 of 6
(3,718 Views)

Hi,

 

Opening and running the sequence from the test sequencer is fine.  The breakpoints appear when I open the sequence.

The sporadic appearance of breakpoints only occurs in the LabVIEW VI.

 

I am only opening one sequence file, but I think it would happen with any sequence file.  I will verify this.

 

The breakpoints are always visible and functional in the execution view, but only sometimes visible in the sequence view.

 

Thanks for any help.

 

0 Kudos
Message 3 of 6
(3,712 Views)

I have tried to reproduce the behavior, but am unable to do so.  Do I understand correctly that it is the Stop sign icons for the breakpoints that are not showing up? Can you determine any pattern behind when the breakpoints will or will not show up in the Full-Featured UI?   Are there any changes that you are making?

 

In case there's any question, this is the correct way to set the PersistBreakpoints property:

RunState.Engine.PersistBreakpoints = True

 

The help information for the PersistBreakpoints property is available in the TestStand Help file that installed with your software, as well as on the online TestStand help: PersistBreakpoints Property  

 

Mark E.

Applications Engineer

National Instruments


Mark E.
National Instruments

0 Kudos
Message 4 of 6
(3,691 Views)

Yes, it is the stop sign icons that are sporadically not showing up.  At the moment, I cannot determine a pattern of when they don't show up.

 

In my LabVIEW code, I am doing ApplicationManager->GetEngine->PersistBreakpoints=true.

 

Has there ever been a case of this situation (breakpoints functional and visible in execution view, but not visible in sequence view)?

 

Cheers.

 

 

0 Kudos
Message 5 of 6
(3,687 Views)

Just to make sure that I understand what you're saying, the breakpoints function but do not always show up in the LabVIEW TestStand UI?  That is extremely weird behavior that we have not heard of before.   Which versions of LabVIEW and TestStand are you using?  Do you have other versions installed on your computer?  

 

If possible, please create a simple sequence file and UI that reproduces this problem, zip them together and attach them to a reply to this post.  I will then be able to look into them and troubleshoot.  Thank you!

 

Mark E.

Applications Engineer

National Instruments

 


Mark E.
National Instruments

0 Kudos
Message 6 of 6
(3,659 Views)