Load specific type palettes configuration for each sequence files

[alfi]

Hello,

we want to load a specific type palette configuration with a sequence file.

We have several versions of step dlls and we don't want to use steps from different versions in one sequence. The problem is that we don't want to let the users (who creates the sequence) the choice to select the steps from different dll versions. So we want to load the type palettes when we load the sequence. Our solution: We tried to save the configuration of teststand in the directory of the each sequence, then we changed the configuration path entry in the windows registry each time we load a sequence file.

We use teststand 4.0.

Do someone have an idea how to solve these problem on a better way?

Many thanks!

Alex

[nikolair]

Hi,

it's possible to load specific types with a sequence file when inserting the types into the sequence directly. In that way you can ensure that the types are specific to one sequence file but no longer global available.

To do this one has to create the user defined types in the "Sequence File Types" section.

regards,

Nikolai 

[j_dodek]

Hi Alex,

The answer is yes, if you use only one sequnence file (or more of the same StepType) !
in your a Teststand engine at while editing on running our uut.
If this is not possible i think or better i am sure you will have a problem with Type conflicts.

A few months ago i had the same problems with the types and the dll.
I solved it in this way:
The StepType infomation is only present in the SequenceFile.
So you only have to get rid of the StepType information on our Station. Just delete the Ini-File ouf your Type in
the TestStand folder and save it for backup on place where TestStand never! never! reach it.

The big advantage of this is you don´t have to care about your Types on your Station. And believe me
if your your SequenceFile is running on many Stations this is the best solution.

But how to get the Type on your SequenceFile? I do it in this way just only on my development maschine:
Take the ini-File from the Backup, place it into the right TestStand folder and start TestStand. Create a new Sequence File and paste your Step in the SequenceFile, save it. Close TestStand an get rid of of the Type-ini. Now you can use your Step from this SequnceFile and you copy paste it to every SequenceFile you want.
(but if the there already exits a type of an other version --> Conflict --> how to update ?? --> other story!!)

I hope this helps

greetings from the lake of constance, Germany

Juergen

[alfi]

Hi,

thanks for help! The information you gave me is very interesting.

I think the best solution four our problem is to create a template sequence file with all the steps in it. So the versions of the steps will be saved in the sequence file, and the user who want to edit the sequence can only use these steps. With an newer release of the steps we create a new template sequence. On the user machine we will only copy the step dlls an no type paletts (ini), so the user can only use the steps saved in his sequence. This will prevent version conflicts between several step dll and type palett version.

Thanks a lot for help!

Best regards

Alex

[j_dodek]

Hi Alex,

An other hint if you are using network directorys. Load your dll over a network directory.
This will reduce reduce your maintainance effort in the productions line because you can save the job coping your dll on local drive. Or if you have an update just replace the dll on the network.

Important is to use a relative path. With it you can select the TS - Search directories from where it should be loaded first. (extremly useful if there are several Dll versions release, debug, or logger so you have not to switch in the step at all)

Greetings

Juergen