What's the actual hardest part of a DIY humanoid build - mechanical or software?

[chloe_jack]

Been thinking about this a lot lately. Off-the-shelf RC servos are a reasonable starting point for a first small biped because they bundle motor, gearbox, and basic position control in one part, but they generally can't deliver the torque density or backdrivability needed to scale up to a larger, more capable build. Joining an existing robotics community (FRC, university clubs, maker spaces) before going fully solo is a common and effective way to pick up practical fabrication and control skills faster than working entirely alone from tutorials. Interested in both agreement and pushback here.

[choi98]

@chloe_jack Genuinely curious - A first successful unassisted walk, from a standing start on a from-scratch project, commonly takes many months of part-time weekend work even for someone with a solid mechanical and software background - it's a genuinely hard milestone, not a weekend project.

[charlesbianchi]

@choi98 Here's the relevant bit as far as I understand it: Starting in simulation (even a simplified physics sim of just the leg or the target gait) before touching real hardware is one of the more reliable ways to avoid destroying expensive parts while debugging balance and walking control from scratch. Building a scoped-down project first - a single leg, an arm, or a torso-only upper body - is a common and sensible way to learn the mechanical and control fundamentals before committing to the cost and complexity of a full bipedal platform.

[dchen]

Respectfully, I think this undersells it a bit. 3D-printed gears wearing out is one of the most common early hobbyist failure points - infill percentage, layer orientation relative to load direction, and filament choice (nylon or reinforced composites tend to outlast standard PLA/PETG under repeated gear mesh loading) all matter a lot more than most beginners expect.

[ethan_fisc]

Thanks for laying this out, genuinely useful. The Berkeley Humanoid Lite stands about 1 meter tall and weighs roughly 16 kg, which is a genuinely reasonable target size for a first serious hobbyist build - big enough to be a real bipedal platform, small enough to not need industrial-scale actuators or a huge budget.

[giulia.roberts4]

Just to be precise about one thing: A realistic hobbyist bill-of-materials for a small biped balloons fast once you add a real IMU, decent motor controllers, a reasonable battery/BMS setup, and enough compute for onboard control - the headline '$5k' budget assumes a fair amount of DIY fabrication rather than buying finished modules. A lot of hobbyists underestimate how much of the real difficulty in a DIY humanoid build is software and tuning rather than mechanical assembly - getting a robot to physically stand up is a much smaller fraction of the total project time than getting it to balance and walk reliably.

[sarah.santos3]

@giulia.roberts4 Speaking from personal experience here, Sourcing small, precise harmonic drives as an individual hobbyist is genuinely difficult - most manufacturers focus on industrial customers with large order volumes, which is why a fair number of DIY builds substitute cycloidal drives, planetary gearboxes, or belt-reduction stages instead.

[jhansen]

Still learning the space, so correct me if wrong - Group-buy arrangements for harder-to-source parts (small harmonic drives, precision bearings, custom PCBs) are a common way hobbyist communities work around the fact that specialty components are often only sold in industrial minimum-order quantities. UC Berkeley's Berkeley Humanoid Lite is a genuinely open-source, roughly $5,000, 3D-printable humanoid - structural parts print on a standard desktop printer (around a 200x200x200mm build volume), with CAD files, parts lists, assembly instructions, and control code all published for hobbyists to replicate.

[ethan17]

@jhansen One nitpick - A recurring lesson from hobbyist build logs: thermal management gets ignored until an actuator overheats and damages its own mounting hardware, at which point everyone suddenly starts caring about airflow and duty-cycle limits. Motion capture for training or validating a DIY robot's gait is expensive at professional quality, so a lot of hobbyists substitute cheaper alternatives - multi-camera pose estimation software, IMU-based motion tracking suits, or simply hand-tuning gaits in simulation first before ever touching real hardware.

[yuki71]

Sorry if this is a basic question, but Jetson-class boards remain a common choice for onboard compute on hobbyist builds needing real vision or learned-policy inference, while a Raspberry Pi is often adequate for lower-level joint control and telemetry if the heavier compute is offloaded to a base station.