Resources

Host Compute & Control Networks

Robot Host Compute, Edge AI & ROS 2 Communication Guide

Prepare host platform, ROS 2, software baseline, sensor lanes, fieldbus, power, thermal and logging inputs for robot compute reviews.

Who should use this

Embodied AI, humanoid, AMR, teleoperation and sensing-heavy robot teams reviewing NVIDIA Jetson Orin or x86 industrial PC host context.

Hardware decision

The guide organizes host, interface, power and software-environment inputs without treating platform selection as a real-time or compatibility guarantee.

Prepare before RFQ

Bring host platform, carrier or expansion context, ROS 2 distribution, JetPack or BSP baseline, customer-supplied DDS / QoS or Linux timing requirements, camera lanes, fieldbus ports, power and thermal limits.

When to use this guide

Start here if the hardware question affects sourcing, files or RFQ review.

  • Sensor lane count, host interfaces or logging bandwidth affects the hardware selection.
  • ROS 2 distribution, JetPack, BSP, DDS / QoS or Linux timing constraints are available as customer-supplied review inputs.
  • Interface maps, driver records, carrier-board documentation or controlled files are needed before integration review.

Key engineering decisions

Host platform and expansion

Identify Jetson Orin NX, Jetson AGX or x86 industrial PC, plus carrier board, expansion board and available port context.

Software environment context

Record ROS 2 distribution, JetPack or BSP baseline and customer-supplied DDS, QoS, RT-PREEMPT or CPU-isolation requirements without implying performance validation.

Sensor and control interfaces

Map camera lane count, GMSL2 / FAKRA, Ethernet, USB, CAN and EtherCAT, including any customer-supplied EtherCAT master context.

Power, thermal and logging

Capture input rail, peak current, TDP, enclosure thermal envelope, storage capacity and sustained logging bandwidth.

RFQ preparation checklist

Include these inputs before asking for quote or document review.

  • Jetson Orin NX / AGX or x86 host
  • Carrier board / expansion-board context
  • ROS 2 distribution
  • JetPack / BSP baseline
  • Customer-supplied DDS / QoS / RT-PREEMPT / CPU-isolation context
  • Camera lane count and interfaces
  • Ethernet / USB / CAN / EtherCAT port needs
  • Power rail, peak current, TDP and storage bandwidth

Engineering file considerations

Document access depends on file type and review context.

  • Driver, SDK, BSP and interface documents should be associated with a named host and peripheral stack.
  • Carrier-board files, complete interface drawings and supplier-sensitive records may require controlled access review.
  • Include RT-PREEMPT, real-time Linux, EtherCAT master or CPU isolation context only when these requirements are customer-supplied review inputs.

Not covered by this guide

NVIDIA certification or carrier-board compatibility guarantee
Hard real-time or deterministic performance guarantee
Algorithm performance or model deployment success guarantee

Ready to attach this guide to a real request?

Use the guide checklist to submit one RFQ with product, file and subsystem context. Controlled access may apply to STEP/STP, native CAD, full drawings and supplier-sensitive records.

Use guide for RFQ preparation