Mapped subcategories
- Robot main-compute platforms
- CPU, GPU, NPU and SoC modules
- Edge-AI computers
- Real-time controllers
- Safety controllers
- Motion-control cards
- Carrier boards and storage
- High-speed networking
Component layer C · Priority 03
Main computers, accelerators and real-time controllers—compared beyond headline TOPS.
These records test whether the same claim-level schema can preserve meaningful differences across unlike products.
A high-end Jetson module whose headline TOPS value is an INT8 sparse throughput claim and must be paired with its power mode and workload precision.
A general-purpose embedded compute module with unusually long published production availability and flexible carrier-board integration.
A robotics platform emphasizing heterogeneous imaging and AI pipelines rather than a directly comparable single TOPS headline.
A complete industrial computer that adds wide-input power, rugged I/O and expansion around an AGX Orin module; module TOPS must not be mistaken for whole-system performance.
A rugged complete computer offered with 32 GB and 64 GB AGX Orin variants, making ordered configuration part of every comparison.
An industrial Jetson system whose robotics value comes from exposed CAN, serial, Ethernet and digital I/O in addition to module AI throughput.
An industrial SoM whose real-time core, CAN-FD and maintained OS ecosystem may matter more to a robot controller than a large TOPS headline.
A compact Jetson module whose current Super headline must be separated into sparse and dense INT8 throughput and tied to software and power mode.
A widely deployed embedded module with a public production commitment and explicit standard versus extended temperature variants.
A low-power industrial SoM that exposes real-time and CAN-FD integration features rather than a neural-accelerator headline.
A compact Orin NX system whose system-level ports and input range are distinct from the underlying Jetson module capabilities.
An entry Orin module whose Super-mode figures require JetPack 6.2 and a compatible power and thermal configuration.
A legacy-generation robotics development platform retained as a distinct record from the newer RB3 Gen 2 family.
A rugged Orin NX system family whose memory, CPU and optional GMSL configuration depend on ordering code.
A camera-dense AGX Orin system with twelve PoE ports, dual CAN FD and a constrained 19–24 V input range.
A compact Orin NX system with dual CAN and preinstalled NVMe storage; its published TOPS figure predates later Super-mode tables.
An i.MX95 Verdin configuration whose public revision table exposes active EOL and replacement churn rather than hiding it.
The revision-bounded Raspberry Pi 5 identity published by OpenAMR. Raspberry Pi’s current product page supports family-level specifications; it does not by itself provide a Rev 1.1 change manifest or prove the selected OpenAMR unit.
The exact real-time controller named by the OpenAMR responsibility-party component table, separated from the processor identity and from any flashed firmware or carrier wiring.
The family-level product identity used by LeKiwi, TrotBot and optional AlohaMini configurations. It is deliberately separate from the OpenAMR-specific Rev 1.1 record and does not infer a board revision from a RAM label.
The exact tray ordering code, spec code and stepping are attached to the processor record. Processor specifications do not identify a carrier board, BIOS, memory population, cooling system or robot workload.
The commercial-grade part number is separated from the industrial variant and from Kria starter kits. Product-page architecture claims do not prove a complete robot carrier, thermal design, firmware image or sustained workload.
The exact -0100 order suffix is retained: no operating system and no TwinCAT are included. CPU-module specifications do not establish a complete real-time robot controller, I/O terminal set, licenses or deterministic performance.
First deliverable
Publication gate: a record needs a stable model identity, at least one traceable first-party source, useful integration fields, a last-verified date and visible evidence labels.
A sample of the cross-source ledger. The full directory includes use and republication guidance.