GigE Vision 3 RDMA FAQ

Upcoming Changes with GigE Vision 3.0 RDMA

May 26, 2026

Understanding LUCID RDMA, RoCEv2, and GVRSP Compatibility

LUCID Vision Labs implemented RDMA (RoCEv2) for our 10GigE and 25GigE machine vision cameras in 2023, before the final GigE Vision 3.0 RDMA streaming protocol was ratified on April 17, 2026. This early implementation helped demonstrate the performance and efficiency benefits of RDMA for high-bandwidth image streaming and contributed to the industry momentum toward standardizing RDMA within GigE Vision.

Through participation in the GigE Vision Technical Committee (TC), LUCID has supported the development of a standardized, interoperable RDMA streaming method for high-bandwidth machine vision cameras.

Today, Triton10, Atlas10, and Atlas25 cameras support high-performance RDMA streaming using LUCID’s existing RDMA implementation. However, this current implementation does not use the final GigE Vision 3.0 RDMA streaming protocol (GVRSP) transport stream. LUCID is updating camera firmware and Arena SDK software to support full GigE Vision 3.0 GVRSP compliance.

Current Status

LUCID currently supports RDMA streaming on all Triton10, Atlas10, and Atlas25 camera models using LUCID’s existing RDMA implementation based on RoCEv2. This earlier implementation predates the finalized GigE Vision 3.0 GVRSP standard and delivers many of the same practical RDMA benefits, but it is not the standardized transport now defined by GigE Vision 3.0.

GVRSP is also based on RoCEv2, but it provides a common, standards-based framework for RDMA streaming across compliant cameras, host software, and supported network hardware.

Question Answer
Does LUCID support RDMA streaming today? Yes, on all Triton10, Atlas10, and Atlas25 camera models.
Is the current LUCID RDMA using GigE Vision 3.0 GVRSP? No. Current firmware uses LUCID’s existing RDMA over RoCEv2 implementation.
Is LUCID moving to GigE Vision 3.0 GVRSP? Yes. Triton10, Atlas10, and Atlas25 cameras are being updated for standards-compliant GVRSP operation.
Will firmware and software updates be required? Yes. Full GVRSP operation requires compatible camera firmware and Arena SDK support.
Is there significant difference between LUCID's RDMA and GVRSP? No
What are the major differences between the two versions? GigE Vision 3.0 can automatically select GVRSP streaming when the camera, SDK, and NIC support it. LUCID uses UDP by default and enables RDMA only when specified by the user. GVRSP uses GenDC for streaming.

Why does LUCID documentation mention GigE Vision 3.0 readiness?

Triton10, Atlas10, and Atlas25 cameras are designed to support the transition to GigE Vision 3.0 RDMA streaming. However, “GigE Vision 3.0 ready” should not be interpreted as meaning that every current firmware version already supports the final GVRSP transport.

A complete GigE Vision 3.0 GVRSP setup requires:

  • 10GigE or 25GigE cameras: Triton10, Atlas10, or Atlas25 models
  • Updated camera firmware with GVRSP support
  • Updated Arena SDK version with GVRSP support
  • A compatible RoCEv2-capable NIC
  • Supported NIC firmware and drivers
  • Correct transport stream configuration

If any part of the system does not support GVRSP, Arena SDK may use another supported stream protocol instead.

What is LUCID doing to become fully GigE Vision 3.0 compliant?

LUCID is updating both camera firmware and Arena SDK to support GigE Vision 3.0 GVRSP on Triton10, Atlas10, and Atlas25 camera models. This work includes firmware updates for supported cameras, Arena SDK updates for GVRSP operation, validation with supported RoCEv2-capable NICs, driver and firmware compatibility testing, internal regression testing, interoperability testing, and compliance testing against the GigE Vision 3.0 standard. The goal is to move these RDMA-capable products to standards-compliant GigE Vision 3.0 operation and remove reliance on legacy RDMA transport modes.

How does LUCID test GigE Vision 3.0 compliance?

LUCID validates GigE Vision 3.0 support through internal engineering tests, supported hardware qualification, and standards-based compliance testing. This includes validation of camera firmware, Arena SDK behavior, supported RoCEv2 NICs, driver versions, streaming modes, and interoperability within the GigE Vision ecosystem.

Compliance testing typically includes several layers:

Testing Area What It Helps Validate
Protocol behavior testing Confirms that the camera and software follow the expected GigE Vision 3.0 protocol behavior for device control, streaming, and communication.
Device discovery and connection testing Verifies that cameras can be reliably discovered, connected, configured, and reconnected by supported host systems and software.
GenICam feature access testing Checks that camera features are exposed correctly through the GenICam interface and can be read, written, and controlled as expected.
Streaming behavior testing Validates image acquisition performance, frame delivery, stream stability, and expected behavior across supported operating conditions.
Transport-layer validation Confirms that the GVRSP transport layer operates correctly, including stream setup, data transfer, recovery behavior, and protocol-specific handling.
Host software compatibility testing Verifies correct operation with Arena SDK, ArenaView, and supported host-side software configurations.
NIC and driver compatibility testing Confirms that supported RoCEv2-capable network cards, firmware versions, and drivers operate correctly with GVRSP streaming.
Interoperability testing with other vendors’ products Helps ensure standards-compliant behavior in multi-vendor environments, including compatibility with other GigE Vision components and software.

LUCID validates GigE Vision 3.0 compliance through formal third-party testing required for certification. This includes compliance testing through the International Vision Standards Meeting, or IVSM, framework, along with PlugFest interoperability testing using other vendors’ hardware and software.

Will legacy LUCID RDMA continue to be supported?

LUCID is transitioning Triton10, Atlas10, and Atlas25 cameras to the standardized GigE Vision 3.0 GVRSP transport. With the upcoming free firmware upgrade for supported Triton10, Atlas10, and Atlas25 cameras, LUCID’s legacy RDMA implementation will be removed from the updated camera firmware. After upgrading, RDMA streaming will use the GigE Vision 3.0 GVRSP implementation instead of the previous LUCID RDMA mode.

Before upgrading production systems, users should confirm that their full imaging pipeline is ready for GigE Vision 3.0 GVRSP, including the camera firmware, Arena SDK version, RoCEv2-capable NIC, NIC firmware and driver, and application stream configuration.

What are the benefits of moving to GigE Vision 3.0 GVRSP?

The main benefit is standardization. LUCID’s current RDMA implementation already provides efficient high-bandwidth streaming. GigE Vision 3.0 GVRSP brings RDMA streaming into the formal GigE Vision standard, which helps support:

  • Standards-based integration
  • Improved interoperability
  • Clearer validation and compliance testing
  • More consistent host software behavior
  • Long-term support across the high-speed Ethernet machine vision ecosystem

When will LUCID support full GigE Vision 3.0 GVRSP?

LUCID is working on updating firmware and Arena SDK support for GigE Vision 3.0 GVRSP on Triton10, Atlas10, and Atlas25 camera models. Updated firmware and Arena SDK is planned for second half of 2026.

How do I enable GigE Vision 3.0 RDMA once I have the correct setup?

Please read our Knowledge Base article: Using GigE Vision RDMA Streaming Protocol in GigE Vision 3.0