Version
中文 | English

5.3.7. Net Camera

This section describes how to use Net camera in OrbbecSDK_ROS. Currently, only Femto Mega, Gemini 335Le and Gemini 435Le devices are supported, and other Net devices will be supported in the near future.

You can find example usage code in the example.

5.3.7.1. Femto Mega & Gemini 435Le & Gemini 335Le

Parameter Introduction

Network device settings: enumerate_net_device is set to true, which will automatically enumerate network devices.

If you do not want to automatically enumerate network devices, you can set enumerate_net_device to false, ip_address to the device’s IP address, and port to the default value of 8090.

  • enumerate_net_device: Enable automatically enumerate network devices.

  • ip_address: Set net device’s IP address.

  • port: Set net device’s port. Usually, you can set it to 8090.

Single Net camera

If you need to run Gemini 435Le/Gemini 335Le, replace femto_mega.launch in the run command with gemini435_le.launch or gemini_330_series.launch.

For femto_mega.launch as an example:

Automatically enumerate network devices:

roslaunch orbbec_camera femto_mega.launch enumerate_net_device:=true

Specify IP address to start the device:

Note: ip_address needs to be changed to the IP address of the device, here it is 192.168.1.10.

roslaunch orbbec_camera femto_mega.launch enumerate_net_device:=false ip_address:=192.168.1.10 port:=8090

Multi Net camera

For multi_net_camera.launch as an example:

roslaunch orbbec_camera multi_net_camera.launch

Use list_devices_node to inspect connected devices. Since v2.8.x, this tool also prints firmware version, preset list, preset version, local network interface name for Ethernet devices, and IP source type (NONE, LLA, DHCP, PERSISTENT). If one device fails during enumeration, the tool continues enumerating the remaining devices.

To enable SDK and firmware logs, add --sdk_log_level debug:

rosrun orbbec_camera list_devices_node --sdk_log_level debug

5.3.7.2. IP Configuration Tool

To configure network camera DHCP, persistent IP, Force IP, or DHCP address assignment timeout directly, use ip_config_tool. For complete command examples and parameter descriptions, see Network Configuration Tools.

5.3.7.3. Force IP Function

The Force IP feature allows you to assign a static IP address to a network camera, overriding DHCP settings. This is useful when multiple network cameras are connected, and you need each device to have a fixed IP for reliable communication.

Note: The Force IP configuration will be reset if the device is powered off or restarted. You need to reapply the settings after reboot.

Parameters

  • force_ip_enable - Enable the Force IP function. Default: false

  • force_ip_mac - Target device MAC address when multiple cameras are connected (e.g., "54:14:FD:06:07:DA"). You can use the list_devices_node to find the MAC of each device. Default: ""

  • force_ip_address - Static IP address to assign. Default: 192.168.1.10

  • force_ip_subnet_mask - Subnet mask for the static IP. Default: 255.255.255.0

  • force_ip_gateway - Gateway address for the static IP. Default: 192.168.1.1

Example Usage

  • Enable Force IP for a specific device:

roslaunch orbbec_camera gemini_330_series.launch \
force_ip_enable:=true \
force_ip_mac:=54:14:FD:06:07:DA \
force_ip_address:=192.168.1.50 \
force_ip_subnet_mask:=255.255.255.0 \
force_ip_gateway:=192.168.1.1 \
ip_address:=192.168.1.50 \
port:=8090

Tip: Make sure the camera is connected and its MAC address is correct before enabling Force IP. Use list_devices_node to check the MAC address of all connected cameras.