Match StepTypes for 32-bit and 64-bit

[efelixreyes]

I have been creating StepTypes from version 3.1. Now, I need support to understand how I can share the same StepTypes for 32-bit and 64-bit without causing TestStand to display a Type Conflict. I already created some StepTypes that can invoke the proper methods (32-bit or 64-bit) for "Edit" or "Post-Step" in both environments. However, I see a type conflict because the TimeStamp on the type is not the same. How can I prevent TestStand from raising a Type Conflict (I want to produce the same functionality as the NI StepTypes (i.e. flow control)?

[dug9000]

Ideally, you should be using the same step type for both bitnesses (i.e. the same type palette file for both), thus there should be no conflicts because they are the same step type. The only difference is that 64-bit TestStand should find the 64-bit version of code module, while 32-bit TestStand should find the 32-bit version of the code module. That will generally happen automatically if you put the 64-bit code module in the 64-bit public directory and the 32-bit code module in the 32-bit public directory. If you look at the existing step types that ship with TestStand by default you can see how it is done.

Hope this helps,

-Doug

[efelixreyes]

Thanks for your infomation. That is what I was wondering. As long as I keep the same file name for both binaries and use the TestStand Public folder structure everything works perfect. In order for this approach to work the module shall be defined using a relative path.

[dug9000]

That's not exactly what I meant. You can have separate public directories for your 32-bit and 64-bit versions of TestStand and that is the recommended and default way of doing things. What you need to do is make sure that both copies of your type palette file in the two locations have exactly the same step types (i.e. one is really a copy of the other). You need to keep them in sync. If you edit the step type you need to re-copy the file to the other bitness.

-Doug