04-25-2006 05:47 PM
04-26-2006 01:04 AM
Robert,
Can you be a bit more specific regarding any problems you are having with the task you undertaking?
Regards
Ray Farmer
04-26-2006 10:28 AM
My operators are using the "Debug" version of TestStand, so they can add steps to pre-existing sequences. They asked me to write a custom step that opens a LabVIEW vi when they select/edit the custom "FOR EACH" step, so their entries will automatically insert/configure the "FOR EACH" step for them. These changes/additions will be made when the sequence is not running.
Respectfully,
Robert
04-26-2006 03:18 PM
04-26-2006 03:27 PM
Jonathan,
The vi you suggested does not support flow control (FOR, FOR EACH . . .). NewStep==>stepTypeName==>StepType_???
Do you have any suggestions for flow control commands?
Respectfully,
Robert
04-26-2006 04:14 PM
Hi Robert,
That example VI does support flow control, it just doesn't show it. The NewStep method in the example VI only shows pre-defined constants being converted to a string to be evaluated. Some of the step types do not have pre-defined constants. Thus you need to refer to the Type Palette to see what the string parameter "stepTypeName" should be. For example, as shown in the attached image, you would use the string NI_Flow_ForEach to insert that ForEach flow control step. For the "adapterKeyNameVal" parameter, you would just send in an empty string.
You can see the string names associated for each step type by opening the Type Palette and seleting the "NI_FlowControl.ini" file from the Palette drop down menu.
Hope this helps!
Best Regards
04-27-2006 11:36 AM
Johnathon,
Where would I find a list of these NI flow step types?
Respectfully,
Robert
04-27-2006 11:40 AM
04-27-2006 12:17 PM
Thank you,
Robert