Handling incomplete frames in VmbPy with encoder-driven linescan camera

[robbyneven]

Hi,

I am using the asynchronous acquisition example from the VmbPy SDK with a linescan camera triggered by an encoder.

I’ve observed that if the encoder does not send enough pulses within a certain time window, the frame handed over to my Python application is marked as incomplete.

My questions are:

1. How can I determine how many lines of an incomplete frame are actually valid?
2. Are incomplete frames delivered due to an internal timeout in the Vimba SDK (i.e., no frame completion within a given window)?
3. When a buffer is reused, is it zero-initialized before being filled again, or could the invalid/unwritten region still contain data from a previous frame?

The main concern is avoiding the risk of interpreting old or uninitialized buffer content as valid image data.

Thanks in advance!

[arunprakash-avt]

Hi, we would like to know which linescan camera you are using?