call executable step type

[HysHysHys]

Hi all,

I want to execute ms-dos batch file script (.bat) and executable file (.exe) using the "call executable" step type of Test Stand. I tryed different arguments and options but I'm not able to run any executable using this step type?!?

How should I use this step type? Or what can I do to solve this simple problem?

[Scott_Richardson]

To HysHysHys -
What version of TestStand are you using? Try configuring a new sequence file with a single step that invokes the executable "notepad.exe" to see if this works. If it does not work, post the sequence to the thread so that I can see it.

Scott Richardson (NI)

[HysHysHys]

Hi Scott,

I'm using TestStand 3.0.

I tryed the notepad example and it didnt work.

Note1: TestStand seems to find the executable because it suggest a file path.
Note2: I don't think TestStand run correctly because it never popup a small window for ms-dos command as it suggest in argument (show normally activated).
Note3: If I add a wait condition (of 10 seconds), TestStand always quits without respecting this condition.

Here is my sequence file:

Vincent

[HysHysHys]

Hi Scott,

I think that there are some TestStand internal conflicts between NI sequence file. I try to load the Deployement tool of TestStand and TestStand ask me to select between the "CallExecutable" step type currently loaded and the version saved with the sequence file "DeploymentUtility.exe".

How can I reset the default options of TestStand regarding the default sequence and step type.

Vincent

[Scott_Richardson]

Vencent -
Unfortuneately TestStand 3.0 incorrectly allows customers to alter TestStand types and it appears that the internal type PostSubStep was renamed to PostSubStep2. This could explain the problem because by renaming this, the type no longer is associated with an internal class that executes code modules associated with step types.

To fix this you could repair the type palette files for TestStand:
1) Goto the control panel to "Add Remove Programs", find "National Instruments Software", select "Change" and then do a repair on "TestStand 3.0". This should restore the type palette files under TestStand\Cfg. After this when you restart TestStand and you open a file with the incorrectly altered type, you will be able to say "Use cu
rrently loaded type" when you get a conflict dialog box.

2) Another option you be to just pull the type palette file from another TestStand 3.0 system and do the same conflict resolution steps.

Scott Richardson (NI)

[HysHysHys]

Hi Scott

Thanks, it's now working correctly.

Vincent