DvsenseDriver  1.3.0
The SDK for dvsense products.
Loading...
Searching...
No Matches
DVSyncPro (Fusion Pro) Quick Start Guide

Language: Chinese

1. Meet Fusion Pro

When connected to a host computer over USB, Fusion Pro works like a standard fusion camera. Use the supplied host software or SDK to acquire, view, and process fusion data. Everyday acquisition works the same way as with a standard DVSync camera; you do not need to access the camera's internal desktop first.

Pro also supports development inside the camera. Use a browser to access its web desktop, where you can write, debug, and run algorithms and applications for local data processing.

2. Getting started over USB

  1. Install DVSense Insight or the DVSense SDK on the host computer.
  2. Connect the camera to the host using a USB cable that supports data transfer. Wait for the camera to start and for device detection to complete.
  3. Select the camera in the host software and start acquisition to view RGB images, DVS events, and the fusion display. For application development, refer to the SDK's fusion camera examples.

The camera also provides a network interface over USB, which appears as a USB network adapter on the host. Use this adapter to access the camera's internal system and, after enabling Internet connection sharing, to provide Internet access to the camera.

Accessing the internal desktop only requires a working network connection between the host and the camera. Enable Internet connection sharing when the camera needs to download dependencies, update software, or access external services.

3. Accessing the internal desktop

Initial network and login settings

Item Initial value
Camera USB network IP 192.168.137.2
Recommended host USB adapter IP 192.168.137.1
Subnet mask 255.255.255.0 (/24)
Camera system username dvsyncpro
Camera system password dvsense
Web desktop connection password dvsense
Web desktop address http://192.168.137.2:6080/vnc.html

Connection steps

  1. Identify the USB network adapter that appears when you connect the camera. Disconnecting and reconnecting the camera can help identify it in the adapter list.
  2. If Internet connection sharing is not enabled, manually set this host USB adapter's IPv4 address to 192.168.137.1 and its subnet mask to 255.255.255.0. Leave the default gateway and DNS fields empty on this adapter; the host continues to use its existing Wi-Fi or wired connection for Internet access.
  3. Run ping 192.168.137.2 in a host terminal to check camera reachability.
  4. Open the camera web desktop in the host browser, click Connect, and enter the desktop connection password dvsense. The current desktop runs as dvsyncpro; enter dvsense if a system operation asks for a password.
  5. Once connected, open a terminal or editor to write, debug, and run algorithms and applications inside the camera.

The web desktop service starts automatically when the camera boots. No manual start is required.

The address uses HTTP, port 6080, and the page path /vnc.html. In the current configuration, the desktop service starts once the camera's USB network interface is ready. Refresh the page after a short wait if the camera is still starting. A terminal window appears on the desktop; closing it does not close the desktop. You can open another terminal from the desktop's right-click menu.

4. Enabling Internet connection sharing on Windows

These steps apply to Windows 10/11 environments that provide the Internet Connection Sharing option.

  1. Confirm that the host can access the Internet through Wi-Fi or a wired connection, then connect the camera over USB.
  2. Press Win + R, enter ncpa.cpl, and press Enter to open Network Connections.
  3. Find the adapter currently connected to the Internet, such as Wi-Fi. Right-click it, open Properties, and select the Sharing tab.
  4. Select Allow other network users to connect through this computer's Internet connection.
  5. Under Home networking connection, select the camera's USB network adapter and click OK. The Internet-connected adapter is the sharing source, and the camera USB adapter receives the shared connection. Microsoft connection sharing instructions
  6. Check the camera USB adapter's IPv4 configuration: its address should be 192.168.137.1 and its subnet mask 255.255.255.0. Windows sharing typically uses this address, but verify the actual configuration. If it differs, put the camera and sharing adapter on the same subnet and adjust the camera's gateway accordingly.
  7. Check the gateway and DNS settings inside the camera and verify Internet access as described in Section 6.

If the Sharing tab is missing, check whether the Internet Connection Sharing (ICS) service and system administration policies allow sharing.

5. Enabling Internet connection sharing on Ubuntu

The following example uses Ubuntu Desktop with NetworkManager. Confirm that the host can access the Internet, then enable sharing for the connection associated with the camera's USB network adapter.

