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.
The SEC200 can be accessed using different mDNS hostnames, depending on the number of devices connected to the local network and whether a specific device needs to be addressed.
Using an mDNS hostname provides several advantages:
The current IP address of the SEC200 does not need to be known.
The hostname remains usable if the IP address changes, for example when DHCP or Auto IP is used.
A specific SEC200 can be identified and accessed by its serial number.
The hostname can be used in applications that accept a hostname or IP address.
The available mDNS hostnames depend on the number of SEC200 devices connected to the local network:
mDNS hostname
Use case
sec200-sick.local
Access to the SEC200 if only one SEC200 is present on the local network.
sec200-sick-2.local
Access to the second SEC200 on the local network.
sec200-sick-3.local
...
Access to the third SEC200 on the local network.
Additional SEC200 devices are assigned an incrementing number.
Access to a specific SEC200 identified by its serial number.
The mDNS hostname can be used, for example, to:
Open the SEC200 user interface in a web browser.
Ping the SEC200 from a terminal or command prompt.
Establish a TCP/IP connection using tools such as Hercules.
Network limitation
mDNS communication is limited to the local network segment because mDNS multicast traffic is normally not forwarded by routers. The computer and the SEC200 must therefore be connected to the same Layer 2 network or broadcast domain.
An mDNS hostname cannot normally be used to access an SEC200 located in another subnet, VLAN, or routed network. Cross-network resolution is only possible if the network infrastructure provides a specifically configured mDNS gateway, reflector, or repeater.
