Decimation resulting in large number of incomplete frames.
I am trying to increase the frame rate of my acquisition, so I am looking in to using decimation (as opposed to binning) to reduce the image size and increase frame rate. However, when I set decimation to 2x2, I am getting a large proportion of frames that are incomplete (roughly 1 in 5 frames) even when I run at the same frame rate (30 fps) that has been working for 2x2 binning. Is there any reason why decimation is causing so many frames to be incomplete?
-
Hi Ryan,
What version of Spinnaker are you testing with? Have you run the AdapterConfigGUI that comes included with Spinnaker? If not, please do so. Also, it would be helpful to know what firmware the camera is running as well; this can be determined by right-clicking on the camera model in SpinView and selecting "properties". The firmware version is listed as the "Device Driver Version".
0 -
Thank you for your response. I do not think it is a problem with my gigE adapter because I am not experiencing the same problem when I use 2x2 average binning, only when using 2x2 decimation (I would expect less computationally challenging, so this confuses me). Is there any reason why decimation, rather than average binning, would cause this type of problem?
I have also gone through the possible solutions at this link: https://www.flir.com/support-center/iis/machine-vision/application-note/troubleshooting-image-consistency-errors/ and none seemed to produce any improvement.
When I look at device driver version in spinview, it says none: 0.0.0.0
PySpin.System.GetInstnce().GetLibraryVersion() returns "4.0.0.116"
0 -
Hi Ryan,
No, there shouldn't be any reason for decimation to cause more incomplete images than binning.
I think we should take a closer look at this. Could you please open a support ticket on https://flir.custhelp.com/app/ask ?
Best regards,Manuel
0
Please sign in to leave a comment.
Comments
3 comments