upgrade to Test Stand 2010 from 2.0.1 and 3.1

[Srm27]

Hi,

We have purchased an upgrade to Test Stand to upgrade from 2.0.1 and 3.1 to T.S. 2010.

The majority of the code, at present, is run from 2.0.1, across multiple PC's.

Can anyone direct me to a Help to assist in the move?

Has anyone done this before and what were the issues/pitfalls found.

Thanks for you help

Simon

[tom.drake]

You might want to review the TestStand 2010 Release Notes, located in the <TestStand>\Doc\Manuals directory or online below, as a starting point

http://digital.ni.com/manuals.nsf/websearch/551E162690F5CF59862577AC000B547A

This document includes a "Migrating to TestStand 2010" section that includes some helpful tips for migrating your custom components and other files.

You could also review the "What's New in TestStand" topics in the NI TestStand Help to familiarize yourself with all of the new features and compatibility changes in TestStand since 2.0.1 and 3.1.

http://zone.ni.com/reference/en-XX/help/370052J-01/TOC2.htm

[Srm27]

Hi,

Tom thanks for that I will try work my way through it.

I see you can use TestStand Version Selector, as stated in the Released Notes, but would it be Best practice to remove 2.0.1 and 3.1 first and then install the new version of Test Stand.

Baring in mind I will need to make a distribution kit, from my installed version, to update all the other PC's just running on base deployment engines.

As always thanks for the advice

Simon

[Srm27]

Hi,

Uninstalling was not a good idea as a lot of the sequences were stripped out that are required, so it was better to use the TestStand Version Selector

In the section, TestStand 2010 Behavior Changes, of the NI TestStand Release Notes it states the following:

                 TestStand 2010 and 2010 SP1 are the last versions to support writing out files using the TestStand 2.0   

                 and 2.0.1 file formats.

What dose this mean? What should we be looking out for?

We are upgrading from 2.01 and trying to see where the problems are.

Thanks

Simon

[warren_scott]

It will be a lot easier if you have one computer with your current version of TestStand (2.x) and associated code (LabVIEW / CVI / etc) and get a second computer to install the latest version of TestStand / code modules on it.  This way you can simultaneously have both versions open on 2 different computers when you are trying to figure out the best way to handle the upgrade.

Good luck.  There's a LOT of changes in TestStand between 2.x and 2010.