Open Source RoboticsRobots, software & learning

Quad-SDK

Software

Quad-SDK organizes planning, control, estimation and robot-development tools for quadrupedal locomotion. [1] [2] [3] [4]

Installation & first result →Official websiteGetting started

For
Robotics developers investigating the named source configuration [1] [2] [3] [4]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
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

Quad-SDK organizes planning, control, estimation and robot-development tools for quadrupedal locomotion. Its repository includes Gazebo integration and source configurations for research workflows. The contribution is a robotics software stack, not a new manufactured quadruped or a reproduced locomotion result. [1]

Is this for you?

Known limitations
  • Historicalbranch/environment instructions are not currentdistribution validation.
  • Simulation/planning/control sources do notestablish newopenhardware or cross-platformsim-realparity.

Editorial assessment of cited source; no runtime or hardware test.

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

What you need

Operating system
  • Ubuntu 18.04 / ROS Melodic (README main)
  • Ubuntu 20.04 / ROS Noetic (README devel)

Documented source requirements/route, not installation or compatibility reproduced by this catalog.

[1]

Dependencies
  • README mainbranch ROSMelodic/Ubuntu18.04 vsdevelROSNoetic/Ubuntu20.04
  • Selectedquadrupedmodel, Gazebo/dependencies androbot-specificdriver ifmoving beyondsimulation

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

Installation & first result

Open the upstream getting-started guide [1] [2] [3] [4]

  • Inspect the named configuration, source interfaces and required external components.
  • Attempt only the matched documented workflow after resolving environment and rights gaps; no operation reproduced here.

Editorial assessment of cited source; no runtime or hardware test.

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

Installation

Match README main ROS Melodic/Ubuntu 18.04 versus devel ROS Noetic/Ubuntu 20.04 route and installation wiki before using the selected ROS 1 Gazebo launch.

Documented source requirements/route, not installation or compatibility reproduced by this catalog.

[1] [3]

Project notes

Match the ROS1 branch before following commands

The README reports Melodic/Ubuntu 18.04 testing for main and Noetic/Ubuntu 20.04 for devel. The reviewed commit is 50b58ce8f248ff8995270eae3fa0488c91eeddd4; its branch membership is not established by the selected excerpts. Establish the branch/environment match before setup. The README's installation wiki is a next documentation step, but its contents were not supplied here. The documented ROS 1 commands should not be silently translated into a modern ROS 2 setup. No workspace, installer or ROS distribution was installed here. [1]

Its bounded simulation route is roslaunch quad_utils quad_gazebo.launch; the selected launch defaults to the spirit robot, flat world, inverse_dynamics controller, GUI disabled, logging disabled and simulation time enabled. Preserve or deliberately change those choices; the supplied command does not enable the Gazebo GUI by default. The README then documents a robot mode topic and separate planning launches for twist input or a global planner. Inspect those topics/configurations before attempting them: command examples are not proof of safe physical stand-up or of communication with a real robot. None was run. [1] [3]

The selected local_planner.cpp provides actual planning-node implementation to inspect with the launch configuration. Its constructor obtains the robot-state topic through topics/state/ground_truth: check that topic mapping and state provider before adapting the workflow beyond simulation. It was not executed. [4]

The source's EKF and outdoor walking descriptions remain upstream reports. A simulation process or model visualization does not establish state-estimation accuracy, timing, contact behavior or transfer to an arbitrary vendor quadruped. Hardware drivers, model assets and vendor SDK dependencies require their own configuration and rights review. [1]

The root notice is MIT; check component, dependency and asset notices separately rather than assuming this establishes every contribution's terms. No compilation, Gazebo episode, navigation/controller result, hardware motion or restart behavior was verified. [2]

What we checked

Pinned source/document inspection only; no installation, compile, credentials/API use, simulator, lab experiment or physical hardware test.

Not yet established

  • Requirements: 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
50b58ce

Source files and licenses

Concrete scoped robot-facing software/research workflow, not complete manufacturing or verified operational behavior.

LayerAvailability / license
softwareavailable · MIT
Selected source availability/notice only; external hardware, models, data and dependencies have separate rights. No blanket redistribution or operational clearance. [1] [2] [3] [4]
documentationavailable · MIT
Selected source availability/notice only; external hardware, models, data and dependencies have separate rights. No blanket redistribution or operational clearance. [1] [2] [3] [4]

No separate physical design, pretrained distribution or dataset is selected as the released contribution in this scoped software review.

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