12-18-2009 11:07 AM
12-18-2009 12:27 PM
Interesting question. Does you "test station" have the TestStand 4.1 development environment on it or have you just a deployment license on it? Are you using the LabVIEW UI's on it? I think that whatever version of LabVIEW that was used to write the TestStand/LabVIEW User Interfaces would determine the default runtime LabVIEW engine that would be installed. If you are writing code modules in other versions of LabVIEW you would need to deploy the associated LV runtime engine using the TestStand deployment utility under the installer options/Drivers and componants tab.
Hope this helps
12-18-2009 01:00 PM
Good questions. The test station has the development system of Test Stand installed. It also has a UI, but I'm pretty sure it's a version developed using CVI rather than LV. So although I don't believe there's any reason for the TestStand installation to install ANY version of te LV runtime, when I look at the "Add / Remove Programs" application in Windows, I see the 7.1.1 version only (today). I'm pretty sure version 8.2 was in there at somepoint, but I have no idea how it may have gotten removed.
Is it possible that the 8.2 RTE version was installed as a demo, and automatically removed after a time period expired?
12-18-2009 01:10 PM
Couple of things you could check. Use windows explorer and see what is included under TestStand 4.1>>UserInterfaces. My install shows LV, CVI, VB.Net, CSharp and C++ using MFC as available interfaces.
In TestStand Editor select the Configure>>Adapters>>LabVIEW>>Configure Button and see what run time engines are available.
12-18-2009 02:37 PM
Yup, thanks. A Coworker suggested those things, and it looks like the adapters support all four LV versions. Also, the UI's all appear to be there too. So I'm even more confused. Not today, but I'll have to try running the code again soon, and see what the results are. I won't be completely surprised if this problem fixes itself. (Maybe a little Christmas miracle 😉 )
Have a great weekend everyone, and thanks again for your help.
David