On this page
device_hub
IP Conflict
Two devices on the same address behave intermittently, and the pattern is hard to read.
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
| Situation | Action |
|---|---|
| Both are LIDARMAGIC sensors | Change one to a free address, one at a time |
| A sensor collides with a laptop | Move the sensor outside the DHCP pool |
| A sensor collides with another vendor’s device | Reserve a dedicated range for sensors |
Change addresses one device at a time. With both unplugged except one, the remaining device is unambiguous.
Prevent
| Practice | Reason |
|---|---|
| Fixed addresses outside the DHCP range | The router never hands them out |
| A written address table per site | Conflicts are found on paper, not in the field |
| Label each sensor with its address | The next technician does not have to guess |
Next
Addressing rules in general: Network & host setup.