Skip to content

How To: Troubleshoot Lost Packets or Frames While Using GigE Cameras#

You may notice packets or frames being dropped when simultaneously grabbing images from multiple cameras (e.g., a hardware trigger running two cameras in parallel).

Typically, this is due to some hardware caches or buffers on a network switch or NIC becoming temporarily overfilled due to the sudden burst of incoming network packets.

A handy way to check for lost packets/frames is to observe the statistics for your camera in the pylon Viewer:

  1. Switch to Guru level.
  2. Click the camera's name in the device tree of the pylon Viewer to select the camera.
  3. Select Stream Parameters and then Statistics.

If you found out that you are losing packets/ frames while running your GigE camera, you may try to optimize the configuration of your network adapter.

To optimize your network adapter, you can do the following:

  1. Open the Network Connections window in the Windows Control Panel.
  2. Right-click the name of the connection for your network adapter and click Properties from the drop-down menu. The Properties windows opens.
  3. Click Configure. A controller properties window opens.
  4. Click Advanced. Select the following parameters in the Properties group and set their values in the value group:


Depending on the network adapter model, the parameter names of your network adapter may differ from the ones shown below. Also, the ways of setting the parameters may differ, and some parameters may not be available.

  • Set the Jumbo Frames (or Jumbo Packets) parameter to its maximum value. If no Jumbo Frames parameter is present, select the parameter which relates to frame size and set its size to the maximum value, which typically is 1.5 kB (1500).

  • Select the parameter which relates to the number of receive descriptors (e.g., Receive Descriptors) and set it to its maximum value.

  • Select the parameter which relates to the number of CPU interrupts (e.g., Interrupt Moderation Rate) and turn this feature off (or set it to its lowest value).

For your network adapter, the way of setting the number of CPU interrupts may differ. You may, e.g., have to use a parameter to set a low number for the interrupt moderation and then use a different parameter to enable the interrupt moderation.

Additionally, you should optimize the configuration of your GigE camera as well:

  • If your network adapter supports Jumbo Frames, set a Packet Size (in the Transport Layer of a camera in pylon Viewer) to a value <= Jumbo Frames value from your NIC (e.g. 3000, 6000, 9000 [KB]).


    For troubleshooting purposes, start with both the NIC and the camera at a packet size of 1500. As this is the supported packet size of even older 100BaseT networks, it is a very reliable starting point.

  • Increase the Inter-Packet Delay (in the Transport Layer of a camera in pylon Viewer) to a value that lets you still reach the desired frame rate.


    In some cases, you may need to increase the Inter-Packet Delay to its maximum in order to solve the problem of losing packets or frames, which will cause reduction of the maximal camera's frame rate.

  • Optionally, you can Increase the Frame Transmission Delay to delay the start of the frame's transmission. On systems with multiple cameras, this can also lower the load on the switch or NIC.

To automatically configure your cameras for the optimum packet size and inter-packet delay, you may also use pylon GigE Configurator delivered with pylon.

Back to Knowledge Articles