NI Vision Builder migration to Labview

[Ahmad_k]

I'm using the NI Vision builder 2011 to inspect a product. When i'm done, I migrate the to Labview to customize the interface and adding a lot of other control.

Then i found that i need to modify and add another steps in the inspection. How can i do this without losing all the things i have done with the new Interface ?

Because when i migrate to labview the whole VIs as replaced with the new one. Is there a way to only update the inspection VIs ?

[ChristopheC]

The code generated by Vision Builder is not part of an Express VI that you can reconfigure. Once you migrate it to LabVIEW, you basically get an implementation of the inspection at the time when you generate the code.

If you need to modify the inspection, you need to migrate it again to LabVIEW.

I would instead recommend using the LabVIEW API to drive Vision Builder. This will allow you to maintain the link with your Vision Builder inspection. With the API, you can programmatically drive the Vision Builder AI engine (without showing the Vision Builder AI UI), and still create your own interface. You can open an inspection, run it, and retrieve results within your LabVIEW application.

You can find examples showing how to use the Vision Builder AI LabVIEW API in the folder <Program Files>\National Instruments\Vision Builder AI 2011\API Examples.

The main consideration is for deployment: if you migrate the code to LabVIEW, you basically just need to purchase a Vision Development Module Runtime Engine.

If you're using the Vision Builder API, and Vision Builder is running on a remote target, then there is not additioncal costs. If Vision Builder is running on a deployed PC, then you need to buy a Vision Builder AI runtime licence.

Best regards,

Christophe