01-12-2013 09:56 AM
Everyone,
I am new to machine vision and I had some questions as to what I should expect from my vision system in regards to speed and acquisition time. I can start by describing the system I am using.
I have VBAI 2010 for software
The program runs on x64 windows 7 computer with 8 gigs of ram
I have 2 types of cameras on the line, Basler Ace 2500 14gc and Basler Ace 1300 30gc.
The cameras run to a Ethernet switch and then from the Ethernet switch they go to the GigE NIC of the PC.
I use a PC based control software to send triggers through modbus to VBAI 2010
So, for me to send a trigger to VBAI through Modbus, and to receive data back from VBAI after the inspection is complete is taking me around, 500 msec.
So what happens in these steps,
I send the trigger, which initializes the inspection. The inspection starts out with an acquire image(Basler Ace 1300 30gc, set to Mono8/Set to single frame/snapshot). I find an edge, then set a coordinate system, then find another edge and I use the y pixels from this edge in a calculator step. The calculator step just is a multiplication step to change pixels to thousandths of an inch. I then send this calculator number back through modbus to the PC control software.
This whole process takes around 500ms.
So what I am wondering is if this seems like an appropriate time? I have done research on line about acquisition speeds and from what I read I feel like this is a slow time. Does anyone have any pointers for me or things to attack to help reduce cycle time. I am getting push back to try and reduce the cycle time by 200 msec and I don't know if this is a realistic goal or not.
Also with the Basler Ace 2500 14gc I am seeing times in the 1 second range for similar inspection steps(really only an acquire image,detect object, calculator step). Now I do understand that this camera will be slower due to the reduced framerate but I am also looking to cut the fat out of these inspections as well.
All help is appreciated.
Thanks for your time
01-12-2013 11:33 AM
01-12-2013 01:18 PM
Context states the following
Wait for Nect Image - Waits for the next available image before transferring an image
Immediate - Immediately transfers the current image if it is newer than the image that was last acquired