What the hardware release requires
Doggo uses brushless motors, custom leg links and multiple motor controllers. Its hardware folder points to a Fusion 360 CAD assembly and a BOM; the author notes that some pieces must be waterjet cut and later drilled or tapped.
The project has dependencies on Doggo and ODrive submodules. Clone with submodules before attempting to build or edit the control code.
Motor setup before locomotion
The official README describes flashing custom ODrive firmware to four controllers, running doggo_setup.py and loading the Doggo Arduino code on the Teensy. On startup the legs calibrate the motors and encoders before the idle state.
Changes to mechanical gearing require matching gear-ratio values in the controller. A mismatch can turn small setpoint errors into unsafe joint movement.
Maintenance and present-day value
The publisher has ended Doggo support while focusing on Pupper V3. Its mechanical and low-level controller sources remain a learning resource, but present-day reproductions need extra component compatibility work.
Videos of jumps or flips do not constitute an assurance of performance for a self-assembled robot. Begin with static support and cautious motor tests.
Stanford Doggo brushless legs and ODrive setup
Use matching revisions of parts, firmware and instructions. These steps summarize project documentation; no physical build was performed for this article.
Official files and manuals 4 references
Assembly sequence 5 steps
Read the end-of-life notice
Check component availability and verify whether you can still reproduce the specific historical build.
Manufacturer's instructions ↗Obtain the full CAD and BOM
Fetch submodules and choose matching 3D-printed, waterjet and purchased parts.
Manufacturer's instructions ↗Manufacture and finish leg links
Perform documented drilling and tapping after cutting where required, checking alignment before assembly.
Manufacturer's instructions ↗Install controllers and firmware
Wire ODrive boards and the Teensy according to the project; configure custom firmware and gear ratios.
Manufacturer's instructions ↗Calibrate before gait trials
Start with supported joint positions and the idle state; verify feedback and controlled travel before locomotion.
Manufacturer's instructions ↗
Legacy firmware, cut parts and encoder tests
Answers are based on published source material and project documentation. Their order does not represent search volume.
01Is Stanford Doggo still maintained?
No. Its README explicitly announces end of life and directs new attention toward Pupper V3.
Sources Official project documentation ↗
02Are all structural parts 3D printed?
No. The author says some leg links require waterjet cutting, drilling and tapping in addition to printed pieces.
Sources Official project documentation ↗
03Why is my clone missing the control code?
Doggo and ODrive are submodules. Clone the repository recursively or initialize submodules at the pinned revisions.
Sources Official project documentation ↗
04Can I use stock ODrive firmware?
The official build instructions specify a custom ODrive fork. Stock firmware compatibility is not established for that historical controller configuration.
Sources Official project documentation ↗
05How do I calibrate the legs?
Flash the matching ODrive and Teensy code, run the supplied setup script and allow the startup encoder calibration as documented. Keep the robot supported during tests.
Sources Official project documentation ↗
06What happens if I change the transmission ratio?
The software must be updated to the new gear ratio; the author calls this out explicitly for modified mechanical designs.
Sources Official project documentation ↗
What to check before building Stanford Doggo
Build and integration
Use the historical Fusion 360 CAD and BOM as one snapshot. Prepare 3D-printed parts and waterjet links, drill and tap required joints, install brushless drives and the Teensy, then flash the project's custom ODrive firmware. Follow the calibration sequence before using any locomotion commands.
Known constraints
This project has an explicit end-of-life notice. Some CAD parts require waterjet cutting, hole drilling and tapping rather than printing. The ODrive firmware is a project-specific fork and the source may require recursive submodule checkout; do not expect modern board firmware to be a drop-in replacement.
Original documentation
Found a changed specification? Submit a correction with its source ↗