This Document is not yet Rated

Rate this Document

Custom Vision Builder AI Steps do not function correctly on the CVS

Primary Software: Vision Builder for Automated Inspection
Primary Software Version: 3.0
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem: I created a custom step for Vision Builder AI (VBAI) 3.0.1 which works fine on a Windows system. But the same step when compiled for a CVS does not work. However, this only happens if I use Coordinate Systems, Global Variables or Previous Results in my custom step. How can I fix this issue?

Solution: When any one of the following VIs is used in a Custom Step and then deployed to a CVS, the VIs do not return the correct values and instead return empty arrays.

• VIs VBAI CoordSys Name Utility.vi
• VBAI CoordSys ID Utility.vi
• VBAI Get Global Variables.vi
• VBAI SDK Get Result.vi

To fix this issue, replace the respective VIs from C:\Program Files\National Instruments\Vision Builder AI 3.0\Plugins folder with the ones attached below.
Then rebuild your custom step in LabVIEW for the Real-Time system. Copy your new custom step to the CVS and then reboot your CVS.

Related Links:

Attachments:





Report Date: 04/30/2007
Last Updated: 04/30/2007
Document ID: 48T9GT5L

Your Feedback!	Poor  |  Excellent							Yes	No
Document Quality?							Answered Your Question?
	1	2	3	4	5
Document needs work? Please tell us why.
Please Contact NI for all product and support inquiries.