Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

Using Custom Step in the inspection

Hello,
I'm calling on VBAI 3.0 the custom step that i created in Labview 8.0. when i lunch the inspection a pop up message indicates me that my custom step in not available in this version of the software. In the host computer the program (custom step included) is working proprely, but once i targeted the custom step on the CVS to make an inspection it gives me this error message that i mentioned. is someone who can gives me guidance regarding this issue please?
 
Regards
 
Tchaou 
0 Kudos
Message 1 of 5
(4,199 Views)
Hi,
 
Once you're done developping your custom step in LabVIEW, you need to save it for distribution to be able to call it with the Vision Builder AI executable, or use it on the Compact Vision System. Select the menu Tools>>Vision Builder AI 3.0>>Save your Custom Step for Distribution...
If you plan to use it on the CVS, you need enable the checkbox "Build Step for RT target" and specify the IP address of the CVS. The wizard will build the step for the CVS and download it. You need to reboot the CVS to be able to use it.
When you design a step for the Compact Vision System, you need to make sure to use only functions supported by LabVIEW RT, otherwise, the step might be broken when run on the target. I am saying that because I remember that the step you were working on was using ActiveX controls, not supported on RT.
 
Best regards,
 
Christophe
Message 2 of 5
(4,190 Views)
Hi,
 
Thank you for your answer, was very helpful. I just want to know where can i found the list of kind of functions not surported by the CVS.
 
Regards
 
Tchaou
0 Kudos
Message 3 of 5
(4,177 Views)

Hello Tchaou,

If you connect to an RT target such as a CVS from LabVIEW, only the VIs that you can use in RT will appear in the functions pallette. This is the best way to find out which VIs you can use. If a function does not appear in the functions palette, you cannot use it.

A general rule of thumb is that any VIs that have functionality explicitly pertaining to windows will not work in Real-Time. Examples of these are: ActiveX, .NET, Report generation for Office, Registry programming, etc.

Hope that helps,

Jack J.

Message 4 of 5
(4,155 Views)
Hi Jack,
 
Thank you for your response.
 
Tchaou
0 Kudos
Message 5 of 5
(4,151 Views)