NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Set LabWindows CVI Adapter to older version

Hi,

 

I recently installed CVI 2015. I also have CVI 2012 installed along with TestStand 2012.

Now when I click on the edit code button in the TestStand 2012 module tab it defaults to opening the code project file in CVI 2015. Is there a way to reset that back to CVI 2012. I have projects that need to be built and released using the 2012 version.

 

Thanks

 

Curt

0 Kudos
Message 1 of 14
(4,137 Views)

Hi Curt,

 

TestStand will open the file using the default version of LabWindows™/CVI™ on your computer. On a Windows computer, you can set the default program to be LabWindows™/CVI™ 2012 through the Default Programs section of the Control Pattern (use the "Associate a file type or protocol with a program" option). You can also right-click on a file with the desired extension and use the "Open With..." option to set the default program, as described in KB 4WGETJUB.

 

 

Steven Gloor
Staff Customer Engineer - CTA, CLD
0 Kudos
Message 2 of 14
(4,121 Views)

Hi Steve,

 

Thanks for the reply. Unfortunately it didn't work. I've searched the registry for any link between TS 2012 and CVI 2015 and I can't find anything. Is it possible there's something in a TS config file?

 

It's really annoying to not be able to click on the edit code button in the test stand module tab to pull up my source files.

 

Thanks

 

Curt

 

 

0 Kudos
Message 3 of 14
(4,083 Views)

TestStand will use whichever version of CVI you launched last. Try exiting all versions of CVI on your machine, then launching and exiting the one you want TestStand to use.

 

Hope this helps,

-Doug

0 Kudos
Message 4 of 14
(4,062 Views)

Hi Doug,

 

Thansk for the reply, but that didn't resolve the issue. Another engineer in my group is seeing the same issue after installing CVI 2015 on his system so it's not an isolated issue with my installation.

 

Any NI engineers reading this board have any ideas?

 

Curt

0 Kudos
Message 5 of 14
(4,026 Views)

The registry key that defines what TestStand will launch is the following:

HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{5AB151E3-414A-11D0-A62C-0020AF16F78E}\LocalServer32

The value is something like this:

c:\program files (x86)\national instruments\cvi2015\cvi.exe /Automation

When you launch a different CVI ADE, this entry value should be changing. Can you verify whether the value changes?

 

You might also try to launch CVI elevated as Administrator to see if that changes anything.

Scott Richardson
https://testeract.com
0 Kudos
Message 6 of 14
(4,012 Views)

Hi Scott,

 

I checked and yes the registry key does update when I open projects with differeent versions of CVI.

Unfortunately, that didn't fix the problem.

 

This isn't a show stopper, it's just a pain in the ass when I need to update the  source code linked to sequence file step.

 

Thanks for the help

 

Curt

 

0 Kudos
Message 7 of 14
(3,990 Views)

Curt, for future reference, what OS are you using?

Scott Richardson
https://testeract.com
0 Kudos
Message 8 of 14
(3,982 Views)

Hi Scott,

 

Windows 7 64 bit

 

Curt

0 Kudos
Message 9 of 14
(3,969 Views)

1) are you using 64-bit versions of TestStand or CVI?

2) Did you try running CVI "as administrator" to see if that fixes the problem?

 

Thanks,

-Doug

0 Kudos
Message 10 of 14
(3,960 Views)