Streaming & Configuration Issues#

Use this page if image transfer is unstable, the client cannot process the data format, or configuration changes behave differently than expected.

Streaming is unstable or frames are dropped#

Typical symptoms:

• Frame drops occur during acquisition.
• The client shows incomplete or unstable image updates.
• Problems occur especially with larger images or many layers.

Check the following:

• If you use GenDC, configure the MTU on the host as described in Network Configuration.
• Ensure that all devices in the network path support Jumbo Frames when using a large MTU.
• Reduce the most performance-critical parameters if frame drops persist:
  • objectSpeedX
  • objectLengthX
  • distanceZToDeepestLayerOfInterest
  • layerSelection.indexes
  • upscaleImage

Background:

• The RadarImager computational limits can show up as frame drops.
• Oversized GenDC containers are limited by Gigabit Ethernet transmission and can also overload the client side.

To estimate how much acquisition, processing, and transmission each contribute in your setup, see the Performance Estimation guide or try the Performance Estimation Tool.

The client cannot process the transmitted image data#

Typical symptoms:

• The client connects, but cannot decode the received image data.
• Multi-layer transfer causes compatibility problems.

Check the following:

• By default, images are transferred in a GenDC container.
• If your client does not support GenDC, enable GICStream.singleImage.
• Be aware that singleImage removes the GenDC container and its metadata.
• If you transfer many layers, review layerSelection.indexes and the GenDC limitations.

Useful references:

• Output Parameters
• Generic Data Container (GenDC)

A parameter change seems to have no effect#

Typical symptoms:

• You change a parameter, but the image does not change.
• Some settings appear to update only later.

Important background:

• Most parameters update the displayed image immediately.
• Some measurement parameters only take effect after a new measurement.
• While such a pending measurement update exists, image recalculation for other changes can be temporarily paused until a new measurement is performed.

Check the following:

• Trigger a new measurement by letting the object pass the RadarImager again.
• Recheck whether you changed one of these measurement-related parameters:
  • objectLengthX
  • distanceZToDeepestLayerOfInterest
  • reverseObjectMovementDirectionX
• If useExternalTrigger is disabled, no new trigger will overwrite the current image.

Settings are lost after restart#

Typical symptoms:

• The setup works during runtime, but after restart the parameters are back to defaults.

Reason:

• The current configuration is not persistent after restart or power outage.

Recommendation:

• Store the required parameter set in your application or commissioning workflow and reapply it during startup.
• Keep using the Configuration and Settings API documentation as the reference for the parameter values to restore.