Humanoid · ToddlerBot project / Carnegie Mellon University

ToddlerBot teleoperation leader files

Record state

Public BOM audited. This is a source-bound system evidence record, not an independent rebuild.

Publication surface

Versioned repository file tree · commit-addressable.

Rebuild conclusion

No complete rebuild evidence package found.

IDENTITY + REVISION

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

ToddlerBot teleoperation leader files

teleop_leader configuration tree at ToddlerBot commit e337f3b177b4b53abff70b31d1695a7b66cc6d2e.

Version state

Addressable source snapshot

The selected engineering surface is immutable at the cited commit or release asset. It is not a serial-numbered as-built robot manifest.

Lifecycle boundary

Changes remain attached to the source.

Configuration-specific folders are kept separate. RCI does not merge actuator, gripper or leader variants into one fictional build.

Responsibility party

ToddlerBot project / Carnegie Mellon University

RCI maps the named public responsibility party; inclusion does not imply endorsement, partnership or unit-level verification.

VERSION & SUPPLY

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

Immutable configuration geometry plus active fixed-XML-filtered actuator composition; full-body variants also expose the pinned J4012/Orin NX, serial fan-out, IMU, stereo-camera and bounded power architecture.

Largest rebuild gap: No cryptographically frozen full procurement sheet, exact motor suffix set, communication-board revision, as-built serial evidence, powered acceptance record or independent rebuild closes the configuration.

Editorial boundary: RCI normalizes only responsibility-party file identity, revision, engineering role and unresolved boundaries. The record is not a procurement BOM, unit manifest, successful rebuild, compatibility proof, endorsement or RCI hardware test.

DISCLOSURE MATRIX

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 dimensionStateWhat the state means here
Exact platform revisionPublishedThe selected responsibility-party surface publishes this dimension inside the recorded boundary.
Versioned BOM snapshotPartialUseful information exists, but exactness, completeness or version binding remains incomplete.
Line-item quantitiesPartialUseful information exists, but exactness, completeness or version binding remains incomplete.
Manufacturer part numbersPartialUseful information exists, but exactness, completeness or version binding remains incomplete.
Supplier linksPartialUseful information exists, but exactness, completeness or version binding remains incomplete.
Custom-part production filesPublishedThe selected responsibility-party surface publishes this dimension inside the recorded boundary.
Electrical interconnect definitionPartialUseful information exists, but exactness, completeness or version binding remains incomplete.
Software / firmware bindingPartialUseful information exists, but exactness, completeness or version binding remains incomplete.
License boundaryPublishedThe selected responsibility-party surface publishes this dimension inside the recorded boundary.
Change, EOL and substitution historyPartialUseful information exists, but exactness, completeness or version binding remains incomplete.
Unit-level as-built manifestNot publishedThe selected sources do not publish this evidence dimension.
Independent rebuild evidenceNot publishedThe selected sources do not publish this evidence dimension.
BOM SURFACE

toddlerbot/descriptions/teleop_leader configuration-specific engineering files plus selected pinned system and actuator-composition rows

The count below preserves the responsibility party's publication structure; it is not silently flattened into unique purchasable components.

Selected count

51 rows / list items

51 selected responsibility-party records combine immutable configuration paths with bounded system rows. File paths are not installed quantities; actuator counts are active configuration assignments after default/config deep merge and fixed-XML filtering, not serialised as-built evidence.

Format

Versioned repository file tree

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.

RELATION GRAPH

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.

ASSEMBLY + INTERFACE TOPOLOGY

4 bounded nodes and 3 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

External leader-side teleoperation host

Pinned teleoperation leader configuration operated from an external development/teleoperation host.

Identity boundary: Host model, operating system, software environment, USB controller and physical machine are not frozen.

Source rows: toddlerbot-teleop-leader-item-03

control node

Leader serial-interface boundary

Serial interface between external host and leader-arm Dynamixel bank.

