RCI 050 · System-topology field note

Two exact links. Three preserved transitions.

The TurtleBot3 Waffle Pi profile normalizes 46 official shared-table rows under one configuration column, promotes exactly two rows to exact-model component links, and keeps the Raspberry Pi, camera and LDS revision questions open instead of answering them.

Published 2026-08-185 min readRobot System Index v0.8.21

What is now public

The TurtleBot3 Waffle Pi deep profile selects one responsibility-party surface: the ROBOTIS e-Manual TurtleBot3 parts-list table at a pinned documentation commit. That table publishes 46 rows shared between the Burger and Waffle Pi columns, and the profile normalizes all 46 again under the Waffle Pi quantity column. Rows with a Waffle Pi quantity of zero remain visible as noninstalled alternatives, so 46 is a publication surface, not a claim that 46 different items are fitted to one robot.

On top of the row layer, the profile carries a five-node, four-relation interface topology—Raspberry Pi main compute, OpenCR1.0 control board, the two-actuator drive pair, the USB2LDS-mediated LDS path and the Camera v2.1 path—each relation retaining its unresolved ports, IDs, firmware and cable details with a physical-validation state of none. The same records are served machine-readably in robots.json, the exact component-relation CSV, the interface-relation CSV and the lifecycle-relation CSV.

Only two rows meet the exact-model bar

An exact Robot→Component relation requires a pinned BOM row whose published identity matches a versioned RCI catalog record exactly. For the Waffle Pi column, two rows qualify; three prominent rows deliberately do not.

Published rowWaffle Pi qtyStateBoundary
DYNAMIXEL XM430-W210-TXM430-W210-T catalog record2Exact-model crosswalkThe Burger column publishes zero for this row; serials, IDs, firmware and duty cycle are not established.
OpenCR1.0OpenCR 1.0 catalog record1Exact-model crosswalkBoard name only; physical board revision, IMU population and firmware image are not fixed.
Raspberry Pi1Generic row — no crosswalkOfficial footnotes span Pi 3 Model B, 3 Model B+ and 4 Model B eras; no PCB revision or RAM capacity is bound.
LDS-01 or LDS-021Published alternative — no crosswalkLDS-02 replaced LDS-01 from 2022; no unit-level sensor generation or cutover serial is selected.
Raspberry Pi Camera v2.11Named row — no crosswalkModule PCB revision, serial, lens calibration and tested image mode are not bound.

The lifecycle boundaries are preserved, not resolved

The official footnotes record three transitions that the profile keeps explicit: the Raspberry Pi 3 Model B gave way to the 3 Model B+ as standard from 2019; the Pi 4 Model B has been included as standard since September 2021; and the LDS-02 replaced the LDS-01 from 2022. None of these transitions publishes a unit serial or shipment cutover, so two robots sharing the Waffle Pi product name can carry different compute boards and different lidar generations. The profile also keeps Waffle Pi distinct from the earlier Intel Joule-based Waffle configuration, whose production ended after the Joule reached end of life.

Reading rule

The current specification page names Pi 4 and LDS-02, while the parts row stays generic or alternative. RCI records both statements and selects neither; the exact build boundary of a particular unit must be established separately.

What this is not

  • Not an as-built inventory. No serialised Waffle Pi, kit revision, receipt or unit manifest is bound to the pinned table.
  • Not a compatibility or performance claim. The two exact links prove shared published identity, not installed serials, current supply, continuous torque or safe wiring.
  • Zero RCI physical tests. No Waffle Pi has been inspected, powered, enumerated or traffic-tested by RCI.
  • Open unknowns stay open: the exact Raspberry Pi PCB revision and RAM, the per-unit LDS generation, the camera module revision, OpenCR hardware and firmware state, actuator IDs and cable revisions are all unresolved in the selected source.

Corrections

If a row mapping, quantity, lifecycle date or boundary above is wrong, use the corrections process. Corrections are logged; prior states are not erased.