NI TestStand
Is there a possibility to change step-parameters during debug execution ?
Hi bestware,
I am assuming you want to provide some sort of debug from your Operator Interface.
I've been looking at using the SequenceFilePreStep and SequenceFilePostStep to provide some sort of debug.
Using the SequenceFilePreStep callback you could place some code in here to evaluate the step running (about to be executed) and display an appropiate Dialog box to allow the user to change any of the available parameter.
My simple example tests if the step is a NumericLimitTest step type and if so, allows the user to change the Upper Limits only (said it was simple).
Now to Looking at the Locals and Parameters in the Sequence of the Step about to be performed. You will have to look at RunState.Caller.Locals and RunState.Caller.Parameters. Get a list
of the variables, find out the type and provide the suitable interface to be able to modify the contents.
Look at here http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=137&HOID=506500000005000000FF750000&HTHREAD=000030207&UCATEGORY_0=_8_&UCATEGORY_S=0 and see what Dan has been doing in this area.
Hope this is a start.
Regards
Ray Farmer
I am assuming you want to provide some sort of debug from your Operator Interface.
I've been looking at using the SequenceFilePreStep and SequenceFilePostStep to provide some sort of debug.
Using the SequenceFilePreStep callback you could place some code in here to evaluate the step running (about to be executed) and display an appropiate Dialog box to allow the user to change any of the available parameter.
My simple example tests if the step is a NumericLimitTest step type and if so, allows the user to change the Upper Limits only (said it was simple).
Now to Looking at the Locals and Parameters in the Sequence of the Step about to be performed. You will have to look at RunState.Caller.Locals and RunState.Caller.Parameters. Get a list
of the variables, find out the type and provide the suitable interface to be able to modify the contents.
Look at here http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=137&HOID=506500000005000000FF750000&HTHREAD=000030207&UCATEGORY_0=_8_&UCATEGORY_S=0 and see what Dan has been doing in this area.
Hope this is a start.
Regards
Ray Farmer
Hi Christian,
You do know that when your execution stops at a breakpoint, you can browse the context via the Context Tab. Double clicking on a variable brings up a dialog windows from which you can change the actual value and hence you can change a steps properties before its executed. Go to Chapter 6 of the User Manual 'Sequence Execution' ( chapter 6-7 Context Tab explains more).
You can also place variables in the watch window so you can easy see actions happening during single stepping.
You also need to be aware that any changes made to property values doing execution are lost when the execution completes.
Regards
Ray Farmer
You do know that when your execution stops at a breakpoint, you can browse the context via the Context Tab. Double clicking on a variable brings up a dialog windows from which you can change the actual value and hence you can change a steps properties before its executed. Go to Chapter 6 of the User Manual 'Sequence Execution' ( chapter 6-7 Context Tab explains more).
You can also place variables in the watch window so you can easy see actions happening during single stepping.
You also need to be aware that any changes made to property values doing execution are lost when the execution completes.
Regards
Ray Farmer
