On this page
search_off
Cannot Find the Sensor
The device list is empty. It is almost always the host subnet.
First check
# 1. What is your adapter's address?
ifconfig en0 # macOS
ipconfig # Windows
# 2. Can you reach the sensor at its known address?
ping <sensor-ip>
If ping fails, the rest of the software configuration does not matter — fix the network first.
Cause ranking
| # | Cause | Check |
|---|---|---|
| 1 | Host adapter on a different subnet | Compare the first three octets with the sensor’s address |
| 2 | Adapter set to DHCP and pulled an address from a router | Look for a 192.168.x or 10.x address that is not the sensor’s subnet |
| 3 | Wrong sensor default address for the model | Confirm on the series page |
| 4 | Sensor not powered | Link LED off — see Topology |
| 5 | Software scanning the wrong adapter | Wi-Fi and VPN adapters can take priority |
Fix
Set the adapter manually to a free address in the sensor’s subnet, same mask, no gateway. Step-by-step for both platforms in Network & host setup.
Then rescan. The device should appear within a few seconds.
A VPN client is a frequent hidden cause: it installs a virtual adapter that the
software may scan instead of Ethernet. Disconnect the VPN before concluding the
sensor is faulty.
If it still does not appear
| Test | Interpretation |
|---|---|
| Ping the sensor from a different machine | If it answers, the sensor is fine and the problem is this host |
| Try option C wiring (direct 12 V) | Rules out PoE negotiation problems |
| Check the switch port’s PoE budget | An over-budget port may never power the device |
Next
Once found: First point cloud.