Floating base dynamics is the mathematical description of motion for a multi-body system, such as a legged robot or drone, where the base link is not kinematically fixed to an inertial frame. This introduces six unactuated degrees of freedom (three for translation, three for rotation) for the base's pose, making the system underactuated and requiring special treatment in modeling and control. The dynamics are derived from Newton-Euler equations or Lagrangian mechanics, explicitly accounting for the coupling between the freely moving base and the actuated joints.
Glossary
Floating Base Dynamics

What is Floating Base Dynamics?
The mathematical framework governing the motion of robots whose base is not fixed to the world, a fundamental concept for legged and mobile systems.
In practice, floating base dynamics are essential for state estimation, whole-body control, and motion planning. The equations are used to compute required joint torques for a desired base acceleration while satisfying contact constraints with the environment. This framework directly enables advanced behaviors like dynamic walking, push recovery, and acrobatic maneuvers by providing the precise relationship between internal forces, external ground reaction forces, and the resulting motion of the entire system.
Key Mathematical Properties
The equations of motion for a floating base system are distinguished by their treatment of the unactuated base and the constraints imposed by intermittent ground contact. These properties form the foundation for dynamic simulation, control, and motion planning.
Unactuated Base Coordinates
The system's configuration is described by floating base coordinates, typically the 6-DOF pose (position and orientation) of a base link (e.g., the pelvis or torso) relative to a world frame, plus the joint angles. The key property is that the six base coordinates are unactuated—no direct motor torque acts on them. Their motion is governed entirely through dynamic coupling with the actuated limbs via the equations of motion. This necessitates control strategies that use limb motion to indirectly control the base.
Equations of Motion Structure
The dynamics are derived using Lagrangian or Newton-Euler methods, resulting in a matrix equation:
M(q) * v̇ + C(q, v) * v + G(q) = Sᵀ * τ + J_c(q)ᵀ * f
- M(q): The system's mass matrix, which is symmetric, positive-definite, and configuration-dependent.
- C(q, v): The Coriolis and centrifugal forces matrix.
- G(q): The gravitational forces vector.
- S: A selection matrix that maps actuated joint torques (τ) into the generalized force space.
- J_c(q): The contact Jacobian mapping external contact forces (f) (e.g., Ground Reaction Forces) into generalized forces.
This structure explicitly separates actuated inputs (τ) from external contact forces (f).
Contact Constraints
Intermittent contact with the environment introduces kinematic constraints. When a foot is firmly planted (sticking contact), its velocity is constrained to zero: J_c(q) * v = 0. Differentiating this yields the acceleration-level constraint: J_c(q) * v̇ + J̇_c(q) * v = 0. These constraints are holonomic for position and non-holonomic for velocity. The contact forces f become Lagrange multipliers that enforce these constraints. The dynamics are therefore hybrid, switching between different constraint regimes as feet make and break contact.
Centroidal Dynamics Coupling
A critical property is the decomposition between the floating base and the centroidal dynamics. The net external wrench (force and moment) on the robot equals the rate of change of its centroidal momentum (linear momentum of the center of mass and angular momentum about the CoM). This is described by the Newton-Euler equations:
Σ f_ext = m * a_com
Σ (r_i × f_i + μ_i) = L̇_com
where L_com is the centroidal angular momentum. These equations provide a high-level, force-based description that is directly coupled to the detailed floating-base model via the Centroidal Momentum Matrix.
Underactuation and Dynamic Consistency
Because the base is unactuated, the system is underactuated when not in full static contact. The dynamic consistency property states that any feasible motion of the center of mass and centroidal angular momentum must be achievable through some combination of joint accelerations and contact forces. This is formalized by projecting the full dynamics into the null-space of the contact constraints and the range-space of the actuation. Control algorithms like Whole-Body Control exploit this by prioritizing tasks (e.g., CoM motion) that satisfy the underactuated dynamics.
Numerical Integration & Featherstone's Algorithm
For simulation and model-based control (e.g., MPC), the equations must be solved efficiently. Featherstone's Articulated Body Algorithm (ABA) computes forward dynamics (v̇ given τ and f) in O(n) time. Its inverse, the Recursive Newton-Euler Algorithm (RNEA), computes inverse dynamics (τ given v̇ and f). For floating bases, these algorithms are initialized with a fictitious 6-DOF joint connecting the base to the world. The Composite Rigid Body Algorithm (CRBA) is used to compute the mass matrix M(q). These algorithms are foundational for real-time control.
How Floating Base Dynamics Enables Control
Floating base dynamics is the mathematical framework that governs the motion of robots and other multi-body systems whose base link is not fixed to the world, a fundamental concept for legged locomotion and mobile manipulation.
Floating base dynamics refers to the equations of motion for a multi-body system, like a legged robot or a drone, where the base link has six unactuated degrees of freedom (three translational, three rotational) and is not kinematically fixed to an inertial frame. This formulation treats the entire system as 'floating' in space, requiring special mathematical treatment to account for the dynamic coupling between the freely moving base and the actuated joints. The resulting Newton-Euler equations form the core of model-based control, state estimation, and motion planning for any robot that moves through its environment without a fixed anchor.
For control, these dynamics are essential because they define the relationship between ground reaction forces, joint torques, and the resulting acceleration of the robot's center of mass. Controllers use this model to solve inverse dynamics or formulate Quadratic Programs (QP) to compute the forces and torques needed to achieve desired motions while maintaining dynamic balance. This enables advanced behaviors like push recovery and terrain adaptation, as the controller can predict how a push or a step onto uneven ground will affect the floating base's trajectory and preemptively generate stabilizing actions.
Frequently Asked Questions
Floating base dynamics is the mathematical framework governing the motion of robots whose base is not fixed to the world, such as legged or mobile robots. This section answers key questions about its formulation, challenges, and role in modern robotics.
Floating base dynamics is the set of equations of motion for a multi-body system, like a humanoid or quadruped robot, where the base link (e.g., the torso) is not attached to a fixed point in space and has six unactuated degrees of freedom (three for position, three for orientation). This is fundamental because it correctly models the robot's true physical interaction with the world, where external ground reaction forces and moments are what ultimately cause the base to accelerate, not direct joint actuation. Accurate dynamics are essential for computing stable motions, feasible joint torques, and for model-based controllers like Model Predictive Control (MPC) and Whole-Body Control (WBC) to function correctly.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Floating base dynamics is a foundational concept for legged robots. These related terms define the specific models, control strategies, and stability criteria built upon this dynamic framework.
Centroidal Dynamics
Centroidal dynamics describes the relationship between the net external forces and moments acting on a robot and the motion of its center of mass and its centroidal angular momentum. It is a crucial simplification for whole-body control, as it aggregates the complex multi-body dynamics into the motion of a single rigid body (the centroidal frame) located at the CoM. This allows planners to reason about balance and angular momentum without solving the full floating base equations at every iteration.
- Key Application: Used in Whole-Body Control (WBC) to generate dynamically consistent motions.
- Core Equation: Relates the time derivative of the centroidal angular momentum to the net external moment about the CoM.
Whole-Body Control (WBC)
Whole-Body Control (WBC) is a hierarchical control framework that coordinates all degrees of freedom of a legged robot to execute multiple tasks simultaneously—like maintaining balance, tracking foot trajectories, and avoiding joint limits—while strictly respecting physical constraints like contact forces and torque limits. It directly utilizes the floating base dynamics model to solve for joint torques and contact forces in real-time, often formulated as a Quadratic Program (QP).
- Primary Input: A set of prioritized tasks (e.g., CoM position is higher priority than arm posture).
- Core Mechanism: Solves an optimization problem that includes the full rigid-body dynamics equations, treating the floating base explicitly.
Reduced-Order Model (ROM)
A Reduced-Order Model (ROM) is a simplified dynamic representation that captures the essential locomotion dynamics while ignoring the full complexity of the multi-body system. The most common ROMs, like the Linear Inverted Pendulum (LIPM) and Spring-Loaded Inverted Pendulum (SLIP), are derived from or are compatible with the floating base framework. They treat the robot as a point mass or a simple mechanical system, enabling fast planning for footstep placement and center of mass trajectory generation.
- Examples: LIPM for walking, SLIP for running/hopping.
- Purpose: Enables real-time model predictive control by drastically reducing computational complexity.
Quadratic Program (QP) Formulation
A Quadratic Program (QP) formulation is the standard mathematical optimization structure used to solve real-time control problems in legged robotics, such as inverse dynamics and Whole-Body Control. The floating base dynamics equations provide the linear equality constraints that ensure physical consistency. The QP minimizes a quadratic cost (e.g., tracking error, energy use) subject to these dynamics constraints and other linear constraints for contact forces, friction cones, and torque limits.
- Standard Form: Minimize a quadratic cost function subject to linear equality and inequality constraints.
- Solver Requirement: Must solve in milliseconds (e.g., 1-5 ms) for real-time control, using libraries like OSQP or qpOASES.
Inverse Dynamics
Inverse dynamics is the computation of the joint torques or forces required to produce a desired acceleration for a robot, given its kinematic structure, mass properties, and current state of motion. For a floating base system, this is an underdetermined problem because the base is unactuated. The solution requires solving for both the joint torques and the contact wrenches simultaneously, which is typically done using a QP formulation that incorporates the floating base dynamics as a constraint.
- Core Challenge: The six unactuated base degrees of freedom mean there is no unique solution without additional optimization criteria.
- Standard Approach: Solved as a QP that minimizes torque or contact force magnitudes while satisfying dynamics.
Ground Reaction Force (GRF) & Center of Pressure (CoP)
The Ground Reaction Force (GRF) is the force vector exerted by the ground on a robot's foot during contact. The Center of Pressure (CoP) is the point on the contact surface where the total GRF is considered to act. These are not inputs but critical outputs of the floating base dynamics. When solving for control, the GRFs at each foot must be computed to satisfy the system's momentum dynamics. The location of the aggregate CoP relative to the support polygon is a direct indicator of stability.
- Dynamic Role: GRFs are the primary external forces that appear on the right-hand side of the floating base dynamics equation.
- Stability Rule: For static stability, the CoP must remain within the support polygon. For dynamic stability, metrics like the Zero-Moment Point (ZMP) are used.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us