Can I change "Skip Mode" to "Run Mode" on all sequences, recursively?

[bmihura]

I want to make sure that none of my sequences steps are in Skip Mode, but I have many layers of sequences now.

Is there some way to un-skip everything without tediously opening every sub-sequence?

[James_Grey]

Try do a Find In Files on a value of Skip.  That will make it easier to find and change all the occurrences.

[SercoSteve]

You could write a tool that searches a TS sequence and changes the StepType RunMode property programatically, using the TS API, to "Normal", "Skip", "Fail" or "Pass" depending on your requirements.

Regards

Steve 

Message Edited by SercoSteve on 03-21-2006 02:02 AM

[bmihura]

Thanks; that would work as would the previous suggestion of searching for such things.

But I'm starting to wonder why such features are not built into this $3,000 piece of "software". Oh, and $3,000 won't buy you any customer support.

TestStand's motto: how difficult and slow can you possibly make a programming language?

Relatively speaking, LabVIEW and LabWindows/CVI are elegant and easy to use.

[SercoSteve]

Of course its going to be difficult and slow when you don't understand what your doing.

[Bob_Y.]

I have a lot of the same problems.  Are these things covered in the TestStand classes offered by NI?  It is part of the curriculum to teach people how to change all of the skips to runs or build other tools to help automate things that seem to be extremely tedious in TestStand?

I have to admit that I am a LabVIEW user and I expect TestStand to have all of the helpful tools that LabVIEW has.  I know that is unrealistic as they are different pieces of software used for different things; domain knowledge of one does not always transfer to the other.  On the other hand, I find a definite lack of this sort of useful tool in TestStand.  Maybe they are there and I don't know the right keywords to find them through help, etc. but others are asking similar questions and maybe its not me.

So I would say to bmihura, its not just you, either!

Thanks,
Bob Young

[Jesse_O]

Hello bmihura,

I have attached a zip file below that sets the run mode for every step within a single sequence file.  If you would like to add this utility to the tools menu of TestStand, simply select Tools >> Customize >> Add.  In the window that appears select Sequence for the item type, then select the ChangeRunMode.seq sequence file and specify the MainSequence in the sequence input.  Next click ok twice and you will have this utility added to your Tools menu.  This sequence file was saved in TestStand 3.1 and TestStand 3.5. 

Bob, there is no information in the TestStand class that directly shows you how to create an application that changes the run mode.  The information taught in the class should provide the tools necessary to write code similar to what I have posted. 

The discussion forums are a great way to find solutions to the problems encountered in TestStand.  As you can see, National Instruments employees are constantly providing help to customers on the forums.

Regards,

Jesse O
Applications Engineering
National Instruments

[RayFarmer]

Hi,

Changing the state of a property is not a difficult task, such as changing the run mode, but I know that good examples are always good starting points, especially when you are just starting with a package or even coming back after a long break from using the package.

The NI website has a number of examples that would help to show how to achive certain tasks, such as https://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3EE5556A4E034080020E74861&p... (Link is no longer valid.- KMartinez Community Admin) which steps through a sequence obtaining the names of steps, Once you have identified the parts that are doing the actual interface to the step properties, you on the road to achiving a tool to change your skips to normal.

Not sure thats it should be a default tool or how useful it would be to majority of users.

Taking labview, you dont have a default tool that makes a selection of controls change from visible to hidden. You would have to create your own.

Regards

Ray Farmer

[Bob_Y.]

Not sure thats it should be a default tool or how useful it would be to majority of users.

Taking labview, you dont have a default tool that makes a selection of controls change from visible to hidden. You would have to create your own.

---

Very true.

I am also not sure how often I would use any of the tools that are not already there.  A large number of the ones that are I won't use and some I would not think to look at if I did need them as I don't have the experience.  I know that I am only using about 15% of the possible power of TestStand and that I am learning more all the time. 

As for a LabVIEW tool to do some things in LabVIEW, I have written several of them as well and use them as necessary (including one to make every control visible and one to make all selected controls hidden).

It is just that I have lots of experience with LabVIEW and only have learned part of TestStand.  (I also tend to be overly defensive!  )

Thanks for everyone's help in a thread that was not even mine originally,
Bob Young