Is it possible to ignore the dropped packet/frame error during

2 min readJan 1, 2022

Is it possible to ignore the dropped packet/frame error during acquisition from a GigE Vision camera?

I am using a GigE Vision compliant camera with the Image Acquisition Toolbox GigE Vision adaptor.

Occasionally, I get a an error related to a dropped packet / frame and the image acquisition process stops:

ERROR: gige: Block/frame 24 is being dropped because a lost packet is unable to be resent. There are several possible causes for packets being lost. See the troubleshooting information in the "Configuring GigE Vision Devices" section of the Image Acquisition Toolbox documentation.

Is there a way to catch this error, or is there a way to ignore the dropped packet / frame and continue acquisition?

NOTE:-

Matlabsolutions.com provide latest MatLab Homework Help,MatLab Assignment Help for students, engineers and researchers in Multiple Branches like ECE, EEE, CSE, Mechanical, Civil with 100% output.Matlab Code for B.E, B.Tech,M.E,M.Tech, Ph.D. Scholars with 100% privacy guaranteed. Get MATLAB projects with source code for your learning and research.

Note: This error can occur if the Ethernet adapter, camera network connection, and camera GigE streaming parameters (PacketSize and PacketDelay) are not configured for optimum operation.

The dropped packet / frame error is taking place in the Image Acquisition Engine thread and cannot be caught with try/catch.

One option, which, depending on the application, might be useful is to use the following command to disable errors when dropped frames occur and to continue acquisition:

imaqmex('feature', '-gigeDisablePacketResend', true);

Note: ‘gigeDisablePacketResend’ option will be reset by the imaqreset command.

When dropped frames are allowed, it is relevant to know how many frames and which frames have been dropped during acquisition. The BlockID field in the metadata returned by getdata corresponds to the frame number set by the camera. A simple way to visualize this is to plot the acquired frames’ BlockID and BlockID differences, as in the following code snippet:

SEE COMPLETE ANSWER CLICK THE LINK