ODrive v3.x

Identify the board before using its limits

The v3.6 documentation distinguishes 24 V and 56 V variants, with listed input ranges of 12–24 V and 12–56 V respectively. It also says board files and schematics after v3.5 are closed source. Its linked v3.5 schematic and STEP model are therefore not a v3.6 manufacturing package. Public firmware, a board model and reproducible electronics are separate questions. [S006]

The controller supports two motor axes, but the getting-started guide recommends beginning with one motor and encoder. Budget for the motor, feedback device, power source, wiring and braking arrangement as well as the controller. The complete delivered cost and current availability of a matched legacy setup were not verified. [S005]

Commissioning depends on the motor and power system

USB does not power the board: the main supply is needed even for USB communication. Motor phase connections and a rigid encoder coupling must be established before calibration. Braking can return energy to the supply; the guide discusses a brake resistor and supply regeneration limits rather than assuming every power source can absorb that energy. [S005]

The setup requires motor current and velocity limits, suitable calibration current, pole pairs, torque constant and encoder counts per revolution. Encoder counts are not interchangeable with pulses per revolution. Parameters are saved to persistent memory through a save operation that reboots the board. Brake-resistor configuration also requires saving and rebooting to take effect. [S005]

Calibration measures motor electrical properties and encoder alignment while moving the rotor. The documented procedure allows inertia and weak friction but excludes a gravity or spring bias. Errors should be investigated before retrying; successful calibration is followed by closed-loop tuning. A communications watchdog exists but must be explicitly configured and enabled, so its presence in the code is not proof of an active stop-on-disconnection behavior. [S005]

Preserve the software pairing

The archive contains Python-based odrivetool instructions for Windows, macOS and Linux. Those instructions include old Python examples and historical package-management advice. They are useful evidence of the original setup, not confirmation that an unpinned install works on a current computer. Record the board revision, firmware and host-tool versions together before changing an existing system. [S002] [S005]

The guide also distinguishes older boards requiring initial ST-Link flashing from later boards described as preflashed. That historical shipment description does not establish the state of a used board today. No firmware was built or flashed, host tool installed, or motor operated during this review. [S005]

The selected firmware and repository software carry MIT licenses, with separate notices applying where present. This is a useful open legacy control stack for research and maintenance, with explicit limits on hardware design access and ongoing development. It is not a claim that every product sold under the ODrive name shares these sources. [S003] [S007] [S008]