How to use a user sequence library

[LuI]

Hi all,

I am building up an increasimng set of sequence modules that might be handy in a kind of toolbox library for later re-use. How is this best be accomplished?

AppNote157 states, that I should '... isolate non-product-specific operations in a callback or the process model...' But how do I accomplish this, how do I test 'em and access 'em from my target sequence?

Having my own process model open and trying to start a new 'tools' sequence results in runtime errors, because this very same sequence is the process model AND taget sequence. Trying to build a simple test.seq that tries to call such a sequence within the actual process model (my individual one) results in runtime errors - sequence not found.

How do you organice your
code?

Any enlightening will be appreciated!

TIA and
Greetings from Germany!

-- Uwe

[LuI]

Hi again,

I'd like to answer my own Q's at least in parts:
1. One may add tools to the process model file. Always use your individual process model file to do so.
2. Do not test it from within the process model file! Test it from a client sequence as you would with the target sequence file when running your sequences.
3. One has to add the process model file path in quotation marks and with doubled backslashes (as typical in many programming languages, where a single backslash acts as a break to enter binary data).
One also has to add the tool sequence name (the one to be called within the process model) in quotation marks.

Somehow anoing, isn't it? Instead of an easy way to access library sequences one has to do lots of typing and/or copying&pasting :-(((
I'll try t
o acces the process model file path programmatically and put this one into a station global to ease the access to it.
Probably these tools sequences can also be shifted to an extra sequence as some of NIs own sequences do. For instance the process model sequences call diverse sequences from 'Modelsupport.seq' and 'reportgen_XML.seq'.

So there is a way to have a user sequence library, but it seems it is either not intended to organize one's code this way or NI uses better techniques that I have not yet found.

TIA and
Greetings from Germany!


-- Uwe

[Shannon R]

Uwe,

If you are looking for a way to organize your code, TestStand does have Workspace files. You can add sequences, projects, and code modules to a TestStand workspace for easy reference to the files. You can also associate a process model with a certain sequence file by going to Edit>>Sequence File Properties. On the Model tab you can specify to always use a certain file.

If this doesn't help you, post again with a clarified question.

Thanks!
Shannon R.
Application Engineer
National Instruments