Symptom index

What you seeMost likely causePage
Sensor never appears in the softwareHost adapter on a different subnetCannot find sensor
Worked before the IP change, gone afterHost adapter still on the old subnetHost IP mismatch
Cloud appears, freezes after a few secondsPower supply cannot sustain spin-up currentNo point cloud
Two sensors behave intermittentlyDuplicate addressesIP conflict
Calibration residual will not settleBad reference point or wrong geometryCalibration issues
Tracks correctly but response feels lateHost-side pipeline, not the sensorInteraction lag

Start here: the two network faults

Roughly speaking, if the device list is empty or a sensor vanished after configuration, you do not have a hardware fault. You have an addressing problem.

  ① adapter subnet ≠ sensor subnet        →  cannot find sensor
② sensor IP changed, adapter did not   →  host IP mismatch
  

Both are fixed in minutes. Both are also frequently misdiagnosed as dead hardware, which is why they lead this page.

Before you contact support

GatherWhy
Sensor model and serialIdentifies hardware revision
Sensor address and maskConfirms the subnet reasoning
Host adapter address and maskThe other half of the same calculation
Link LED stateSeparates power from data faults
Whether the cloud ever appearedSeparates “never worked” from “regressed”

Still stuck?

Contact support@lidarmagic.com with the items above. Attaching a photo of the sensor’s LED state shortens most exchanges.