Open Source RoboticsRobots, software & learning

libfranka

Software

C++ control and communication library for Franka robots, with Python bindings and distribution-specific installation routes. [1] [3]

Installation & first result →Official websiteGetting started

For
Developers with access to supported Franka hardware and knowledge of robot control [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

libfranka supplies a C++ control and communication interface for Franka robots, with Python bindings also documented in the repository. It is source for an interface to purchased hardware, not a manufacturing design or an open release of the robot's firmware. Start with the robot system and compatible library version before choosing a package or running a control example. [1] [3]

Is this for you?

Known limitations
  • Open library source does not establish openness of purchased robot hardware or firmware.
  • The README Debian example version is not proof of the latest available or compatible release.
  • No real-time kernel/network setup, upstream compilation, device connection or control loop was tested.

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

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

What you need

Dependencies
  • Selected README documents Ubuntu20.04/22.04/24.04/26.04 routes
  • CMake>=3.22 for the main documented source route
  • Linux PREEMPT_RT kernel recommended for real-time control

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

Installation & first result

Open the upstream getting-started guide [1]

  • Select the robot-system-compatible library release and Ubuntu package route; inspect network and real-time host configuration before using control examples.
  • 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] · Editorial assessment

Installation

Select the robot-system-compatible library release and Ubuntu package route; inspect network and real-time host configuration before using control examples.

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

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

Hardware, models & data

Inputs and outputs

Franka robot state and control callback commands through the library communication interface.

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

[1] [3] · Editorial assessment

Project notes

Select the host and package route

The selected README describes Ubuntu 20.04, 22.04, 24.04 and 26.04 routes, recommends a PREEMPT_RT Linux kernel for real-time control and names CMake 3.22 or later for its main source-build instructions. Its Debian-package example uses libfranka 0.19.0 on Jammy. That example is an installation illustration, not proof that 0.19.0 is the latest release or the right version for an arbitrary robot system. [1]

First match the robot-system version in the upstream Robot System Version Compatibility matrix before choosing a package. This review has not established a specific robot-system/library pairing. The README requires a Franka robot with the FCI feature installed and recommends a 1000BASE-T Ethernet connection. Its listed Debian packages target amd64 and are its recommended installation route. [1]

The source route additionally names GCC 9 or later and dependency/patch preparation; selecting it is more involved than installing the matched prebuilt package. Follow the linked real-time setup guidance for the chosen host. Package installation alone would not establish that a computer meets controller timing or physical safety requirements. No package, network or real-time host was configured here. [1]

Inspect an actual interface, not just the examples

The selected Robot implementation constructs a network-backed robot connection and guards against conflicting control/read ownership. This establishes implementation source for the interface. It does not verify a network connection, error recovery or control-loop operation on hardware. Keep those tests separate from reading example motion code. [3]

The repository declares Apache-2.0 for its software. Purchased robot hardware, firmware and any other system components have separate terms. This profile records source requirements and limits only: no upstream compilation, robot connection, real-time loop, motion or powered test was performed. [1] [2]

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
e88d08f

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 · Apache-2.0
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 · Apache-2.0
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