Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

Adquisition and inspection with 2 gige cameras Basler in Vision Builder 2010

Hello,

I am in course of making an application with 2 cameras basler scA1000-30gm in Vision Builder 2010 with ni DAQmx.

I have seen the example solutions for the multiple camera adq. and i have made a program in VB2010 in order to adquire the 2 images and inspect them.

My issue is with the point of Timeout Error of the Image Adq. Step. i observe sometimes one of the two cameras is in Timeout Error so the process is not being completed.

I have put 5000 for the Timeout.

I also observe sometimes i have double trigger. Why that happens when i am sending for every trigger one pulse of 10 miliseconds?

 

Someone could resolve my questions?

 

I am new in the area, so i am learning all that stuff, and i am excited about the results.

Well, just to resolve these issues.

 

I can send my program if that needed, also more info about the application.

 

Thank you in advance,

Ioannis.

0 Kudos
Message 1 of 3
(3,999 Views)

reduce the ammount of bandwidth each camera is using from 8000 to 2048.  THis will give eack camera enough bandwidth, without blocking the other.  If both devices are using Jumbo packets, and they are both set to 8000, then there is no extra room on the network, so one will usually time out.

Machine Vision, Robotics, Embedded Systems, Surveillance

www.movimed.com - Custom Imaging Solutions
0 Kudos
Message 2 of 3
(3,847 Views)

Changing the packet size on GigE Vision is not the same as on IIDC FireWire. It has nothing to do with the bandwidth reserved for the camera. Reducing the packet size just adds more congestion; not less.

 

If you have multiple cameras sharing bandwidth via a hub you want to throttle them using the Peak Bandwidth Desired Feature and split up the bandwidth such that the total is <= 1000Mbit.

 

That said, based on the errors described, I don't think bandwidth is the issue here.

 

I suspect you need to look at how you are triggering the camera and what options you are using in the Acquire step. Depending on the options you select, it might be waiting for the "next" image. This means that it will always wait for a new image, even if there are ones just acquired that you haven't seen yet. You'd have to examine the mode you are using and how you are triggering the camera with respect to the VBAI code and see if it makes sense.

 

Eric

0 Kudos
Message 3 of 3
(3,842 Views)