Type Conflict in File - TestStand 3.0

MSEcast · ‎09-03-2009

Hi,

I am having a "Type Conflict in file" error in TestStand 3.0. We have a system in production that used to have 8 instruments; the GPIB addresses of these instruments are station globals defined in TestStand. Ever since this system was created, no new instrument was added and all the sequence files created had the same station globals; however recently I added a new LCR and therefore I added a new station global.

During Development I did not see the problem since I had to manually change the station globals in order for my software to work; however now that I released it, I changed the Station Globals for the system and therefore I am affecting all the old sequence files.

This is happening with TestStand 3.0 which is a very old version. When running the old sequence files manually a dialog box pops up asking if I want to use the currently loaded type or to use the type from the sequence. By selecting either-or the problem goes away and the sequence is now able to run normally. I am wondering if there is a way to do this programmatically or if there is any configuration that I can set so that It chooses one of these two options by default.

I read that TestStand 4.1 has an option inside the Station Options->Preferences that I believe fixes this kind of problem. Please let me know if there is something I can do in TestStand 3.0

Thanks in advance

bruno_p · ‎09-04-2009

Hi,

I think that you can avoid this conflict in TestStand 3 :

- Define a newer version number of your type (if the version was 1.0.0.0, set the new version to 1.1.0.0) : Type Properties --> Version.

- In the version tab, set the option "Use the definition that has the highest version number".

Now the type in your StationGlobals should be newer than the type in the sequence files.

When you load a sequence file, TestStand will update automatically the type in your sequence file (if you open the file in the sequence editor, TestStand indicates that the file should be saved, because it was modified to update the type).

Hope this will work for you.

Bruno