Technical Application Notes
Click an item to read from the list below.

Technical Application Notes


 

 

Diagnosing and Fixing Connectivity Errors with Ladybug5

Diagnosing and Fixing Connectivity Errors with Ladybug5

Technical Application Note TAN2014013

Revised October 13, 2016

Subject

Technical Application Note (TAN2014013): Diagnosing and Fixing Connectivity Errors with Ladybug5

10348

Applicable Product(s)

  • Ladybug5

 

Application Note Description

This application note describes the how to diagnose a poor connection in a Ladybug5 system and provides recommendations for how to improve connectivity.

 

Diagnosing Connectivity Errors

Generally speaking, connectivity errors occur because the amount of data to be transmitted exceeds the capacity of the connection between camera and computer. Connectivity errors manifest in a variety of ways such as skipped frames, torn images, or failure to enumerate the camera.

LadybugCapPro collects event statistics that display events over time, including image inconsistency errors, link recovery counts, and skipped frames. If the connection is good, the only event value that should increase is the total number of frames. Constantly increasing values for the other events can indicate poor connectivity.

To view Event Statistics:

In the LadybugCapPro main window, click on the green button on the lower left corner. (This button turns red if errors were detected in the last 10 seconds.)

 

  • Image consistency errors—The number of images from the camera that have been corrupted.
  • Image conversion errors—The number of failures to convert the image, for example, debayering, post processing, or GPU failure.
  • JPEG compression/decompression errors—The number of times the camera has failed to compress the image or the library has failed to decompress the image.
  • Transmit failures—The number of image data packet transmissions since the start of capture that were not completed, and subsequently dropped, due to a buffer overflow on the camera. Transmit failures may result in torn images.
  • Recovery count (camera): The number of times the camera reconnects after a brief interruption, such as due to a faulty cable or other connection problem.
  • Recovery count (host): The number of times the host reconnects after a brief interruption, such as due to a faulty cable or other connection problem.
  • Skipped frames: The number of images since the start of capture that were not transmitted to the host system, and subsequently dropped, due to a buffer overflow on the camera. Skipped frames may be a symptom of a bandwidth bottleneck on the bus, or a load/latency issue on the xHCI card or CPU.

 

Recommended Components

Point Grey is continually testing for solutions that maintain optimum connectivity while supporting longer distances. Although a shorter cable (5 meters or less) is recommended, a hub may be used to extend the cable length beyond 5 meters and to improve connectivity. Point Grey recommends using a hub when using a laptop or when using cables longer than 3 meters.

 

The Ladybug5 has worked successfully with the following systems:

  • Dell Precision M3800 (2014 model)—tested and recommended by Point Grey
  • Intel NUC D34010WYK
  • Gigabyte Brix GB BXi7-4500
  • MacBook Pro (running Bootcamp)

For more information on configuring the Ladybug camera, see TAN2015008 Best Practices for Ladybug5, and TAN2008007 Using the Ladybug in a Mobile Setting.

 

Point Grey does not recommend the 5 meter ACC-01-2301 blue cable for use with the Ladybug5 camera.