type conflict error

[walter.shao]

see the attached !

[Matt Pickard]

Walter,

Usually when you see that error, if you open your process model and resave it, it should go away. Also you can avoid type conflicts by always choosing to increment the version when saving types. You can set this in Configure >> Station Options >> Preferences. Type conflicts occur when two types with the same name and same version have different time stamps. If two types of the same name have different version numbers, TestStand will just use the latest version and won't throw that error.

Matt P.
NI

[Scott_Richardson]

Walter -
Type conflict errors occur when a loaded type is different than a type in a file and the TestStand engine does not know how to resolve the difference. In general the only way to automatically resolve the difference is if one of the types has a higher version number AND both types are not marked as "modified". If the versions are identical or one of the types is marked as modified, TestStand will warn you.

When you edit a type, the type is marked as modified. The modified bit is typically turned off when you increment the type's version.

The odd thing about the error message is that the type that TestStand is complaining about is TEInf. TEInf is the type used to define the TS subproperty under steps. If you have modified this built in type,
I would highly recommend that you resolve this conflict by selecting the original one that TestStand installed and not use the one that appears to be altered/modified.

If you are using TestStand 3.0, this version incorrectly allows you edit NI types, so this may have allowed you to get into this situation.

Scott Richardson (NI)