• Support Home
  • Getting Started
    • Connecting Your Camera
    • 3rd Party Software Getting Started Guides
  • Tech Ref Manuals
    • Arena SDK Documentation
    • HTP003S – Helios2+ ToF 3D
    • HLT003S – Helios2 ToF 3D
    • HLS003S – Helios ToF 3D
    • HLF003S – Helios Flex ToF 3D
    • ATX245S – Atlas10 24.5 MP
    • ATX204S – Atlas10 20.4 MP
    • ATX162S – Atlas10 16.2 MP
    • ATX124S – Atlas10 12.3 MP
    • ATX081S – Atlas10 8.1 MP
    • ATX051S – Atlas10 5.0 MP
    • ATL314S – Atlas 31.4 MP
    • ATL196S – Atlas 19.6 MP
    • ATL168S – Atlas 16.8 MP
    • ATL120S – Atlas 12.3 MP
    • ATL089S – Atlas 8.9 MP
    • ATL071S – Atlas 7.1 MP
    • ATL050S – Atlas 5.0 MP
    • ATL028S – Atlas 2.8 MP
    • ATP200S – Atlas IP67 20 MP
    • ATP120S – Atlas IP67 12.3 MP
    • ATP089S -Atlas IP67 8.9 MP
    • ATP071S – Atlas IP67 7.1 MP
    • ATP028S – Atlas IP67 2.8 MP
    • TRI200S – Triton 20.0 MP
    • TRI120S – Triton 12.3 MP
    • TRI122S – Triton 12.2 MP
    • TRI089S – Triton 8.9 MP
    • TRI071S – Triton 7.1 MP
    • TRI064S – Triton 6.3 MP
    • TRI054S – Triton 5.4 MP
    • TRI050S-P/Q – Triton 5.0 MP Polarized
    • TRI050S – Triton 5.0 MP
    • TRI032S – Triton 3.2 MP
    • TRI028S – Triton 2.8 MP
    • TRI023S – Triton 2.3 MP
    • TRI016S – Triton 1.6 MP
    • TRI005S – Triton 0.5 MP
    • TRI004S – Triton 0.4 MP
    • TRI02KA – Triton 2K Line Scan
    • PHX200S – Phoenix 20.0 MP
    • PHX120S – Phoenix 12.3 MP
    • PHX122S – Phoenix 12.2 MP
    • PHX089S – Phoenix 8.9 MP
    • PHX064S – Phoenix 6.3 MP
    • PHX050S-P/Q – Phoenix 5.0 MP Polarized
    • PHX050S – Phoenix 5.0 MP
    • PHX032S – Phoenix 3.2 MP
    • PHX023S – Phoenix 2.3 MP
    • PHX016S – Phoenix 1.6 MP
    • PHX004S – Phoenix 0.4 MP
  • Application Notes
    • Bandwidth Sharing in Multi-Camera Systems
    • Combine Helios 3D Point Cloud with RGB Color
    • I2C Support on LUCID Cameras
    • Using Helios2 with the Point Cloud Library for Dimensioning
    • Using GPIO on LUCID Cameras
    • Using PTP & Scheduled Action Commands
    • Helios2 And Triton Synchronization
    • Product Change Notifications (PCN)
  • Knowledge Base
  • Contact Support
  • Log In
  • Support Home
  • Getting Started
    • Connecting Your Camera
    • 3rd Party Software Getting Started Guides
  • Tech Ref Manuals
    • Arena SDK Documentation
    • HTP003S – Helios2+ ToF 3D
    • HLT003S – Helios2 ToF 3D
    • HLS003S – Helios ToF 3D
    • HLF003S – Helios Flex ToF 3D
    • ATX245S – Atlas10 24.5 MP
    • ATX204S – Atlas10 20.4 MP
    • ATX162S – Atlas10 16.2 MP
    • ATX124S – Atlas10 12.3 MP
    • ATX081S – Atlas10 8.1 MP
    • ATX051S – Atlas10 5.0 MP
    • ATL314S – Atlas 31.4 MP
    • ATL196S – Atlas 19.6 MP
    • ATL168S – Atlas 16.8 MP
    • ATL120S – Atlas 12.3 MP
    • ATL089S – Atlas 8.9 MP
    • ATL071S – Atlas 7.1 MP
    • ATL050S – Atlas 5.0 MP
    • ATL028S – Atlas 2.8 MP
    • ATP200S – Atlas IP67 20 MP
    • ATP120S – Atlas IP67 12.3 MP
    • ATP089S -Atlas IP67 8.9 MP
    • ATP071S – Atlas IP67 7.1 MP
    • ATP028S – Atlas IP67 2.8 MP
    • TRI200S – Triton 20.0 MP
    • TRI120S – Triton 12.3 MP
    • TRI122S – Triton 12.2 MP
    • TRI089S – Triton 8.9 MP
    • TRI071S – Triton 7.1 MP
    • TRI064S – Triton 6.3 MP
    • TRI054S – Triton 5.4 MP
    • TRI050S-P/Q – Triton 5.0 MP Polarized
    • TRI050S – Triton 5.0 MP
    • TRI032S – Triton 3.2 MP
    • TRI028S – Triton 2.8 MP
    • TRI023S – Triton 2.3 MP
    • TRI016S – Triton 1.6 MP
    • TRI005S – Triton 0.5 MP
    • TRI004S – Triton 0.4 MP
    • TRI02KA – Triton 2K Line Scan
    • PHX200S – Phoenix 20.0 MP
    • PHX120S – Phoenix 12.3 MP
    • PHX122S – Phoenix 12.2 MP
    • PHX089S – Phoenix 8.9 MP
    • PHX064S – Phoenix 6.3 MP
    • PHX050S-P/Q – Phoenix 5.0 MP Polarized
    • PHX050S – Phoenix 5.0 MP
    • PHX032S – Phoenix 3.2 MP
    • PHX023S – Phoenix 2.3 MP
    • PHX016S – Phoenix 1.6 MP
    • PHX004S – Phoenix 0.4 MP
  • Application Notes
    • Bandwidth Sharing in Multi-Camera Systems
    • Combine Helios 3D Point Cloud with RGB Color
    • I2C Support on LUCID Cameras
    • Using Helios2 with the Point Cloud Library for Dimensioning
    • Using GPIO on LUCID Cameras
    • Using PTP & Scheduled Action Commands
    • Helios2 And Triton Synchronization
    • Product Change Notifications (PCN)
  • Knowledge Base
  • Contact Support
  • Log In
