Open Source RoboticsRobots, software & learning

XDrive controller source

Software

Closed-loop stepper-controller firmware with linked Altium schematic/PCB, BOM and enclosure source references. [1] [3]

Installation & first result →Official websiteGetting started

For
Embedded motor-control developers familiar with STM32 and EDA source formats [1]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
operating system, compute requirements not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

XDrive is a closed-loop stepper-controller source project with application and bootloader firmware, board files, an upstream BOM and enclosure references. This profile covers those implementation/design references, not a motor-drive module whose complete build or operation has been reproduced. Start with a named revision before mixing board files and firmware. [1] [4]

The reviewed repository revision is e4aa58dee0e93b95732da67f50cc17c3a567b961, and the inspected hardware directory is Hardware/XDrive_H1.1b. This identifies the source snapshot; compatibility between that board and any compiled firmware has not been established. [4] [20]

Is this for you?

Known limitations
  • One actual Drive.SchDoc payload inspected as an Altium compound file with schematic records; full board/ERC/PCB manufacture not validated.
  • README's2021startup encoder workaround explicitly leaves an underlying issue unresolved.
  • GPL3 root and ST BSD3 file notices apply at different scopes; current complete build cost and hardware completeness remain unknown.

Editorial scope assessment from the cited implementation/documentation; no execution or compatibility test.

[1] [2] [3] [4] [20] · Editorial assessment

What you need

Dependencies
  • README points to Firmware_APP and Firmware_BL Keil project routes
  • Hardware revision and source/document versions must be matched; complete toolchain/BOM/power requirements not validated

[1] [2] [3] [4] [20]

Installation & first result

Open the upstream getting-started guide [1]

  • Begin with the pinned application/bootloader projects and H1.1b schematic; inspect source and board documentation before programming or manufacturing hardware.
  • Preserve exact source/dependency/model versions and evaluate the selected workflow before connecting physical hardware or reusing data.

Editorial scope assessment from the cited implementation/documentation; no execution or compatibility test.

[1] [2] [3] [4] [20] · Editorial assessment

Installation

Begin with the pinned application/bootloader projects and H1.1b schematic; inspect source and board documentation before programming or manufacturing hardware.

Editorial scope assessment from the cited implementation/documentation; no execution or compatibility test.

[1] [2] [3] [4] [20] · Editorial assessment

Hardware, models & data

Inputs and outputs

Stepper motor control/encoder-related firmware with board and enclosure references; no closed-loop operation tested.

Editorial scope assessment from the cited implementation/documentation; no execution or compatibility test.

[1] [3] · Editorial assessment

Project notes

Actual schematic content is present

We downloaded Hardware/XDrive_H1.1b/Drive.SchDoc from the selected repository revision. Its 65,024-byte payload has an Altium/Protel compound-file signature and embedded schematic capture records, including component references. This establishes more than a file name, but it is limited text/container inspection. No EDA application import, electrical-rule check, PCB verification, manufacturability assessment or board construction was performed. [20]

The tree separately lists PCB documents, schematic sheets, BOM and enclosure files. That does not establish their completeness or synchronization. The README identifies Firmware_APP as the main firmware project and Firmware_BL as the USB-update bootloader, including a Keil project route. Toolchain, exact board/firmware match and complete fabrication requirements still need review before programming or purchasing parts. [1] [4]

Do not turn a workaround into a resolved fault

The README's January 2021 notes describe avoiding startup jitter associated with an initial encoder read, while explicitly saying the underlying issue is unresolved. That is a limitation to investigate in the selected firmware, not evidence that current operation is fault-free. No startup, encoder, closed-loop motion or hardware safety test was run. [1]

The root notice is GPLv3; the inspected STM32-generated main.c header carries a third-party BSD-3-Clause notice. Preserve file-specific scopes. No current parts total, power configuration or complete first-working build cost was established, and no upstream assets are redistributed by this profile. [2] [3]

What we checked

Source research only. Selected implementation/model text, repository tree and license declarations were inspected. No upstream compilation, dependency installation, simulator, network/USB/device integration, data collection, benchmark or physical robot test was performed. Source files are linked rather than redistributed; external services and paid products are not endorsed.

Not yet established

  • Requirements: operating system, host computer
  • Version-specific hardware compatibility (ecosystem tags alone do not establish it)

Updates

Upstream last updated
Not established
Latest release
Not established
Profile updated
Nov 1, 2026
Sources last checked
Nov 1, 2026
Next review
Dec 1, 2026
Reviewed revision
e4aa58d

Source files and licenses

Distinct robot-facing library contribution with actual implementation/model content and a bounded documented next step. Review covers source artifacts, not operational performance or a complete tested deployment.

LayerAvailability / license
softwareavailable · GPL-3.0 root with file-specific third-party notices
Declaration for the scoped source implementation/documentation; dependencies, external services, model/data assets and inherited file-specific terms require separate checks. No blanket redistribution or operational clearance. [1] [2] [3]
documentationavailable · GPL-3.0 root with file-specific third-party notices
Declaration for the scoped source implementation/documentation; dependencies, external services, model/data assets and inherited file-specific terms require separate checks. No blanket redistribution or operational clearance. [1] [2] [3]

This profile is scoped to source implementation/model descriptions and an initial inspection workflow; no physical manufacturing design, pretrained checkpoint or dataset is selected for redistribution or tested deployment.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.7.0-draft.5

Change history