Verify first, configure later. A sensor that streams correctly on its factory address is known-good hardware. If you change the IP first and the connection then fails, you cannot tell whether the network or the sensor is at fault.

What to look at

Open the point cloud view in your software and check three things:

CheckHealthyNot healthy
ShapeWalls and objects appear at the right distance and orientationEverything at 0, or a single ring
StabilityPoints stay put; noise is a thin bandCloud flickers or collapses
CoverageFull configured angular spanWedge missing at one end

Orientation

Angles increase clockwise seen from above, with zero at the connector face. Confirm this against a known target — a wall straight ahead should show up where you expect it. Mounting rotation is the usual source of a mirrored scene, and it will make every later calibration step wrong.

Common issues at this stage

SightCause
Cloud appears then freezesPower supply cannot sustain spin-up current
Sparse or noisy points on one sideWindow or cover in the optical path
Only a partial arcObstruction, or the sensor is mounted too close to a surface
Nothing at allSensor found but not streaming — check the software’s device state

Next

Once the cloud is stable and correctly oriented, move on to Set IP.