odriverobotics/odrive

High performance motor control

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 19 minutes ago
Added to GitGenius on September 18th, 2026
Created on April 25th, 2016
Open Issues & Pull Requests: 18 (+0)
GitHub issues: Enabled
Number of forks: 1,747
Total Stargazers: 3,767 (+0)
Total Subscribers: 162 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 21.0 hours
Mean response time: 3.4 days
90th percentile: 12.1 days
Tracked items: 9

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (5)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

ODrive is a motor controller firmware that enables high-performance control of brushless motors at low cost. The project aims to make inexpensive brushless motors viable for demanding robotics applications by providing accurate motor control through dedicated firmware and control software.

The firmware solves the problem of reliably driving brushless motors in robotics by implementing closed-loop control algorithms that work with inexpensive motor hardware. The approach combines firmware running on ODrive hardware with a Python library and tools that allow developers to configure, calibrate, and command the motor controller from their applications.

This repository contains firmware for the ODrive v3.x generation, which is no longer under active development. Developers should be aware that the firmware source code in this repository targets an older hardware generation. The manufacturer has released newer ODrive hardware generations, but their firmware source code is not publicly available. Anyone working with v3.x hardware or maintaining legacy systems may find this repository useful, but those starting new projects should evaluate whether the older hardware generation meets their requirements or contact the manufacturer about access to newer firmware.

The project maintains both master and devel branches with build status tracking. The repository structure separates firmware, Python tools, and documentation into distinct directories, and the team provides a developer guide for those contributing to firmware development.