Using the graphical interface

  1. Open Settings → Network, find the camera's USB wired connection, and open its settings.
  2. On the IPv4 page, select Shared to other computers.
  3. If the interface lets you specify a sharing address, set it to 192.168.137.1 with subnet mask 255.255.255.0, and leave the gateway empty. Save and reactivate the connection.
  4. If the interface does not let you enter a sharing address, use the commands below.

Check the sharing subnet: When no sharing address is specified, NetworkManager typically chooses 10.42.x.0/24, which differs from the camera's initial subnet. This guide uses 192.168.137.1/24 so the camera can retain its initial IP. NetworkManager IPv4 documentation

Using the command line

In a terminal on the Ubuntu host, list connection names and their associated adapters:

nmcli -f NAME,DEVICE,TYPE connection show --active

Identify the connection associated with the camera's USB adapter. Replace Camera USB connection name below with its actual name, then run:

sudo nmcli connection modify "Camera USB connection name" \
ipv4.method shared \
ipv4.addresses 192.168.137.1/24 \
ipv4.gateway "" \
ipv4.dns "" \
ipv4.never-default yes
sudo nmcli connection up "Camera USB connection name"

Reactivating the connection may briefly interrupt the web desktop. Reconnect once it is restored. NetworkManager manages forwarding and the related network services in shared mode; you do not need to configure forwarding rules manually.

6. Camera network settings and verification

After enabling sharing on the host, the camera's internal USB network connection also needs the correct default gateway and DNS settings. Open the camera web desktop and check the USB connection's IPv4 settings. If they are already correct, no changes are necessary.

Camera setting Recommended value
IP address 192.168.137.2
Subnet mask 255.255.255.0
Default gateway 192.168.137.1 (the host USB adapter address)
DNS A DNS server accessible on your network, such as 223.5.5.5; Ubuntu sharing can also use 192.168.137.1

Saving the network settings may briefly interrupt the desktop connection. Reconnect after a short wait.

Run these commands in a terminal inside the camera:

ping -c 3 192.168.137.1
ping -c 3 223.5.5.5
getent hosts www.dvsense.com
  • Reaching 192.168.137.1 confirms USB network connectivity between the camera and host.
  • Reaching an external IP confirms Internet forwarding. If your network blocks ping, try opening a website in a browser to verify access.
  • Resolving a website's domain name and opening its page confirms working DNS and Internet access.

7. Viewing Sync Viewer fusion results over WebRTC

The camera provides the dvsense_dvsyncpro_webrtc_viewer sample, which sends synchronized RGB images with DVS events overlaid to the host browser through WebRTC. It uses the same synchronization grouping approach as the desktop Sync Viewer and lets you observe fusion results directly.

The default precompiled Sample package does not include this WebRTC executable. Compile the sample supplied in the development package manually. Install the SDK deb package through apt. It provides precompiled libraries, public headers, CMake configuration, and sample application source code; it does not provide the SDK's internal implementation source. Run the following steps in an Ubuntu terminal inside the camera. The sample links to the installed SDK libraries.

Installing build and runtime dependencies

Enable Internet connection sharing as described above so the camera can access package repositories. Confirm that the DVSense apt repository is configured for the camera's Ubuntu version and ARM64 architecture. Install the SDK development package and dependencies:

sudo apt update
sudo apt install libdvsensedriver-dev build-essential cmake pkg-config libopencv-dev \
libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev \
libgstreamer-plugins-bad1.0-dev libsoup-3.0-dev libjson-glib-dev \
gstreamer1.0-plugins-base gstreamer1.0-plugins-good \
gstreamer1.0-plugins-bad gstreamer1.0-nice

Building the sample against the installed SDK

The current deb development package installs sample source code under /usr/share/DvsenseDriver/Samples. The WebRTC sample is in /usr/share/DvsenseDriver/Samples/DvsenseDVSyncproWebRtcViewer. SDK CMake configuration files are in /usr/share/cmake/DvsenseDriver, and shared libraries are in /usr/lib. Copy the sample to your user directory and build it:

