TestStand using a sequence model that is not the model chosen in the station global configuration

[DLMC]

The particulars:

Windows 11 Enterprise

TS 2021

LV 2022

I am migrating NI2013 test stand to NI2022.  This was working a few months ago, but changed to Windows 11 and something broke.

Regardless...

While editing the test I found that the Configure->Station Options->model is set to SequentialModel.seq in the NI teststand components/models folder, but looking at the bottom (and from watching how it runs) I see that it is actually using the sequence model in my teststand working folder.  This is a good thing, that is the one I want it to use, but how did TestStand get told to use the local model and not the one configured in the sequence editor?  I want to merge this test sequence with others to use common VIs and test model, so I am keen to know how this is done.  Everything I read says to set it up in the sequence editor Configure->Station Options->model, but this isn't using what is set there.  I am perplexed.

What is the secret to getting a test sequence to use the local model?

be well,

DLC

[Oli_Wachno]

Hi,

this goes back to the basics of how TestStand identifies and locates files.

1.) Sequence file names loaded into memory are unique: you cannot load two SequentialModel.seq into memory

2.) TestStand locates files using the search directories in the order specified

So if TestStand is looking for SequentialModel.seq is goes through it's SearchDirectoryList and loads the first file by that name it finds.

In your case, I bet the Working Folder is searched through before the actual %TestStand% directory

Guess you are NOT using TestStand Environments, are you?

BR

Oli

[DLMC]

Thanks for the reply Oli.

this goes back to the basics of how TestStand identifies and locates files.

1.) Sequence file names loaded into memory are unique: you cannot load two SequentialModel.seq into memory

I did know that, but that does not apply here, for reasons I didn't mention.  The Sequential Model sequence that is being used is not called SequentialModel.seq.  It has a different name denoting the product line. e.g. ProductLine_SequentialModel.seq.

2.) TestStand locates files using the search directories in the order specified

So if TestStand is looking for SequentialModel.seq is goes through it's SearchDirectoryList and loads the first file by that name it finds.

In your case, I bet the Working Folder is searched through before the actual %TestStand% directory

It is indeed the first directory searched.  But, see above.

Guess you are NOT using TestStand Environments, are you?

Until now I didn't know that existed.  That is very handy for a development system, thanks for the pointer.

My question still remains - How did the original authors of this code get TestStand to use the local folder's sequence model instead of the sequence model the TestStand sequence editor says it should be using?  Does the editor have a default path that is overridden in another part of a sequence's setup?

be well,

DLC

[DLMC]

this goes back to the basics of how TestStand identifies and locates files.

1.) Sequence file names loaded into memory are unique: you cannot load two SequentialModel.seq into memory

I did know that, but that does not apply here, for reasons I didn't mention.  The Sequential Model sequence that is being used is not called SequentialModel.seq.  It has a different name denoting the product line. e.g. ProductLine_SequentialModel.seq.

2.) TestStand locates files using the search directories in the order specified

So if TestStand is looking for SequentialModel.seq is goes through it's SearchDirectoryList and loads the first file by that name it finds.

In your case, I bet the Working Folder is searched through before the actual %TestStand% directory

It is indeed the first directory searched.  But, see above.

Guess you are NOT using TestStand Environments, are you?

Until now I didn't know that existed.  That is very handy for a development system, thanks for the pointer.

My question still remains - How did the original authors of this code get TestStand to use the local folder's sequence model instead of the sequence model the TestStand sequence editor says it should be using?  Does the editor have a default path that is overridden in another part of a sequence's setup?

be well,

[DLMC]

DLC

[ShockHouse · Accepted solution]

It may be that it's changed at the sequence file level which overrides the global level.

When your sequence file is open go to Edit -> Sequence File Properties -> Advanced. Here you can modify the Model the Sequence File uses. By default it uses the Station Model. But you can change it to any other model. So when that specific sequence file is opened, it will use the model specified here without changing everything else on the machine. 

[Oli_Wachno]

Good Point!

You should be able to probe this also by unchecking the Allow Other Models  Option

SeqEdit should throw a Runtime Error.