10-09-2007 01:48 AM
10-09-2007 07:17 AM
10-10-2007 03:12 PM
Hi danilo,
In response to your latest post, yes you can change camera parameters on the fly but not all of them. Which parameters are you wanting to change? You may need to reinitialize the camera each time depending on what parameters.
There could be a few reasons your acquisition time is slow. It would take longer than it should if you are opening and closing a camera session during each step. A better solution would be to initialize all the cameras at the beginning and then close them after you have run through the various steps. Is there a specific reason you are using VB instead of LabVIEW? Using LabVIEW would allow you to run these steps in parallel if needed in your applications.
10-11-2007 12:29 AM
10-11-2007 11:18 AM
Hi danilo,
Yes, you can change parameters when using a GRAB to do the acquisition, but the specific parameters you will be able to change are determined by the camera. Some are read/write while others are only one or the other, but it's not universal to every camera.
Can you give some more information on how you are doing the programming? Possibly even paste a section of the code in so I can see the exact steps you are using?
10-11-2007 02:06 PM
10-11-2007 02:55 PM
Hi,
If you are just acquiring one image per iteration then using grab will not give you an added benefit as far as speed. When acquiring a single image, grab and snap will take about the same time except grab may even have some extra overhead associated with it. Do you know that it is the acquisition that is taking 500 ms and not the analysis? The actual parameters you set for the camera will also affect your acquisition time.
I am sorry I wasn't very clear in my last post. You may be able to change/set all the required parameters for the camera when using snap, but some may not be available for setting in grab. This is dependent on the specific camera. You can either use code to get the camera's attributes and if they are read/write or get the settings from the camera documentation. Coding it as trial-and-error may be quicker for you, though.
10-11-2007 03:21 PM
10-12-2007 09:39 AM
Hi danilo,
That is interesting that it is taking 500 ms since calculations show it should only take around 82 ms or so. One way to test and see if you get the same results in grab would be to test in Measurement and Automation Explorer (MAX). Simply do a grab and take the inverse of the fps and see if that will give you more satisfactory results. Also test it against the results from doing a snap in MAX.
10-12-2007 10:26 AM