Link Local IP Network Configuration - PC

Recall that the Zivid SDK looks at Cameras.yml to find cameras, see Zivid Two Network Configuration. There are two options to make a camera available to the Zivid SDK.

1. You can list all the IP addresses that may be assigned in link local mode. The available range is so large that it does not make sense to list them all in the Cameras.yml file.

2. You can list the hostnames assigned to the connected cameras. The hostname is by default zivid-<serial number> (e.g. zivid-2022C0DE). You can also assign a custom hostname when you enable DHCP mode on the camera, see DHCP or Link Local IP Network Configuration - Camera.

In the following guide we will only focus on hostname.

Warning

Before you obtain a link-local IP address for your PC, make sure the camera is configured for link-local IP address, see DHCP or Link Local IP Network Configuration - Camera.

1. Identify network interface name

   WindowsUbuntu (including headless)

   C:\> netsh interface ip show config
   Configuration for interface "Ethernet 2"
      DHCP enabled:                         Yes
      InterfaceMetric:                      5
      DNS servers configured through DHCP:  None
      Register with which suffix:           Primary only
      WINS servers configured through DHCP: None
   
   Configuration for interface "WiFi"
      DHCP enabled:                         Yes
      IP Address:                           192.168.0.4
      Subnet Prefix:                        192.168.0.0/24 (mask 255.255.255.0)
      Default Gateway:                      192.168.0.1
      Gateway Metric:                       0
      InterfaceMetric:                      35
      DNS servers configured through DHCP:  192.168.0.1
      Register with which suffix:           Primary only
      WINS servers configured through DHCP: None
   

2. Obtain link-local IP address

   WindowsUbuntu (including headless)

   Windows has an Automatic Private IP Addressing (APIPA) feature. This feature is enabled by default, and includes an implementation of NetBIOS Naming Service (WINS). In order to trigger this feature the network interface must be configured for DHCP.

   C:\> netsh interface ip set address "Ethernet 2" dhcp
   

   Then make sure that you release any assigned IP addresses, just in case a DHCP server was available at one point.

   C:\> ipconfig /release
   

3. Enable NetBIOS Naming Service service

   WindowsUbuntu (including headless)

   The APIPA feature includes an implementation of NetBIOS Naming Service (WINS), it is enabled by default.

4. Once the network settings are configured, connect the Zivid Two camera and wait more than 15 seconds. Then check if a link-local IP address has been assigned. This step does not depend on the NetBIOS Naming Service service, but it’s a good idea to enable that first.

   WindowsUbuntu (including headless)

   C:\> netsh interface ipv4 show ipaddresses "Ethernet 2"
   
   Address 169.254.208.207 Parameters
   ---------------------------------------------------------
   Interface Luid     : Ethernet 2
   

5. Verify that you can find the camera

   WindowsUbuntu (including headless)

   C:\> ZividNetworkCameraConfigurator info <hostname>
   

   for example, with hostname zivid-two:

   C:\> ZividNetworkCameraConfigurator info zivid-two
   Successfully connected to zivid-two.
   Information:
      Model Name: Zivid Two
      Serial Number: 21514DB3
      MAC Address: 4C4BF98000F1
      Firmware Version: 1.6.0+152047fc
   

Once you have configured both the camera and the PC you can open Zivid Studio and the camera will be found automatically.

Hint

The status LEDs at the back of the camera show the current link capacity.