12-11-2008 01:31 PM
I am running Testand 3.1 and Labview 7.1.1. I am able to deploy my package when using the LabVIEW development adapter, but get broken VI error's when trying to deploy using the Runtime Adpater.
More background:
I am sucessful building the package only the first time try to use the runtime adapter. If I make a change and try to build again using runtime adapter it error on the build. If I switch back to Development adapter it builds just fine.
In addition, if I use the installer (built using the development adapter) on the deployment machine, then run the operator interface, then switch adapters to runtime before running my sequenc, everything works fine. I do not want to have to mannually switch adapters on the deployment machine.
I have read other threads regaring this topic and I know it has to do with the LabVIEW vi.lib, but I cannot seem to make this work.
Any suggestions?
Regards,
Derek
12-12-2008 03:04 PM
Hi Derek,
It sounds like your VI's need to be mass compiled to LabVIEW 7.1.1. When building your installer using the LabVIEW development environment, you may have been asked throughout the build process to save multiple VIs. What is happening here is that those VI's are being saved to the current version of LabVIEW and being saved to the Distribution Files directory for the installer.
Unfortunately, the VIs on your development machine still remain in their old versions, therefore when you attempt to build using the LabVIEW run-time engine, TestStand realizes that the VIs have different versions and throws an error.
Try mass compiling your VIs and rebuilding the deployment with the LabVIEW run-time engine. Please post your results in this thread.
Thanks!
02-18-2009 02:59 PM
Hi Derek,
I was looking through the forums and just wanted to follow up on this one to see if this issue is resolved or if you are still experiencing this same problem.
Please let me know.