home/Knowledge Base/Camera Features/Using GigE Vision RDMA Streaming Protocol in GigE Vision 3.0

Using GigE Vision RDMA Streaming Protocol in GigE Vision 3.0

22 views 0 November 7, 2025

Introduction

GigE Vision 3.0 introduces the GigE Vision RDMA Streaming Protocol (GVRSP). RDMA allows the camera to stream data directly to the computer’s memory, bypassing the CPU and operating system. This eliminates the CPU overhead required to manage data transmission and frees up resources for other processing tasks. The GigE Vision 3.0 RDMA implementation utilizes the RoCEv2 standard.

GVRSP must be enabled to utilize RDMA data transfer. When both the camera and host system support GVRSP, it is automatically enabled, no user action is required. LUCID also provides a manual option to activate GVRSP.

This knowledge base article explains how to enable and verify GVRSP operation.

Using GVRSP

Prerequisites

GVRSP is available on LUCID’s 10G or higher cameras.

  • Arena SDK:
    • Windows 10 64-bit or 11 64-bit: v1.065.5 or higher
    • Linux x64: v0.1.116 or higher
  • Supported Network Interface Cards (Host Channel Adapters):
    • PCIE-10GPOE4-LUCID2
    • LUCID PCIE-10GPOE2-LUCID
    • PCIE-10GETH2-BC
    • PCIE-25GETH2-BC
  • NIC Driver:
    • v234
  • NIC Firmware:
    • v234
  • NIC Network Direct Service Provider Interface (for Windows):
    • v234
  • LUCID Cameras:
    • Atlas10 firmware v1.48.0.0 or higher
    • Triton10 firmware v1.16.0.0 or higher
    • Atlas25 supported out of box

The Arena SDK installation process installs NIC drivers and updates your NIC if it sees one of the above NICs on the system. You can also use the LucidNicTools software package to determine if your NIC is compatible with GVRSP.

You can check if your LUCID camera is using GigE Vision 3.0 by looking at the Device TL Version Major node. If this node reports 3, you have a GigE Vision 3.0 device.

