Using Ouster Edge Processor

Requirements

Ouster Gemini Detect requires optimized edge processing hardware for multi-sensor spatial intelligence. Reach out to Ouster Sales for more details on the available Catalyst GPU.

Note

Catalyst Pro and Catalyst lite have reached EOL and are not available for future sale.

Catalyst-GPU

Highlights

• NVIDIA® Jetson AGX Orin™ up to 275 TOPS

• NVIDIA 8-core ARM Cortex CPU

• 1024-core NVIDIA Ampere™ GPU

• Memory 32GB LPDDR5

• Storage 64GB eMMC and 128G NVMe

• 2 x Ethernet 10/100/1000 Mbps

• 4 x POE+ (IEEE 802.3af/at) 10/100/1000 Mbps. (The total power budget of all 4 POE ports should be less than 60W)

• 4-channel DI, 4-channel DO Digital I/O

• Operating Temperature: -20 ~ +74 °C

• Dimensions 192 (W) x 230 (D) x 87 (H) mm

Catalyst-GPU

The processing required by Ouster Gemini Detect varies depending on how the lidar’s are configured. The table below shows the number of lidar’s supported for each Catalyst GPU when in 1024x10 and 2048x10 lidar modes.

	1024x10	2048x10
Catalyst-GPU[1]	1 - 2	1 - 2

[1]

The Catalyst-GPU can support 1 lidar in 1024x10 mode with an AOD of 140m by 140m. It can also support 2 lidar’s in 1024x10 mode where each lidar has an AOD of 100m by 100m. These specifications do not require any exclusion zones and assume an object count up to 50 objects. To support 2048x10 mode, the Catalyst-GPU can support the same area of interest stated above but requires the use of exclusion zones to limit the amount of points Detect processes.

Connecting Sensors to the Catalyst GPU

Sensors can be connected directly to Catalyst GPU or indirectly via other networking hardware such as a network switch. If other networking hardware is used to connect multiple Ouster sensors to a single Catalyst interface; the bandwidth of the interface and hardware must be carefully considered. We recommend connecting up to 4 lidars on a single Gbps Ethernet link.

Every Catalyst gGPU has a number of built-in Ethernet interfaces in the front of the unit. The following Ethernet interfaces are configured for directly connecting to lidars:

• Catalyst-GPU: LAN 3 and 4

These designated ports will automatically distribute DHCP network addresses if a sensor is configured for DHCP use (default for Ouster sensors).

Ouster sensors will always broadcast an mDNS hostname when directly connected to a Catalyst device. If other networking devices are between the sensor and Catalyst, these devices will need to allow mDNS traffic. The mDNS hostname of Ouster sensors has the form os-XX.local where XX is the sensor serial number.

It is recommended to use the mDNS hostname to communicate with sensors when available as they will never change.

Catalyst-GPU

Port	Address Range
LAN 3	10.125.20.2-10.125.20.22
LAN 4	10.125.21.2-10.125.21.22

Catalyst-GPU

Connecting to the Edge Processor

LAN1 or LAN2 on the Catalyst-GPU is designated for connection to a user’s network. This interface will accept a DHCP address if connected to a network with a DHCP server. This interface will also broadcast an mDNS hostname if connected to a network which supports mDNS traffic. The hostname will be of the form OBC-A{SERIAL_NUMBER[0]}-{SERIAL_NUMBER[1:3]}-{SERIAL_NUMBER[3:10]} where {SERIAL_NUMBER} is a 10 character serial number that can be found on the Catalyst unit. For example, if the serial number is GSAB123456, the hostname would be OBC-AG-SA-B123456.