new step type - type conflict

[KHB]

Hi

I have a new step type in Type Palette - MyTypes.ini and it works fine , but when I make a step and save the sequence I get error message "Type Conflict In File".

Now I use step types in Sequence File Types in seq file but then I have to copy the step to all sequences.

How can I use global step types and not get warrning every time I open sequences which contains the step?

thanks for any help

/Kambiz

[RayFarmer]

Hi,

You started off using MyTypes.ini  but you seem to have a ini file called Test.ini

Does that mean you still have the step type in MyTest.ini as well.

If you have the same Step Type being loaded from two places then I am guessing that is where your conflict is.

Delete the MyTypes.ini file from then cfg folder then start up TestStand.

Regards

Ray Farmer

[KHB]

Hi

Sorry, it should be "Test.ini".

"MyTypes.ini" is empty and I don't use it. I only have the step in "Test.ini" .

I got

< Type 'TestStep' in TestSeq.seq (C:\TestStand_Sequences\TestSeq.seq) is different from the currently loaded type

< 'TestStep'.

< Currently Loaded Type
< Version 1.0.0.20
< Last modified: 2008-04-22 13:16:50 (Same in Both Types)
< Category: StepTypes
< Location(s): Test.ini

< Type in File
< Version 1.0.0.20
< Last modified: 2008-04-22 13:16:50 (Same in Both Types)
< Category: StepTypes
< Location: TestSeq.seq

< Summary of Differences:

< TestStep.Result.ResultList (Value or Flag Difference)
< TestStep.SignalList (Value or Flag Difference)

But I have same Value and Flag!? both are empty.

Message Edited by KHB on 04-22-2008 07:21 AM

[RayFarmer]

Hi,

What you have is a local copy of the Step Type in your SequenceFile.

You need to delete any steps that are using that local copy, then delete the step type from the Sequence File.

Regards

Ray Farmer

[rajku]

Can you please explain the solution little more clear. I am also having the same problem

Thanks

Rajkumar B

[Josh_W]

This document gives a pretty good explanation of type versioning and how to resolve them:

TestStand Type Versioning and Conflicts

[rajku]

I see the type conflict only when I run from the Operator interface. Why is that ? I am very much sure that the Types are of same version

With Regards

Rajkumar B