On this page
build
Troubleshooting
Start from the symptom. Two failures account for most support requests, and both are network configuration.
Symptom index
| What you see | Most likely cause | Page |
|---|---|---|
| Sensor never appears in the software | Host adapter on a different subnet | Cannot find sensor |
| Worked before the IP change, gone after | Host adapter still on the old subnet | Host IP mismatch |
| Cloud appears, freezes after a few seconds | Power supply cannot sustain spin-up current | No point cloud |
| Two sensors behave intermittently | Duplicate addresses | IP conflict |
| Calibration residual will not settle | Bad reference point or wrong geometry | Calibration issues |
| Tracks correctly but response feels late | Host-side pipeline, not the sensor | Interaction 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
| Gather | Why |
|---|---|
| Sensor model and serial | Identifies hardware revision |
| Sensor address and mask | Confirms the subnet reasoning |
| Host adapter address and mask | The other half of the same calculation |
| Link LED state | Separates power from data faults |
| Whether the cloud ever appeared | Separates “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.