Windows

Tested on Windows 10. The sensor hostname is os-991234567890.local (serial number on the sticker on top of the sensor).

Connecting the Sensor

1. Connect the sensor to an available Ethernet port on the host machine or router.
2. The sensor automatically obtains an IP address via link-local or DHCP, depending on network configuration.

The Sensor Homepage

1. Enter http://os-991234567890.local/ in your browser’s address bar to open the sensor homepage.

Determining the IPv4 Address of the Sensor

1. Open a Command Prompt by pressing Win+X, then A.

2. Ping the sensor to find its IPv4 address:

Command

ping -4 [sensor_hostname]

Example

C:\WINDOWS\system32> ping -4 os-991234567890.local

Response

Pinging os-991234567890.local [192.0.2.130] with 32 bytes of data:
Reply from 192.0.2.130: bytes=32 time<1ms TTL=64
Reply from 192.0.2.130: bytes=32 time<1ms TTL=64
Reply from 192.0.2.130: bytes=32 time<1ms TTL=64
Reply from 192.0.2.130: bytes=32 time<1ms TTL=64
Ping statistics for 192.0.2.130:
  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
  Minimum = 0ms, Maximum = 0ms, Average = 0ms

3. Alternatively, resolve the sensor IP using dns-sd:

Command

dns-sd -G v4 [sensor_hostname]

Example

C:\WINDOWS\system32> dns-sd -G v4 os-991234567890.local

Response

Timestamp     A/R  Flags   if   Hostname                     Address        TTL
14:22:46.897  Add  2       6    os-991234567890.local.  192.0.2.130    120

Determining the IPv4 Address of the Interface

1. Open a Command Prompt by pressing Win+X, then A.

2. View the IPv4 address of your interfaces:

Command

netsh interface ip show config

Example

C:\WINDOWS\system32> netsh interface ip show config

Response

Configuration for interface "Local Area Connection"
    DHCP enabled:                         Yes
    IP Address:                           169.254.1.100
    Subnet Prefix:                        169.254.0.0/16 (mask 255.255.0.0)
    InterfaceMetric:                      25
    DNS servers configured through DHCP:  None
    Register with which suffix:           Primary only
    WINS servers configured through DHCP: None
Configuration for interface "Loopback Pseudo-Interface 1"
    DHCP enabled:                         No
    IP Address:                           127.0.0.1
    Subnet Prefix:                        127.0.0.0/8 (mask 255.0.0.0)
    InterfaceMetric:                      75
    Statically Configured DNS Servers:    None
    Register with which suffix:           Primary only
    Statically Configured WINS Servers:   None

• In this example, the sensor is plugged into interface "Local Area Connection".
• The host IPv4 address is on the IP Address: line — here, 169.254.1.100.

Setting the Host Interface to DHCP

Set the interface to obtain an IP address automatically via DHCP. Useful for plug-and-play setups.

Command

netsh interface ip set address ["Network Interface Name"] dhcp

Example — with interface name "Local Area Connection":

C:\WINDOWS\system32> netsh interface ip set address "Local Area Connection" dhcp

Response: (no output)

Setting the Host Interface to Static IP

Assign a static IPv4 address to the interface. Useful when the sensor must send data to a specific IP.

Command

netsh interface ip set address name="Network Interface Name" static [IP address] [Subnet Mask] [Gateway]

Example — with interface name "Local Area Connection" and IPv4 address 192.0.2.1/24:

C:\WINDOWS\system32> netsh interface ip set address name="Local Area Connection" static 192.0.2.1/24

Response: (no output)

Finding a Sensor with mDNS Service Discovery

The sensor announces itself on the network via mDNS with service type _ouster-lidar._tcp. Use Bonjour Browser to locate all sensors on Windows.

Example using Bonjour Browser:

Step 1: Download Bonjour Browser.

Step 2: The sensor appears under _ouster-lidar._tcp. Click it to view all sensor details.