Vision builder migrating to labview... Many VI

[Brad]

In particular, I'd be interested to learn if you want to control VBAI on the same target that your LV VI is running by using the API or do you want to control a different RT target that has VBAI running from a master RT target that is just running a LabVIEW VI using the API to control VBAI remotely? Or something else?

Thanks,

Brad

[artex]

Hi Brad, thanks for your input.

Well, actually, I am new to LabView  so, better explain what my need is:

We have designed a  fruit sorting machine currently running on proprietary software & hardware. What we want is to use LabView instead for controling it. 

Basically, we do several image inspections (4 RGB and 4 Infrarred images) and then we sort the fruits via actuators. All this done in over a conveyor belt, in real time.

So, after what I had asked/read/researched, I think using VBAI + LabView (via API or Shared Variables or migrating VBAI to LabView) is the way to go. However, I am not really sure if just using LabView I would be better of.

I hope this clarify better what we need to do.

Regards

[Brad]

So are you using a real time target or Windows to do the inspection? Do you have multiple RT targets/PCs? Just trying to figure out how you coordinate the images from all those cameras and where the decision making is happening.

Thanks,

Brad

[toan.nguyen]

Hello, I'm having the same problem where I'm trying to run the LabVIEW code generated by VBAI on a different camera. Have you figured out how to fix this?

Thanks

[Brad]

Depending on the complexity of your VBAI inspection, you might have more success with using the Vision Acquisition Express VI to acquire images and the Vision Assistant Express VI to process those images.

This will make it easy to edit the Acquisition Express VI to quickly change the camera associated with the code without having to go through a lot of compolicated code.

Hope this helps,

Brad