Identity boundary: Board revision, selected channels, USB descriptor, driver/latency state, port mapping and physical controller are not frozen.

Source rows: toddlerbot-teleop-leader-item-04

actuation node

Fourteen-position bilateral leader actuator bank

Fixed XML retains 2 XC430 and 12 2XL430 family assignments; software assigns teleop-leader motor IDs from 16 upward.

Identity boundary: Family assignments and software IDs do not prove complete order codes, EEPROM state, serials, calibration, follower pairing or physical installation.

Source rows: toddlerbot-teleop-leader-item-01, toddlerbot-teleop-leader-item-02

power node

External leader actuator-power boundary

An external source must power the fourteen leader actuator positions.

Identity boundary: Supply voltage/current, connector, polarity, protection, distribution, grounding and powered acceptance are not frozen.

Source rows: toddlerbot-teleop-leader-item-05

From → toRelationPublished supportStill unresolved
External leader-side teleoperation host → Leader serial-interface boundarybidirectionaldata-controlExternal-host USB serial boundaryThe teleoperation leader is operated from an external host through the project Dynamixel serial-control stack.hshi74/toddlerbot commit e337f3b177b4b53abff70b31d1695a7b66cc6d2eHost, controller board, USB descriptor, driver, port and observed enumeration are not frozen. RCI has not connected the leader interface.Physical validation: none.
Leader serial-interface boundary → Fourteen-position bilateral leader actuator bankbidirectionaldata-controlDynamixel Protocol 2.0 leader control/feedback boundaryPinned fixed XML retains fourteen active leader positions and pinned code offsets their IDs from 16 while using the Dynamixel SDK path.hshi74/toddlerbot commit e337f3b177b4b53abff70b31d1695a7b66cc6d2eComplete suffixes, port, baud, EEPROM, firmware, physical IDs, calibration and follower mapping are not frozen. RCI has not read or commanded the leader bank.Physical validation: none.
External leader actuator-power boundary → Fourteen-position bilateral leader actuator banksource-to-targetpowerExternal leader actuator-power boundaryThe fourteen active leader actuator positions require a separate powered hardware path; RCI models it without inventing an orderable supply.hshi74/toddlerbot commit e337f3b177b4b53abff70b31d1695a7b66cc6d2eVoltage, current, connector, polarity, distribution, protection, ground, load margin and powered behavior are not published in the selected configuration surface. RCI has not applied power.Physical validation: none.
NORMALIZED BOM

