How do I save a type for a previous version of TestStand (4.0 --> 3.5)?

[RayFarmer]

Hi,

Here is an example (Previous Version.zip) that highlight the pitfalls of creating a Step Type as detailed in the knowledgebase. Just follow the Readme.doc contained in the zip file. This example assumes you haven't used the compatibity file for TS3.5 found in the second example.

The second example (Type Conflict.zip) highlights the difference it makes using the Compatibilty file. Again just follow the Readme.doc file.

I hope these examples can be used to enhance the NI TestStand Advanced Series: NI TestStand Type Management Best Practices found at http://zone.ni.com/devzone/cda/tut/p/id/7022.

Regards

Ray Farmer

Message Edited by Ray Farmer on 08-10-2008 06:21 PM

[Manooch_H]

Hi Ray,

You are right that the previously posted sequence file overwrites the current type file. I've updated the attached TS 4.0 sequence file correcting this behavior and providing a bit more modularity. I don't know about the error you are receiving:

"An error occurred calling 'Writefile' in PropertyObjectFile' of NI TestStand API 4.1. The compatibility type palette files for selected version could not be found"

I've tested this sequence out in TestStand 4.0 as well as TestStand 4.1 and did not receive any errors. The new sequence prompts the user for the previous version they are saving for and creates a new type file with that input appended to the end of the file name. The created type files will still be in the same directory as the current file types so they can either be copied to the proper directory for the selected previous version or they can be navigated to when adding types to the previous version.

I appreciate you following up on my previous post and bringing this to my attention. Let me know if there is a discrepency in the updated sequence file.

[RayFarmer]

Hi Manooch,

Thanks for the update.

(Maybe the error was because  I was using a beta version of 4.1!)

I tried your new sequencefile, much better, but it does need a little tweak. I looked at the resultant type file and although it had _35 appended to the file name it was infact a version 3.1.

I spotted the problem, the WriteFile has the enum of WriteFileFormat_TestStand31. I couldn't see anywhere in the sequence where this setting was changed. I changed the API call to use a Locals and set this after the MessagePopup so that the value was equal to 7 for version 3.5.

This produced the correct version of type file.

Regards

Ray

[Ajay_MV]

There is another shortcut way to do this.

• Add your custom steps to a sequence file in higher TS version.
• Save the sequence file As in lower TS version
• Open the sequence file in lower TS version
• Copy the types from the Sequences Files under Types to a new Type palette .INI file.
• Save the Type palette INI files

Thanks,

Ajay