Skip to content

Connection & Acquisition Issues#

Use this page if the RadarImager is not found, cannot be opened in the client, or no new image is acquired. For full setup instructions, refer to the linked setup guides.

Device is not found or cannot be opened#

Typical symptoms:

  • The device does not appear in the Impact Control Center device list.
  • Clicking Update does not find the device.
  • The device is visible, but cannot be used reliably.

Check the following:

  • Verify the Power LED and Status LED. A non-blinking status LED indicates an error condition.
  • Make sure the Ethernet cable is connected to the RadarImager RJ45 port.
  • Configure the host with the static IP settings from Network Configuration.
  • Use the correct network adapter on the host system.
  • In ICC, click Update and then Use as described in Connect with ICC.
  • On Linux, ensure the firewall rule for ICC is present if a firewall is active.

The RadarImager does not start correctly#

Typical symptoms:

  • The Status LED stays permanently on.
  • The Status LED stays permanently off.
  • The system never reaches the normal blinking state after power-up.

Check the following:

  • Make sure the Ethernet cable is connected to the RadarImager RJ45 port during startup.
  • Verify the expected Power LED and Status LED behavior.
  • If the Status LED remains permanently on or off, or the RadarImager never changes to the normal blinking state, contact Support.

No new image is acquired#

Typical symptoms:

  • The device is connected, but the image does not update.
  • Pressing Acquire does not result in a new image.
  • No image or the same old image remains visible.

Check the following:

  • Confirm that a trigger event really occurs while the object passes the system.
  • Watch the Status LED during acquisition: in normal operation it should be blinking, and when a trigger event is detected it should briefly switch to fast blinking. If this change does not occur, the RadarImager is most likely not receiving a trigger event.
  • Verify that the trigger sensor is connected to Trigger Port1 as required in Hardware installation.
  • Check useExternalTrigger. If it is disabled, incoming trigger signals are ignored.
  • Ensure the object fully passes below the RadarImager during acquisition.
  • In ICC, make sure the device has been opened with Use and Acquire is set to receive images in ICC.

Images are received incompletely or transmission errors occur#

Typical symptoms:

  • Transmission errors occur during acquisition.
  • Image reception is unstable although triggering works.

Check the following:

  • Verify the configured MTU size as described in Network Configuration.
  • Ensure that all components in the network path support the configured MTU size.
  • If Jumbo Frames are used, make sure the network adapter, switches, and any other intermediate components all support this MTU consistently.

Deeper layers cannot be selected#

Typical symptoms:

  • Higher values for layerSelection.indexes are rejected.
  • Layers below a certain depth cannot be selected.
  • Updating the layer index fails from a certain depth onward.

Check the following:

  • Verify that distanceZToDeepestLayerOfInterest is set large enough for the desired depth.
  • Keep in mind that the maximum selectable layer index is limited by distanceZToDeepestLayerOfInterest.
  • After changing distanceZToDeepestLayerOfInterest, trigger a new measurement, because the updated depth range only takes effect with the next measurement.

Trigger behavior is wrong or inconsistent#

Typical symptoms:

  • Images are only acquired intermittently.
  • Every second pass is captured incorrectly.
  • Direction-sensitive triggering does not behave as expected.

Check the following:

  • Verify imageTriggerMode. Use IMAGE_TRIGGER_SIMPLE for a single trigger sensor and IMAGE_TRIGGER_DIRECTION_SENSITIVE only if two sensors are installed.
  • Verify imageTriggerRisingEdgeDetection matches the electrical behavior of the trigger sensor.
  • Ensure the trigger sensor generates one clean, well-defined edge per object. Irregular, sloped, or vibrating trigger geometries can create multiple trigger edges.
  • Make sure the trigger setup prevents the sensor from triggering multiple times for the same object.
  • In direction-sensitive mode, ensure Port1 is mounted closer to the RadarImager than Port2.
  • Ensure the distance between consecutive objects is large enough so the trigger sequence cannot be interpreted incorrectly.

If you only want to suppress captures in the reverse direction, see imageTriggerMode and Hardware installation.