Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

migrating viosion buider AI 2.6.2 scripts to Labview 7.0

I read other posting discussing similar issues, but none fo them specifies what I have.
In my inspection, I simulated the acquistion from a image stcks, then did pattern-recognition and reported the matches. It worked fine.
But when I tried to migrate my scripts from VBAI to labview, it generated vis doing nothing (see figure in the attachment).
Then I tested other inspections included in the tutorials. After the migration step, they all generated the same vis (identical block diagrams and front panels) as I got with my own scripts, which would not do any inspections they are suppoesed to. I tried to run several of these vis, after I hit the start button, it just kept saying "Failed" in the indicator.  A closer check revealed that in the block diagram there is no proper blocks which specify the directory of the images that are to be inspected.
 
0 Kudos
Message 1 of 6
(3,716 Views)

Hey Bou,

In the Readme for the VBAI 2.6.1 it says the following:

Migration to LabVIEW

Vision Builder AI 2.6.1 can create LabVIEW VIs that implement the steps of your inspection diagram. This feature requires LabVIEW 7.0 or later and IMAQ Vision 7.1 or later.

So make sure that you are using both LabVIEW 7.0 or higher and Vision 7.1 or later. If you have Vision 7.0 then the code might not migrate successfully.
 
Also, Vision Builder AI can be used used for 30 days in evaluation mode. The software is fully functional in evaluation mode, except for code generation. So if you have not activated the software yet, then the LabVIEW code generation will not work properly, so make sure it is activated in the NI License Manager.
 
If you have activated the software, and you have all of the minimum requirements, then something else might be going on. Also, you mentioned that you have VBAI 2.6.2, but currently there is no version 2.6.2, so I was wondering what version that you do have? Also, you did not attach the VI's to the attachment that you mentioned in your post. Please attach your VBAI generated VI's so that we may try to open them on our systems to see what you are seeing. Thanks.
 
Please, let us know how things go, and let us know if you have any further questions or concerns. Thanks, and have a great day.
 
Regards,
DJ L.
0 Kudos
Message 2 of 6
(3,699 Views)

Thanks, DJL.

I rechecked my system. It covers the basic requirement you have mentioned: VBAI is v2.6.1 (there was a typo in the previous post), Vision is v7.1, Labview is v7.0. They are all activated.

It means there is somthing else wrong in the migration process.

Here I will attach the VIs generated from the VBAI scripts. Like I said, no matter which VBAI script was used to generate the VIs, they gave enventually the same package.

Thanks again!

0 Kudos
Message 3 of 6
(3,690 Views)
I forgot to attach the VIs. I compressed all of them into .zip format.
0 Kudos
Message 4 of 6
(3,684 Views)
Hi, DJL
 
I got my application working now. I found that I have to first launch the Labview before I do the migration. In the Help file, it says "You must have launched LabVIEW at least once on your computer before migrating an inspection properly."  I was mistaken that if I ever used Labview on my computer, I would be fine. It turns out to be the other way. Sorry for all the confusion, It is my pleasure to get support from you.
 
Yun
0 Kudos
Message 5 of 6
(3,684 Views)
Hey Yun,
 
I am glad to hear that you were able to successfully migrate your VBAI code to LabVIEW. Good luck in all you applications.
 
Regards,
DJ L.
0 Kudos
Message 6 of 6
(3,677 Views)