Static IP Network Configuration - PC

Caution

The correct instructions for network configuration will depend on your SDK version. Choose your SDK version in the top left drop-down.

This guides you through how to set the static IP of the network card that interfaces your camera. You can configure it to match the default configuration of the camera, or to a custom static IP. If you want to configure it to a custom IP outside the subnet range of the camera, you first have to configure the camera to match this.

Single camera

Navigate to:

Control Panel → Network and Internet → Network and Sharing Center → Change adapter settings

../../../_images/adapter-settings-windows.png

Right click on your network connection and chose Properties.

Then, find Internet Protocol Version 4 (TCP/IPv4) and open its Properties.

../../../_images/ipv4-properties-windows.png

Select Use the following IP address and configure your network interface (card/adapter), and choose an IP address that is in the same subnet as the camera. E.g. for a camera with default configuration, this would be:

  • IP address: 172.28.60.2

  • Subnet mask: 255.255.255.0

    ../../../_images/set-ip-address-windows.png

Caution

You might need to bring down and up your network interface after this step. Right click on your network connection, choose Disable, right click again and choose Enable.

Note

Capture time on Windows can occasionally be longer (about 1 second longer than normal) due to ethernet packet loss leading to data re-transmits. You can reduce the occurrence of packet loss by increasing receive and transmit buffers.

Navigate to Device Manager → Network adapters. Right click on your network adapter and press Properties. Under Advanced, increase Receive Buffers and Transmit Buffers.

../../../_images/windows_network_adapter_buffer_size.png

Navigate to your network settings and then click on the cogwheel for the unconnected network interface (card/adapter). This should look approximately like the screenshot below if you are using Ubuntu 20.04.

../../../_images/network-settings-ubuntu.png

Set up the network configuration in the IPv4 tab. Set IPv4 Method to manual, and choose an IP address that is in the same subnet as the camera. E.g. for a camera with default configuration, this would be:

  • Address to: 172.28.60.2

  • Netmask to: 255.255.255.0

    ../../../_images/ipv4-settings-ubuntu.png

Caution

You might need to bring down and up your network interface after this step (set the first toggle button from the first screenshot to on and off).

  1. Find current interfaces and configuration

    $ ip addr
    Example output for ip addr
    zivid@se-zivid-xps15:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
8: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 48:65:ee:1c:12:ba brd ff:ff:ff:ff:ff:ff
    inet 172.21.96.50/24 brd 172.28.60.255 scope global noprefixroute eth0
    valid_lft forever preferred_lft forever
    inet6 fe80::4a65:eeff:fe1c:12ba/64 scope link
    valid_lft forever preferred_lft forever

  2. Current IP address is 172.21.96.50/24. That will not work if the IP address of the camera is not in the same subnet. E.g. for a camera with default configuration, the IP should be in the same subnet as 172.28.60.5.

  3. We will use netplan to update the IP address for this interface. First find your current configuration.

    $ ls /etc/netplan

  4. By default, you should see a .yaml file named something like 01-network-manager-all.yaml. Then list its contents, e.g.:

    $ cat /etc/netplan/01-netcfg.yaml
# Let NetworkManager manage all devices on this system
network:
  version: 2
  renderer: NetworkManager

  5. For safety, copy the file before you update the configuration as follows:

    $ sudo nano /etc/netplan/01-netcfg.yaml

network:
    version: 2
    renderer: networkd
    ethernets:
        eth0:
            dhcp4: no
            addresses:
                - 172.28.60.2/24
            gateway4: 172.28.60.1

  6. Apply changes

    $ sudo netplan apply

  7. Verify that the IP address has been correctly updated

    Example output for ip addr
    zivid@se-zivid-xps15:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
8: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 48:65:ee:1c:12:ba brd ff:ff:ff:ff:ff:ff
    inet 172.28.60.2/24 brd 172.28.60.255 scope global noprefixroute eth0
    valid_lft forever preferred_lft forever
    inet6 fe80::4a65:eeff:fe1c:12ba/64 scope link
    valid_lft forever preferred_lft forever

Once you have configured the static IP of your PC to be in the same subnet as your camera, go back to Discovering and connecting to the camera.

Multiple cameras

The configuration for multiple cameras extends the single camera configuration, so make sure you have understood how to configure for a single camera before going forward.

There are two cases in the multiple camera setup:

  • Multiple cameras connected to multiple network cards

  • Multiple cameras connected to the same network card via a switch

Tip

Two cameras connected to two separate network interface cards can potentially provide higher speed. This is because they will not have to share network bandwidth. There may be a bottleneck on the PC driver/application side, but at least the cameras do not share the same physical network.

In both cases, you also have to do a custom configuration of the cameras. Follow Static IP Network Configuration - Camera to do this.

Network configuration for two Zivid Two cameras connected to two separate network interface cards.

If you use multiple cameras connected to multiple network interface cards then they should not exist on the same subnet. For example, if the subnet mask is 255.255.255.0, at least one bit in the first 24 bits must be different. Using the default configuration as an example, the network card configurations would be:

Network interface card one:

  • Address to: 172.28.60.2

  • Netmask to: 255.255.255.0

Network interface card two:

  • Address to: 172.28.61.2

  • Netmask to: 255.255.255.0

If the camera has the default IP address 172.28.60.5, it must be configured while connected to a network interface card with the IP address 172.28.60.2. Hence, at least one network interface card must first be configured to 172.28.60.2. You may follow the same procedure for each combination of network interface card and camera, but you may also configure all cameras via one network interface card. For the latter case you must remember which IP address you assign to which camera, and move the physical connection to the relevant network interface card after configuration.

Network configuration for two Zivid Two cameras connected via switch to single network interface card.

If you use multiple cameras connected to the same network card via a switch, you have to configure the cameras to different IPs in the same subnet as the network card. Using the default configuration as an example, you would have to configure the cameras as:

Camera one:

  • Address to 172.28.60.5 (already set by default)

Camera two:

  • Address to e.g. 172.28.60.6

This can be repeated for camera three, four, etc.

Once you have configured the static IP of your PC to be in the same subnet as your cameras, go back to Discovering and connecting to the camera.