Switching Between Vision Builder AI and LabVIEW Real-Time On the CVS Primary Software: LabVIEW Run-Time EnginePrimary Software Version: 7.1 Primary Software Fixed Version: N/A Secondary Software: N/A
Problem: If I have fired up my CVS and targeted it from LabVIEW RT on my host machine, why can I not subsequently target the CVS from VBAI? Solution: When the CVS boots up, an executable that could be considered the VBAI server is begun in the startup sequence. You can successfully target the CVS from VBAI initially. If you then stop targeting the CVS from VBAI and target from LabVIEW RT, you'll find that a dialog box will appear asking you about some certain VIs that are currently running on the remote device. These VIs are part of this LabVIEW-based executable that is the VBAI run-time server and are being run on the LabVIEW run-time engine. In order to successfully target from LabVIEW RT, you'll have to select the option to stop those VIs. This will stop the VBAI executable and leave the LabVIEW run-time engine in exclusive control of the CVS and you can then operate within LabVIEW RT. When you finish targeting the CVS from LabVIEW RT, you'll then be unable to target from VBAI again. Even when you reboot the CVS you will still not be able to target the CVS from VBAI. This is because when you stopped the VBAI Service from running and deployed a LabVIEW RT application to the CVS it modified the NI-RT.ini file to not load the VBAI_Startup.exe on boot. This is the VBAI run-time server that initializes all the VIs needed to connect VBAI to the CVS. So to retarget to VBAI you have two options:Copy NI-RT.ini File:
Related Links: National Instruments Image Acquisition and Vision Support Homepage Attachments:
Report Date: 01/28/2005 Last Updated: 05/23/2007 Document ID: 3HRHQ4WX |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
