Odrive 3.6 Schematic
The ODrive 3.6 uses the STM32F405RGT6. The schematic reveals the genius of the pin mapping.
Pro Tip: If you are designing a custom breakout board, never assign these specific timer/ADC pins to anything else. The firmware expects them at hard-coded addresses.
The schematic reveals a sophisticated multi-rail power system designed to handle high voltages (12V–56V) while generating clean low-voltage supplies for sensitive analog and digital components.
The ODrive doesn’t measure motor current just by looking at the DC input. Instead, it measures the current in each phase individually using low-ohm shunt resistors placed between the low-side MOSFETs and ground. odrive 3.6 schematic
Pros:
Cons:
The ODrive 3.6 is widely considered the gold standard for open-source, high-performance motor control. Whether you are building a 3D printer, a robotic arm, or a custom electric skateboard, the ODrive’s ability to run high-power BLDC (Brushless DC) motors with incredible precision is unmatched. The ODrive 3
However, to truly master this device—whether you are troubleshooting a burnt MOSFET, designing a custom carrier board, or simply trying to understand why the encoder inputs are where they are—you need one thing: the ODrive 3.6 schematic.
In this article, we will dissect the official ODrive 3.6 hardware design, explain the critical sub-sections of the schematic, and show you how to use this document to elevate your robotics projects.
The board functions as a three-phase inverter. It takes a high-voltage DC input (from a power supply or battery) and converts it into three variable-frequency AC outputs to drive a BLDC motor. Pro Tip: If you are designing a custom
The schematic can be broken down into four main subsystems:
The main controller is an STM32F405 with an ARM Cortex-M4 FPU running at 168 MHz. On the schematic, you will see:
Crucially, the schematic maps which GPIOs go to which peripherals: timers for PWM (TIM1, TIM8), ADCs for current sensing, and UARTs for communication.
