Will I find any compatibility issues with 3.1 v. 3.5 v. 4.0

[dusty_g]

I will be working with some special test equipment and on the test console computer it will be running TestStand 3.1.  Some of the poeple that will be developing testscripts from my group have version 3.5 and some have version 4.0.  We will be developing the code on our own machines and then integrating the code to the console. Will we run into any problems with the different versions?

Eventually the console will be upgraded to 4.1.  Will we run into problems then when the console is upgraded with all the work we would have done in version 4.0, 3.5 and 3.1?

We have the same problems with CVI the console will be using version 7.1.1, we have 8.6 and 8.2 at our desks.  Will we see any problems there?

[RayFarmer]

Hi,

I the obvious problem will be the guys generating sequence files at the latest versions and using the functionality added at those later versions. So you have to make sure you have maintained backwards compatibity by not using those functions. You will find this out when you Save As to the older version and get the report telling you that some functions of the sequence file have not be saved out. Therefore, there will be a good trace your sequence files will not run correctly.

Regards

Ray Farmer

[Snowman 6008]

Dusty,

When you upgrade all of your sequence files should still run as they did in 3.1, but the only way to know for sure is to try it out. If you are planning on upgrading it may be easier to go ahead and try that sooner than later, If you want to develop on a 4.1 system and save down to different versions, as Ray pointed out you will not be able to use features that aren't available in 3.1, so all of your systems' features will be restricted. If you wanted to know what changed between 3.1 and now, here is a quick run-down:

What Is New In TestStand 3.1

What Is New In TestStand 3.5

What Is New In TestStand 4.0

What Is New In TestStand 4.1

If you upgraded your system now, you wouldn't have to worry about using any incompatable features. Since you plan on upgrading in the future, is there any reason you don't want to do it right now? Also, if you plan on keeping this system around, if you stay on our SSP plan, you get every update to TestStand as it comes out in addition to full access to phone support, that way you can upgrade from version to version, and make upgrading easier, rather than having to jump multiple versions at a time. 

[dusty_g]

Oh if only upgrading was that easy.  In my work environment something like a simple SW upgrade just doesn't happen overnight.  It's a world of processes.  Mainly becasue this special test equipment is never networked for virus protection so we would never see the updates, and there are numerous other systems out there running 3.1 that the company wants to stay consistent with.  Trust me if i had my way everything would be updated all the time but it just doesn't work that way around here.

Will I face any other compatability issues if i develop something in TS 3.1 and work with NI switch executive and Labwindows CVI 7.1.1?  Will the upgrade cause problems with those environments?

[Snowman 6008]

Dusty,

As long as you have the same version of Switch Executive and CVI on your systems, then TestStand 3.1 will run those code modules the same on your systems. I definetly understand upgrade pushback from other departments. Just as long as they keep a backup machine with windows xp, make sure to keep TestStand 3.1 software backed up and any code and drivers, making sure to document all of the code for any future developers. Nothing is worse to debug than code no one has touched in 10 years. 

So you should be fine, if you run into any issues along the way let us know.

[dusty_g]

Wait, now i'm kind of confused you said "as long as I have the same version of Switch exe and CVI i should be fine" I'm saying what if I don't have the same versions?  In this case will I not be fine?

DG

[Snowman 6008]

Dusty,

CVI is very good at being compatable across many versions (its ANSI C code, and they don't really change that standard), as long as you don't use any newly introduced functions, or require a library from the full version, when you have only base installed on another computer. The UIR of the CVI code on the other hand may not be compatible across drastically different versionsof CVI. For more upgrade notes check the CVI Readme located at Start»Programs»
National Instruments» <Your LabWindows CVI > » LabWindows CVI Readme .