Enabling GVRSP

Arena SDK uses the TLDevice node DeviceStreamProtocol to determine the transmission protocol used. The following options are available for DeviceStreamProtocol:

  • Automatic – This is the default selection. Arena SDK will look for GVRSP support on the camera and on the host and will use GVRSP if supported. If GVRSP support is not found on the camera or the host, Arena SDK will use GVSP (UDP).
  • GVRSP – Arena SDK will use GVRSP (RDMA). If GVRSP is not supported, an error message will be presented.
  • GVSP – Arena SDK will use GVSP (UDP).
  • Legacy – Arena SDK will use legacy RDMA or legacy TCP.

Setting the Device Stream Protocol node

The following shows how to use GVRSP only.

C++:

Arena::SetNodeValue<GenICam::gcstring>(pDevice->GetTLDeviceNodeMap(), "DeviceStreamProtocol", "GVRSP");

C#:

var deviceStreamProtocolNode = (ArenaNET.IEnumeration)device.TLDeviceNodeMap.GetNode("DeviceStreamProtocol");
deviceStreamProtocolNode.Value = "GVRSP";

C:

err = acDeviceGetTLStreamNodeMap(hDevice, &hTLStreamNodeMap);
err = acNodeMapSetStringValue(hTLStreamNodeMap, "DeviceStreamProtocol", "GVRSP");

Python:

device.tl_device_nodemap['DeviceStreamProtocol'].value = 'GVRSP'

In GVRSP mode, the following nodes become invisible:

  • GevSCPSPacketSize
  • GevSCPD

There is no need to turn on Arena SDK packet resend in GVRSP mode. Packet resend is built into the transmission protocol.

Legacy Transmission Protocols

Some cameras will still be able to use LUCID’s Legacy RDMA or Legacy TCP transmission protocols. See the table below for supported transmission protocols on GVRSP-enabled firmware:

Camera FamilyGVRSP (RDMA)GVSP (UDP)Legacy RDMALegacy TCP
Atlas10✅✅✅✅
Triton10✅✅
Atlas25✅✅

The following shows how to use Legacy RDMA on a GVRSP-enabled Atlas10.

C++:

Arena::SetNodeValue<GenICam::gcstring>(pDevice->GetTLDeviceNodeMap(), "DeviceStreamProtocol", "Legacy");
Arena::SetNodeValue<GenICam::gcstring>(pDevice->GetNodeMap(), "TransportStreamProtocol", "RDMA");

C#:

var deviceStreamProtocolNode = (ArenaNET.IEnumeration)device.TLDeviceNodeMap.GetNode("DeviceStreamProtocol");
deviceStreamProtocolNode.Value = "Legacy";
var transportStreamProtocolNode = (ArenaNET.IEnumeration)device.NodeMap.GetNode("TransportStreamProtocol");
transportStreamProtocolNode.Value = "RDMA";

C:

err = acDeviceGetTLStreamNodeMap(hDevice, &hTLStreamNodeMap);
err = acNodeMapSetStringValue(hTLStreamNodeMap, "DeviceStreamProtocol", "Legacy");
err = acDeviceGetNodeMap(hDevice, &hNodeMap);
err = acNodeMapSetStringValue(hNodeMap, "TransportStreamProtocol", "RDMA");

Python:

device.tl_device_nodemap['DeviceStreamProtocol'].value = 'Legacy'
device.nodemap['TransportStreamProtocol'].value = 'RDMA'

Was this helpful?

Yes  No
Related Articles
  • Pixel Formats – 3D
  • Pixel Formats – Line Scan
  • Pixel Formats – Area Scan
  • Using QOI with LUCID Cameras
  • Using Multiple Helios Cameras Simultaneously
  • Shading Correction Control (Atlas10)

Didn't find your answer? Contact Us

  Pixel Formats – 3D

© 2024 LUCID Vision Labs Inc.
Looking to purchase our cameras?
Visit the LUCID Webstore at thinklucid.com
Manage Consent

We use cookies to process e-commerce purchases securely and to understand how our site is used. Your privacy matters — click ‘Accept’ to continue.

Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
View preferences
  • {title}
  • {title}
  • {title}
Manage Consent
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
View preferences
  • {title}
  • {title}
  • {title}