Your SICK ID gives you access to our extensive range of services. This includes direct online orders, price and availability checks, and access to our digital services.
picoScan100: How to find the IP address without SICKs discovery function?
Article No: KA-10422
Version: 1.0
Subject to change without notice
This page explains how to find the device IP address without SICKs discovery function.
Related Products
LRS4000
LMS4000
LMS1000
TiM
LMS1xx
NAV2xx
LMS5xx
LD-OEM
picoScan100
LD-LRS
LMC1xx
LMS4xx
NAV3xx
3D LiDAR sensors
Table of Contents
Background
The picoScan100 can disable SICK’s proprietary device discovery via UDP broadcast for cybersecurity reasons.
When this function is turned off, the device does not reply to the standard search in SOPAS ET or AppManager.
Even when disabled, the device announces its IP address using network mechanisms like Gratuitous ARP. These can be used to locate the device.
Identify Device via ARP using Wireshark
Connect the sensor directly to your PC or a local switch.
Start Wireshark and capture packets on the Ethernet interface.
Apply the display filter arp.
Look for entries with a MAC address beginning with 00:06:77 (SICK).
Read the IP address from the packet details and connect to the sensor with this address.
Windows Procedure using “arp -a”
Open a command prompt as administrator.
Run arp -a.
Locate a line containing a MAC address starting with 00-06-77 (SICK).
Note: This works only if the sensor’s IP lies inside your subnet. To reach devices outside your default subnet, configure your network adapter with a wide subnet mask (255.0.0.0).
Linux Procedure using arp -n
Connect the sensor via Ethernet.
Run arp -n.
Look for a MAC address starting with 00:06:77 (SICK).
Note: This works only if the sensor’s IP lies inside your subnet. To reach devices outside your default subnet, assign a wide subnet mask (255.0.0.0).
Summary
Discovery may be disabled due to cybersecurity configuration.
Use ARP inspection in Wireshark, Windows, or Linux to identify the IP address.
Use subnet mask 255.0.0.0 for a broad search if necessary.
Do not use 0.0.0.0 as it is not a valid subnet mask.