Public BOM audited. This is a source-bound system evidence record, not an independent rebuild.
Quadruped · TrotBot project / Vipin Mohan
TrotBot ROS 2 quadruped hardware boundary
Markdown list · commit-addressable.
No complete rebuild evidence package found.
The robot name is not the version boundary.
RCI preserves the exact source surface and revision conditions instead of applying one prototype or current product page to every unit.
Platform boundary
TrotBot ROS 2 quadruped hardware boundary
README hardware specification at commit 4ac874ef86ed99e9621df685ba23103aeebc0d9c.
Version state
Addressable source snapshot
Commit-addressable documentation without numbered hardware release or unit manifest.
Lifecycle boundary
Changes remain attached to the source.
Servo selection and leg geometry are configurable; RCI does not turn recommendations into one exact actuator SKU.
Responsibility party
TrotBot project / Vipin Mohan
RCI maps the named public responsibility party; inclusion does not imply endorsement, partnership or unit-level verification.
No structured lifecycle relation selected yet.
Replacement, upgrade, EOL and regional procurement signals remain separate from current availability and as-built identity.
No positive lifecycle claim.
Absence here means the selected source set does not yet support one, not that the platform has no revisions or supply risk.
Strongest supported conclusion
Responsibility-party compute, PWM control, 12-servo topology, power domains, gamepad, printed frame and storage requirements.
Largest rebuild gap: Several requirements are generic classes and the repository does not bind exact procurement identities or one as-built robot.
Editorial boundary: The profile records published requirements, not the claimed performance figures as RCI measurements.
Twelve gates separate a parts list from a rebuild package.
Partial means a source contains useful material but does not close the exact revision, quantity, part identity or unit-level boundary.
| Evidence dimension | State | What the state means here |
|---|---|---|
| Exact platform revision | Published | The selected responsibility-party surface publishes this dimension inside the recorded boundary. |
| Versioned BOM snapshot | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| Line-item quantities | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| Manufacturer part numbers | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| Supplier links | Not published | The selected sources do not publish this evidence dimension. |
| Custom-part production files | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| Electrical interconnect definition | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| Software / firmware binding | Partial | Useful information exists, but exactness, completeness or version binding remains incomplete. |
| License boundary | Published | The selected responsibility-party surface publishes this dimension inside the recorded boundary. |
| Change, EOL and substitution history | Published | The selected responsibility-party surface publishes this dimension inside the recorded boundary. |
| Unit-level as-built manifest | Not published | The selected sources do not publish this evidence dimension. |
| Independent rebuild evidence | Not published | The selected sources do not publish this evidence dimension. |
Complete Bill of Materials section — top-level hardware requirement groups
The count below preserves the responsibility party's publication structure; it is not silently flattened into unique purchasable components.
Selected count
8 rows / list items
Eight RCI-normalized top-level requirement records; nested specifications remain attributes rather than extra procured line items.
Format
Markdown list
RCI did not treat the publication format as a normalized database table.
Next evidence gate
Normalize without inventing.
Resolve exact part identity, quantity scope, placement, revision and substitution state while retaining nested assemblies, alternatives and generic groups as explicit boundaries.
As-built state
Not published
A public list does not establish what one serialised unit actually contained.
No manufacturer identity is safely linked from the selected rows.
These are responsibility-party BOM mentions, not partnership, endorsement, verified supply or exact-component equivalence.
Generic or unregistered identities remain unlinked.
RCI will add a relationship only after the source publishes a manufacturer identity that maps unambiguously to the directory.
BOM → exact component
Raspberry Pi 5
The pinned TrotBot hardware requirements name one Raspberry Pi 5 with 8 GB RAM as the main compute board. RCI maps the family identity while leaving the PCB revision unknown.
Published quantity: 1. One main compute board is implied by the singular requirement; no serial, PCB revision, image or unit-level as-built manifest is published.
Boundary: The relation does not prove installation in a physical TrotBot, power/cooling sufficiency, software compatibility, endorsement or RCI validation.
6 bounded nodes and 6 source-supported interface relations.
RCI publishes a connection only when the selected responsibility-party source explicitly supports the endpoints or architecture. A BOM co-occurrence, component capability or engineering convention is not enough.
external-host node
Nintendo Pro Controller command source
Responsibility-party recommended Bluetooth gamepad; Xbox and PlayStation controllers remain alternatives rather than simultaneous requirements.
Identity boundary: Controller revision, Bluetooth identity, pairing state, input mapping and observed link quality are not frozen.
Source rows: trotbot-hardware-item-07
compute node
Raspberry Pi 5 (8 GB) main compute
Responsibility-party recommended Raspberry Pi 5 8 GB control host.
Identity boundary: PCB revision, serial, storage image, ROS 2/CHAMP checkout, kernel and observed interfaces are not fixed.
Source rows: trotbot-hardware-item-01
control node
PCA9685 16-channel PWM controller
One PCA9685-class board at published I²C address 0x40, with twelve of sixteen channels assigned to servos.
Identity boundary: Board vendor/revision, oscillator calibration, pull-ups, firmware/library version and physical channel map are not frozen.
Source rows: trotbot-hardware-item-03
actuation node
Twelve configurable joint servos
Three servos per leg across four legs; responsibility-party source gives 4.8–7.2 V and 6 V nominal while leaving exact models configurable.
Identity boundary: Exact models, serials, calibration, horn geometry, channel assignment, current draw, wear and allowable duty cycle are not fixed.
Source rows: trotbot-hardware-item-04
power node
5 V / 5 A Raspberry Pi supply domain
One 5 V / 5 A USB-C supply requirement for Raspberry Pi 5.
Identity boundary: Supply SKU, cable, USB-C negotiation, protection, grounding and measured voltage under compute load are not fixed.
Source rows: trotbot-hardware-item-05
power node
Separate 6 V high-current servo domain
Responsibility-party 6 V servo rail, published as separate from Pi power with common ground.
Identity boundary: Orderable regulator/supply, 8–10 A peak claim provenance, fuse, emergency-stop implementation, wire gauge and measured transients are not frozen.
Source rows: trotbot-hardware-item-06
| From → to | Relation | Published support | Still unresolved |
|---|---|---|---|
| Nintendo Pro Controller command source → Raspberry Pi 5 (8 GB) main computebidirectional | data-controlBluetooth 5.0 gamepad link to Raspberry Pi 5 | The pinned README recommends Nintendo Pro Controller input and publishes Bluetooth wireless connection to Pi 5 while listing Xbox/PlayStation as alternatives.mvipin/trotbot commit 4ac874ef86ed99e9621df685ba23103aeebc0d9c | Controller revision, pairing, radio identity, mapping, authentication, latency and packet-loss behavior are not frozen. RCI has not paired or captured this link.Physical validation: none. |
| Raspberry Pi 5 (8 GB) main compute → PCA9685 16-channel PWM controllerbidirectional | data-controlI²C control at address 0x40 | The pinned hardware specification names PCA9685 as the Pi-controlled servo interface, publishes I²C address 0x40 and instructs detection on bus 1.mvipin/trotbot commit 4ac874ef86ed99e9621df685ba23103aeebc0d9c | Board vendor, I²C pins/connector, pull-ups, bus speed, oscillator calibration, library checkout and observed address scan are not frozen. RCI has not run i2cdetect.Physical validation: none. |
| PCA9685 16-channel PWM controller → Twelve configurable joint servossource-to-target | data-controlTwelve of sixteen PWM channels; source calls 250 Hz optimal | The pinned README publishes twelve servos, sixteen PCA9685 channels with twelve used, 40–1000 Hz capability and 250 Hz as the project optimum.mvipin/trotbot commit 4ac874ef86ed99e9621df685ba23103aeebc0d9c | Exact servo models, channel-to-joint map, pulse limits, calibration artifacts, observed frequency/jitter and electrical buffering are not frozen. RCI has not probed PWM or moved any joint.Physical validation: none. |
| 5 V / 5 A Raspberry Pi supply domain → Raspberry Pi 5 (8 GB) main computesource-to-target | power5 V / 5 A USB-C compute supply | The responsibility-party BOM and hardware section publish a 5 V / 5 A USB-C supply for Raspberry Pi 5.mvipin/trotbot commit 4ac874ef86ed99e9621df685ba23103aeebc0d9c | Supply SKU, cable, USB-C negotiation, ripple, transient margin, grounding and loaded voltage are not frozen. RCI has not instrumented this rail.Physical validation: none. |
| Separate 6 V high-current servo domain → Twelve configurable joint servossource-to-target | powerSeparate 6 V high-current actuator supply | The pinned source publishes 4.8–7.2 V servo operation, 6 V nominal, a separate high-current servo rail and common ground with Pi power.mvipin/trotbot commit 4ac874ef86ed99e9621df685ba23103aeebc0d9c | Exact supply/regulator, claimed peak current basis, branch/fuse layout, emergency stop, wire gauge, connector map and measured transients are not frozen. RCI has not energized the rail.Physical validation: none. |
| Separate 6 V high-current servo domain → PCA9685 16-channel PWM controllersource-to-target | powerSeparate servo-power input with common ground to Pi domain | The pinned PCA9685 section specifies 5 V logic and a separate servo-power input; the power section requires common ground between Pi and servo power.mvipin/trotbot commit 4ac874ef86ed99e9621df685ba23103aeebc0d9c | Logic-rail source, board topology, ground conductor, isolation, back-feed behavior, fuse and measured ground offset are not frozen. RCI has not inspected or powered this board.Physical validation: none. |
8 source items converted into claim-bounded records.
Identity, quantity and installed-hardware boundaries remain separate fields; a generic source label is never promoted to an exact orderable model.
| Source item | Class | Identity | Quantity boundary | Role + unresolved evidence |
|---|---|---|---|---|
| Raspberry Pi 5 (8 GB)Hardware Specifications / Complete Bill of Materials | computeInstalled / build item | variant-namedRaspberry Pi 5 8 GB | 1 unitOne main compute board is implied by the singular responsibility-party requirement. | Main computeNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| 32 GB or larger microSD cardHardware Specifications / Complete Bill of Materials | storageInstalled / build item | generic-descriptionNo exact identity published | 1 unitOne storage card is recommended; exact model is not fixed. | System storageNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| PCA9685 16-channel PWM driverHardware Specifications / Complete Bill of Materials | controlInstalled / build item | variant-namedPCA9685 | 1 unitOne 16-channel driver is specified. | Servo PWM generationNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| High-torque servo setHardware Specifications / Complete Bill of Materials | actuationInstalled / build item | generic-descriptionNo exact identity published | 12 unitTwelve total servos are published; exact model is configurable. | Three joints per leg across four legsNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| 5 V 5 A USB-C supplyHardware Specifications / Complete Bill of Materials | powerInstalled / build item | generic-descriptionNo exact identity published | 1 unitOne Pi supply requirement is published. | Raspberry Pi supplyNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| 6 V high-current servo power pathHardware Specifications / Complete Bill of Materials | powerInstalled / build item | generic-descriptionNo exact identity published | Not publishedElectrical requirement is published without exact orderable supply identity. | Actuator power domainNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| Nintendo Pro ControllerHardware Specifications / Complete Bill of Materials | controlInstalled / build item | variant-namedNintendo Pro Controller | 1 unitOne controller class is published. | Teleoperation inputNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
| 3D-printed frame and leg componentsHardware Specifications / Complete Bill of Materials | custom-mechanicalInstalled / build item | generic-descriptionNo exact identity published | Not publishedCustom geometry is described without a flattened printed-part count. | Quadruped structureNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot. |
Every conclusion returns to a selected source.
Links point to the responsibility party's material. RCI does not republish third-party BOM rows, CAD or retailer content through this profile.
TrotBot repository README ↗
Hardware Specifications / Complete Bill of Materials
Commit 4ac874eCorrection path
Know a newer revision or an exact as-built record?
Corrections must identify the platform revision, source location and the exact field affected. Manufacturer or project-party clarification is displayed alongside independently sourced evidence without replacing the original boundary.
Send a documented correction →