cp -r /usr/share/DvsenseDriver/Samples/DvsenseDVSyncproWebRtcViewer \
~/dvsyncpro-webrtc-sample
cmake -S ~/dvsyncpro-webrtc-sample -B ~/dvsyncpro-webrtc-sample/build \
-DCMAKE_BUILD_TYPE=Release \
-DDvsenseDriver_DIR=/usr/share/cmake/DvsenseDriver
cmake --build ~/dvsyncpro-webrtc-sample/build \
--target dvsense_dvsyncpro_webrtc_viewer -j2

This links to the precompiled SDK libraries supplied by the deb package and builds only the WebRTC sample application. You do not need to install the dvsense-driver-samples precompiled sample package.

If the sample directory is missing, use dpkg -L libdvsensedriver-dev to list installed files and update the development package with sudo apt install --only-upgrade libdvsensedriver-dev. If the directory is still missing after updating, contact technical support for a development package containing this sample.

Samples in older development packages may lack standalone CMake configuration. If the copied CMakeLists.txt does not begin with the following configuration, add it before the existing contents:

cmake_minimum_required(VERSION 3.16)
project(DvsenseDVSyncproWebRtcViewer LANGUAGES CXX)
find_package(DvsenseDriver COMPONENTS Driver REQUIRED)

If CMake cannot find the SDK, confirm that the development package is installed. Run dpkg -L libdvsensedriver-dev to find DvsenseDriverConfig.cmake, and point DvsenseDriver_DIR to the directory containing it. If GStreamer, libsoup, or json-glib is missing, check that the dependencies above installed successfully.

Starting and viewing

  1. Open the camera desktop using the noVNC address in Section 3 and open a terminal. Stop other acquisition applications using the internal camera before starting this sample.
  2. After building the sample, run the following in a terminal inside the camera:

    ~/dvsyncpro-webrtc-sample/build/dvsense_dvsyncpro_webrtc_viewer 8080
  3. Leave the application running and open a new tab in the host browser at the WebRTC fusion preview: http://192.168.137.2:8080/. The page connects automatically; no noVNC desktop password is required.
  4. Move an object or wave your hand in front of the camera to observe red and blue event points overlaid on the RGB image. The APS, Events, and Triggers values at the top show cumulative counts of received RGB frames, DVS events, and internal RGB/DVS synchronization signals, respectively.
  5. When finished, press Ctrl + C in the camera terminal that started the application. Closing the browser page only disconnects the viewer; the application keeps running inside the camera.

WebRTC preview only requires a working USB network connection; Internet connection sharing is not required. The noVNC desktop uses port 6080, while the WebRTC sample uses port 8080. The desktop service starts at boot, but you must start the WebRTC sample using the steps above. The application's first argument can specify another port. For example, using 8081 changes the viewing address to http://192.168.137.2:8081/.

If startup reports a missing SDK shared library, run sudo ldconfig to update the system library cache, then use ldd ~/dvsyncpro-webrtc-sample/build/dvsense_dvsyncpro_webrtc_viewer to check for not found entries. Verify that the SDK development package and its dependencies are fully installed.

Troubleshooting viewing

  • Page does not open: Check that the application is still running, inspect startup errors, and confirm that the URL port matches the startup argument.
  • Page opens but connection fails: Close other viewing tabs and refresh. Check browser WebRTC support and whether the host firewall permits UDP communication used by WebRTC.
  • Only status text appears, or the image does not update: Inspect the camera terminal output and the APS, Events, and Triggers counts. Check whether another application is using the internal camera.

8. Common issues

Symptom Check first
Host cannot detect the camera or USB network adapter Data-capable USB cable, completed camera startup, and correct driver installation
Cannot reach 192.168.137.2 Host USB adapter is set to 192.168.137.1/24; other adapters or VPNs using 192.168.137.0/24 may cause routing conflicts
Camera IP is reachable, but the web desktop does not open Correct URL protocol, port, and path; desktop service has completed startup
Desktop works, but camera has no Internet access Sharing targets the camera USB adapter; camera gateway points to the host USB address; host has Internet access
External IPs are reachable, but domain names do not work Camera DNS configuration and DNS server reachability

For SDK acquisition and data processing, refer to the fusion camera tutorial and the 1.3.0 API migration guide.