BamBot

The headline price is not a complete teleoperation setup

The hardware page's approximate $300 or €300 total belongs to its follower parts table. Printing, the leader hardware, computing and camera arrangements, tools and a complete power setup must be accounted for separately. Several US and EU cable entries show zero with unfinished purchase links; those are unresolved prices, not evidence that the parts are free. No current delivered price was verified. [S005]

The table selects 12 V STS3215 servos but discusses a 7.4 V alternative requiring different power provision. Its wheel links also span nominal four-inch, 100 mm and 80 mm products. Match the selected servo supply, wheel adapters and geometry before treating regional links as interchangeable. [S005]

Preserve the print release and control fork separately

The hardware guide links the v0.0.0 release. Its preserved STLs.zip contains 25 printable files, including arm, wheel, connector and body components. The separately linked editable Tinkercad assembly was not preserved, and the hardware guide remains marked drafting. File availability does not establish a verified assembly sequence or tested fit. [S005] [S012]

The main repository's software directory provides browser serial examples. The complete BamBot workflow instead points to timqian/lerobot-bambot, preserved here at commit 501d4414ed70bc6fa8641f58484960bb310e5e68. Its README tells readers to use the inherited LeKiwi guide with BamBot-specific changes. This review did not install either software route. [S006] [S007]

Follow the two-arm motor map

In the fork's LeKiwiRobotConfig, arm and gripper channels occupy IDs 1–12. The follower's left, back and right wheels are IDs 13, 14 and 15; the leader contains only IDs 1–12. The inherited guide still shows single-arm wheel IDs 7–9. Copying that example without adapting it would conflict with the second arm's IDs in the BamBot configuration. [S008] [S009]

The default camera is index 1, and the serial paths are machine-specific examples. The configuration uses a loopback address with ports 5555 and 5556; the guide distinguishes a wired arrangement running both processes on a laptop from a remote arrangement whose host address must be configured. Select one route and replace device identifiers consistently. [S008] [S009]

BamBot's README instructs both arms to be placed in the same pose simultaneously during calibration. The inherited guide describes manual arm calibration and says the wheel motors do not need that arm-calibration step. However, the calibrate_follower method filters out names beginning with wheel_, while the configured names are left_wheel, back_wheel and right_wheel. Those names are not excluded by that filter. The applicable calibration path needs tracing or upstream clarification before relying on the guide's wheel exclusion; this is a static observation, not an observed runtime failure. The motion conversion code defaults to a 0.05 m wheel radius and 0.125 m base radius, so those source values also need matching to the actual geometry. They are not measured dimensions or validated limits for every listed wheel. [S007] [S009] [S010]

Keep source rights and build readiness explicit

The control fork carries Apache 2.0 terms and additional notices for included third-party code. The hardware repository's root file is labeled Apache 2.0, but its trademark clause omits wording present in the standard text. The print archive itself contains no license file. This profile therefore leaves hardware-specific rights unresolved instead of treating all hardware and external models as unambiguously covered by a standard license. [S003] [S011] [S012]

No parts were purchased, printed or assembled, and no servo configuration, calibration, driving, teleoperation or learning experiment was performed. The entry records a source-backed configuration to investigate, with the inherited-guide differences and incomplete cost made explicit. [S005] [S007] [S008] [S009]