• 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 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 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 Setup/Using Multiple RDMA Cameras on a Switch

Using Multiple RDMA Cameras on a Switch

143 views 0 September 26, 2024

Introduction

By properly configuring the bandwidth sharing among multiple RDMA cameras, you can avoid frame drops. This document will guide you on how to effectively use multiple 10G RDMA cameras on a 10G switch.

Prerequisites

  • Software: Arena SDK v1.0.44.11 or newer
  • Firmware: Contact support@thinklucid.com
  • 10G switch, including 10G upstream to host NIC
RDMA 10GigE Cameras using a Network Switch

Equipment Used

  • 2x ATX051S
  • 2x ATX162S
  • LUCID PCIE-10GPOE2-LUCID
  • 4x CAB-MR-5M-A
  • 4x M8P-US1
  • Switches used:
    • TP Link TL-SX1008, or
    • FS S3950-4T125-R with 4x 10Gtek ASF-10G-T

Setup

Scenario 1: 2.5Gbps per camera

CameraATX051S-CCATX051S-MCATX162S-CCATX162S-MC
Device Link Speed1250000000 Bps1250000000 Bps1250000000 Bps1250000000 Bps
Width2448244853205320
Height2048204830323032
Pixel FormatBayerRG8Mono8BayerRG8Mono8
ADC Bit Depth12-bit12-bit12-bit12-bit
Packet Size4144414441444144
Packet Delay80808080
Device Link Throughput Reserve10%10%10%10%
Transport Stream ProtocolRDMARDMARDMARDMA
Device Link Throughput Limit ModeOnOnOnOn
Acquisition Frame Rate EnableTrueTrueTrueTrue
Acquisition Frame Rate59.559.518.518.5

Each camera’s bandwidth is limited by configuring the following settings:

  • Device Link Throughput Limit Mode = On
  • Acquisition Frame Rate Enable = True
  • Acquisition Frame Rate value set up to allow ~2.38Gbps per camera

Because the switch connection to the host PC uses one 10GigE connection, these settings ensure that the four cameras can stream to the switch while efficiently sharing available bandwidth with other cameras.

You can calculate the approximate bandwidth in your current settings with the following formula:

= (width) x (height) x (bytes per pixel) x (frame rate)

=  2448   x   2048   x   1               x  59.5
   width     height      8 bits per pixel   frames per second
                       = 1 byte

= 298303488 Bytes per second
= 298303488 / (1 Byte / 8 bits)
= 298303488 / 0.125
= 2386427904 bits per second (2.3 gigabits per second)

Scenario 2: 5Gbps for 1 camera, 1.6Gbps for 3 cameras

CameraATX051S-CCATX051S-MCATX162S-CCATX162S-MC
Device Link Speed1250000000 Bps1250000000 Bps1250000000 Bps1250000000 Bps
Width2448244853205320
Height2048204830323032
Pixel FormatBayerRG8Mono8BayerRG8Mono8
ADC Bit Depth12-bit12-bit12-bit12-bit
Packet Size4144414441444144
Packet Delay80808080
Device Link Throughput Reserve10%10%10%10%
Transport Stream ProtocolRDMARDMARDMARDMA
Device Link Throughput Limit ModeOnOnOnOn
Acquisition Frame Rate EnableTrueTrueTrueTrue
Acquisition Frame Rate38.512.039.539.5

Remember to divide the bandwidth per camera so that the overall bandwidth delivered to the switch is not over 10G.

Conclusion

Adjusting the total bandwidth for the RDMA-enabled 10GigE cameras to stay within the connection bandwidth between the switch and the host PC allows multiple 10GigE cameras to utilize RDMA data streaming through a switch. This configuration ensures that the cameras stream through the network switch without encountering packet collisions or risking frame drops.

Was this helpful?

Yes  No
Related Articles
  • Projecting a Helios2 3D image to and from a 2D image
  • Focusing a Triton2 EVS Camera
  • Controlling Triton2 EVS camera’s event rate when connected at less than 2.5GigE (Event Rate Control / ERC)
  • Configuring RDMA for Linux
  • Configuring RDMA for Windows
  • Back focal distance in LUCID cameras

Didn't find your answer? Contact Us

  Configuring RDMA for Linux

Controlling Triton2 EVS camera’s event rate when connected at less than 2.5GigE (Event Rate Control / ERC)  

© 2024 LUCID Vision Labs Inc.
Looking to purchase our cameras?
Visit the LUCID Webstore at thinklucid.com
LUCID Support & Help
Welcome to LUCID

We use cookies to facilitate online purchases and analyze our traffic. By clicking "Accept", you consent to our use of cookies.

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}
LUCID Support & Help
Welcome to LUCID

We use cookies to facilitate online purchases and analyze our traffic. By clicking "Accept", you consent to our use of cookies.

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}