VBAI run time takes more CPU usage

[SaranVenkateshS]

Hi all. i am using vision builder .

Here my application will acquire image (GigE) and store it to particular location .

Once i do continuous run the CPU usage become above 50%.

[Brad]

A better indication of how much processing time VBAI is taking would be on the Processes tab in Task Manager. Look for the Vision Builder process to see how much it accounts for. When acquiring from GigE cameras, you can significantly reduce the processor overhead by checking some of the caveats mentioned here:

http://www.ni.com/white-paper/5651/en/

Also check out the trouble shooting section and Part II for more details on:

- jumbo packets (which increases efficiency)

- high perfromance driver (which reduces CPU overhead)

- check for packet loss

Hope this helps,

Brad

[SaranVenkateshS]

Hi Brad,

Thanks a lot for your reply..

Let me try your advise .

[SaranVenkateshS]

Hi Brad ,

Still facing same problem..

Once i start vbai file my cpu usage exceed 60 % ..'

if i run multiple 100 % cpu usgae .

Help me to find the solution in viison builder reduce cpu usage .

[ChristopheC]

Brad's suggestions were good ones. Try adding a Delay step with a 1ms delay.

[SaranVenkateshS]

Hi Brad , ChristopheC,

your Suggetstion helped me .

What i did it is .

Insided of continus acquire image i did snapshot .

then i added delay step .. it gives some effort. thanks .

I have another Doubt ..

I am using vbai with labview.

here i need to inspect (vbai) three files.

when i do lanuch engine - >  open connection -> run once = takes so long time .

So it did

while start my sequence 

lanuch engine - >  open connection

when every i need i do run once .

So its saves my timing .

(So once here i am running all the three engines initally )

that time cpu usage increase .. to 90 % )

[SaranVenkateshS]

is there any good way to do multiple vbai files process

[Brad]

It's probably worth taking a step back and making we sure understand what you want to accomplish before making more recommendations. Do you want to acquire from 3 different cameras and log their images to disk as fast as possible, or are you doing other processing as well? If you're just doing acquisition and logging, I would recommend doing it all in LabVIEW with a separate loop for each camera. If you're doing other processing that is not as straight forward to do in LV and that's why you're using VBAI, then we need to know if LabVIEW needs to be synchronized with the inspection, or if it can just start the VBAI inspection and then get results/images periodically. Do you need results/images in LV? Please send your LabVIEW VI if you're still having trouble. Also, I would not recommend using a snapshot mode in the inspection as a way to try and reduce processing load. Is there a reason having your processor so high is a problem? That just means the inspection is running faster and requiring more processor...is there a reason you don't want it to run as fast? You could use a Run Once in a loop in LabVIEW with a delay (another good reason to send your LV code because if you have a while loop without a delay, this is a likely cause for high CPU usage.

Hope this helps,

Brad