![]() |
DvsenseDriver
1.3.0
The SDK for dvsense products.
|
Language: Chinese
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.
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.
| 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 |
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.
These steps apply to Windows 10/11 environments that provide the Internet Connection Sharing option.
If the Sharing tab is missing, check whether the Internet Connection Sharing (ICS) service and system administration policies allow sharing.
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.
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
In a terminal on the Ubuntu host, list connection names and their associated adapters:
Identify the connection associated with the camera's USB adapter. Replace Camera USB connection name below with its actual name, then run:
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.
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:
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.
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:
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:
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:
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.
After building the sample, run the following in a terminal 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.
| 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.