# ODrive MCU Burned Out While Reproducing Stanford Doggo Project

**URL:** <https://discourse.odriverobotics.com/t/odrive-mcu-burned-out-while-reproducing-stanford-doggo-project/14232>\
**Category:** ODrive v3 Support\
**Created:** [May 27, 2026, 3:03pm UTC](https://discourse.odriverobotics.com/t/odrive-mcu-burned-out-while-reproducing-stanford-doggo-project/14232 "2026-05-27T15:03:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![yudong](https://discourse.odriverobotics.com/letter_avatar_proxy/v4/letter/y/e68b1a/32.png) [@yudong](https://discourse.odriverobotics.com/u/yudong)\
**Post date:** [May 27, 2026, 3:03pm UTC](https://discourse.odriverobotics.com/t/odrive-mcu-burned-out-while-reproducing-stanford-doggo-project/14232/1 "2026-05-27T15:03:22Z")

</div>

Hello everyone in the community,

I’m a beginner with ODrive, and the first project I’m trying to learn from is the open-source Stanford Doggo quadruped robot. However, I encountered a serious issue while reproducing the project, and I would really appreciate any advice or guidance from experienced users here.

First, I connected the encoders to the ODrive board and confirmed that the A/B phase signals were outputting proper square waves. After that, I connected the motors. However, the moment I powered the system on after connecting everything, the MCU on my ODrive became extremely hot and eventually burned out.

I have spent several weeks trying to figure out what caused this problem, but I still cannot determine the root cause.

I was using completely open-source code and only connected:

- 2 encoders
- 2 motors
- 1 ODrive board

What confuses me is that before this happened, I had already successfully tested and calibrated the two motors.

I would be very grateful for any suggestions or troubleshooting ideas from the community.