How it presents

An address conflict never looks like a clean failure. Typical symptoms:

  • The device answers, then goes silent, then answers again
  • Two sensors appear as one in the software, or the model reported is wrong
  • Ping succeeds roughly half the time
  • Calibration fails intermittently with no code change

Diagnose

  # Look at the ARP table: two MACs, one IP
arp -a | grep <sensor-ip>
  

Two different MAC addresses against the same IP confirms the conflict.

Fix

SituationAction
Both are LIDARMAGIC sensorsChange one to a free address, one at a time
A sensor collides with a laptopMove the sensor outside the DHCP pool
A sensor collides with another vendor’s deviceReserve a dedicated range for sensors

Change addresses one device at a time. With both unplugged except one, the remaining device is unambiguous.

Prevent

PracticeReason
Fixed addresses outside the DHCP rangeThe router never hands them out
A written address table per siteConflicts are found on paper, not in the field
Label each sensor with its addressThe next technician does not have to guess

Next

Addressing rules in general: Network & host setup.