Odrive 3.6 Schematic [better]
The official ODrive v3.6 schematic is hosted on the ODriveHardware GitHub repository
. While v3.6 specifically is the common production version, ODrive maintains that it is functionally identical to v3.5 , and documentation often refers to the v3.5 files for both ODrive Community Key Schematic & Hardware Resources Official Schematic (PDF): You can download the full v3.5 Schematic which covers the v3.6 design. Hardware Repository: ODriveHardware v3 directory
contains the PCB layout files (Altium) and PDF documentation. Alternative Viewers: Third-party uploads on
also host schematic overviews, though GitHub remains the primary source for the latest revisions. Quick Component References
Based on the schematics, here are the core components used in the v3.6 design: Microcontroller: STM32F405RGT6 Gate Driver: ODrive Community Power Variants: The v3.6 comes in (12V-24V range) and (12V-56V range) versions ODrive Europe Design Status ODrive v3.6 is currently listed as NRND (Not Recommended for New Designs) ODrive Europe odrive 3.6 schematic
. For new high-performance robotics projects, the manufacturer recommends upgrading to the ODrive Europe ODrive Pro ODrive Community
models, which offer improved connectivity and safety features. BOM (Bill of Materials) to build your own board, or do you need the schematic to troubleshoot a specific issue like a burnt component?
ODriveHardware/v3/v3.5docs/schematic_v3.5.pdf at ... - GitHub
ODriveHardware/v3/v3. 5docs/schematic_v3. 5. pdf at master · odriverobotics/ODriveHardware · GitHub. The official ODrive v3
odriverobotics/ODriveHardware: High performance motor control
6. Hall Sensor Inputs (optional)
- 3x Hall per motor (H0, H1, H2) pulled up to 5V
4. Gate Drivers & Three-Phase Inverter (Per Motor)
This is the most complex and power-dense section. For each motor (M0 and M1), the schematic includes:
- Gate Driver IC (e.g., DRV8301 or FD6288Q): This chip takes the 3.3V PWM signals from the STM32 and converts them into high-current, high-voltage signals needed to drive the six MOSFETs per motor. It also handles shoot-through protection and adjustable dead-time.
- MOSFETs (Six per phase – Q1-Q6 for M0, Q7-Q12 for M1): Typically TO-220 or D2PAK package N-channel MOSFETs (e.g., CSD19536KCS). The schematic shows the half-bridge topology: high-side (drain to source) and low-side.
- Bootstrap Circuitry: Capacitors (e.g., C30, C31) and diodes for the high-side MOSFETs, allowing the gate voltage to swing above the main DC bus.
- Gate Resistors (R1-R6): Small resistors (e.g., 10Ω) in series with each gate to dampen ringing and control switching speed.
Heat Warning: The schematic does not show heatsinks, but it hints at their necessity by specifying copper pour areas under the MOSFETs.
Common Mistakes When Reading the Schematic
- Assuming it’s simple: The ODrive 3.6 schematic is not a beginner document. It assumes you know the difference between a pull-up resistor and a current shunt.
- Ignoring the "Power-Ground" split: If you probe a signal with an oscilloscope, connect the ground clip to the logic ground test point, not the motor ground terminal. The schematic shows they are connected via a ferrite bead—using the wrong ground will destroy your scope probe.
- Overlooking the 56V limit: The schematic clearly labels the voltage rating of the DC-link capacitors (usually 63V). Feeding 60V will cause the caps to explode regardless of what the MOSFETs can handle.
Overview
- ODrive 3.6 is a motor controller board used for brushless DC (BLDC) motors with high-current control and encoder feedback. The schematic shows power stages, motor drivers (MOSFETs), gate drivers, current sensing, microcontroller, encoder interfaces, and protection circuits.
4. Current & Voltage Sensing
- Phase Current Sensing: Three low-side shunt resistors feed differential amplifiers (e.g., INA240) whose outputs go to the STM32’s ADCs. This allows for FOC (Field-Oriented Control) current loops.
- DC Bus Voltage Sensing: A resistive voltage divider (with high-impedance buffer) scales VBUS down to 0–3.3V for over-voltage and power calculation.
- Temperature Sensing: A thermistor (NTC) on the PCB, routed to an ADC input, enables thermal derating.
Conclusion
The ODrive 3.6 schematic is a masterclass in integrated motion control. It balances high-current design with sensitive analog measurement, leveraging the STM32’s advanced timers and the robustness of dedicated gate drivers. For anyone designing a similar BLDC controller, studying this layout and schematic is highly recommended. 3x Hall per motor (H0, H1, H2) pulled up to 5V
I’m unable to provide a direct schematic image or file for the ODrive 3.6 (e.g., the actual PCB layout, component values, or proprietary circuitry), because that hardware design is copyrighted and proprietary to ODrive Robotics. Sharing the full schematic would violate their intellectual property.
However, I can give you a high-level functional block description of what the ODrive 3.6 schematic contains, based on publicly available information, open-source hardware documents they have released (like the v3.5–3.6 community materials), and reverse-engineering notes from the maker community.
Conclusion: The Schematic as a Learning Tool
The ODrive 3.6 schematic is a masterclass in practical motor drive design. It elegantly combines a powerful microcontroller, robust gate driving, high-current switching, precision analog sensing, and flexible I/O in a two-layer (plus heavy copper) board. Whether you are a robotics engineer debugging a blown board, a student learning FOC, or a maker building a custom CNC controller, studying this schematic will elevate your understanding of brushless motor control.
Remember: the schematic is the truth of the hardware. When in doubt, refer to it, trace the signals, and don’t be afraid to probe with a multimeter or oscilloscope. Happy hacking.
Further Resources:
- ODrive Hardware GitHub Repository
- STM32F405 Datasheet
- DRV8301/FD6288Q Datasheets
- "Field-Oriented Control Explained" – ODrive Community Guides
Need specific help with a repair or modification? Join the ODrive Discord or Forum, and always mention which revision of the schematic you are referencing.