51 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 itemClassIdentityQuantity boundaryRole + unresolved evidence
left_elbow_gear_drive_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_elbow_gear_drive_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_elbow_gear_drive_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_elbow_gear_drive_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_elbow_roll_link_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_elbow_roll_link_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_elbow_roll_link_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_elbow_roll_link_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_elbow_yaw_link_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_elbow_yaw_link_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_elbow_yaw_link_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_elbow_yaw_link_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_hand_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_hand_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_hand_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_hand_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_leader_hand_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_leader_hand_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_leader_hand_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_leader_hand_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_shoulder_gear_drive_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_shoulder_gear_drive_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_shoulder_gear_drive_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_shoulder_gear_drive_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_shoulder_pitch_link_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_shoulder_pitch_link_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_shoulder_pitch_link_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_shoulder_pitch_link_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_shoulder_roll_link_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_shoulder_roll_link_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_shoulder_roll_link_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_shoulder_roll_link_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_shoulder_yaw_link_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_shoulder_yaw_link_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_shoulder_yaw_link_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_shoulder_yaw_link_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_wrist_gear_drive_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_wrist_gear_drive_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_wrist_gear_drive_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_wrist_gear_drive_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_wrist_pitch_link_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_wrist_pitch_link_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
left_wrist_pitch_link_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/left_wrist_pitch_link_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_elbow_gear_drive_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_elbow_gear_drive_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_elbow_gear_drive_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_elbow_gear_drive_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_elbow_roll_link_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_elbow_roll_link_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_elbow_roll_link_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_elbow_roll_link_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_elbow_yaw_link_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_elbow_yaw_link_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_elbow_yaw_link_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_elbow_yaw_link_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_hand_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_hand_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_hand_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_hand_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_leader_hand_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_leader_hand_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_leader_hand_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_leader_hand_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_shoulder_gear_drive_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_shoulder_gear_drive_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_shoulder_gear_drive_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_shoulder_gear_drive_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_shoulder_pitch_link_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_shoulder_pitch_link_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_shoulder_pitch_link_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_shoulder_pitch_link_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_shoulder_roll_link_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_shoulder_roll_link_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_shoulder_roll_link_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_shoulder_roll_link_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_shoulder_yaw_link_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_shoulder_yaw_link_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_shoulder_yaw_link_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_shoulder_yaw_link_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_wrist_gear_drive_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_wrist_gear_drive_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_wrist_gear_drive_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_wrist_gear_drive_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_wrist_pitch_link_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_wrist_pitch_link_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
right_wrist_pitch_link_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/right_wrist_pitch_link_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
torso_collision.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/torso_collision.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
torso_visual.stltoddlerbot/descriptions/teleop_leader/assetscustom-mechanicalAlternative / not simultaneously installedfile-identifiedtoddlerbot/descriptions/teleop_leader/assets/torso_visual.stlNot publishedOne distinct file path is present in the selected immutable evidence surface; the path does not publish an installed or procurement quantity.Custom-part geometry or production assetFile presence does not prove that this revision was manufactured or installed on one physical robot. No unit-level as-built manifest binds this file to a serialised system.
XC430 leader-arm actuator positionsPinned default.yml, teleop_leader fixed XML and responsibility-party teleoperation architectureactuationInstalled / build itemvariant-namedXC430 family2 unitTwo active XC430 family assignments survive the teleop-leader fixed-XML filter.Bilateral leader shoulder-pitch actuationNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
2XL430 leader-arm actuator positionsPinned default.yml, teleop_leader fixed XML and responsibility-party teleoperation architectureactuationInstalled / build itemvariant-named2XL430 family12 unitTwelve active 2XL430 family assignments survive the teleop-leader fixed-XML filter.Remaining bilateral leader-arm actuationNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
External teleoperation hostPinned default.yml, teleop_leader fixed XML and responsibility-party teleoperation architecturecomputeInstalled / build itemgeneric-descriptionNo exact identity published1 unitThe architecture supports an external development/teleoperation computer, but no exact host SKU, OS image or physical unit is fixed.Leader-side teleoperation computeNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
Eight-channel communication board boundaryPinned default.yml, teleop_leader fixed XML and responsibility-party teleoperation architecturecontrolInstalled / build itemgeneric-descriptionNo exact identity published1 unitA serial communication boundary is required; board revision, selected channels, USB identity and port mapping are not frozen for the leader configuration.Host-to-leader Dynamixel serial interfaceNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
External leader-arm power boundaryPinned default.yml, teleop_leader fixed XML and responsibility-party teleoperation architecturepowerInstalled / build itemgeneric-descriptionNo exact identity publishedNot publishedThe configuration requires actuator power, but exact supply, voltage branch, protection, connector and as-built wiring are not fixed in this selected surface.Leader actuator energy sourceNo unit serial, receipt, lot or as-built inspection binds this row to one physical robot.
SOURCE REGISTER

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.

01

ToddlerBot teleop_leader configuration tree ↗

46 configuration-specific files plus selected rows derived from default.yml, configuration robot.yml, fixed XML and pinned hardware/software documentation; shared geometry remains separate

teleop_leader configuration tree at ToddlerBot commit e337f3b177b4b53abff70b31d1695a7b66cc6d2e.

Correction 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 →

Return to all robot systems · Machine-readable record