aiofranka
Note: This repository was transferred from
Improbable-AI/aiofrankatoyounghyopark/aiofranka. Old links and git remotes redirect here automatically.
aiofranka is an asyncio-based Python library for controlling Franka Emika robots. It provides a high-level, asynchronous interface that combines pylibfranka for official low-level control interface (1kHz torque control), MuJoCo for kinematics/dynamics computation, Ruckig for smooth trajectory generation.
The library is designed for research applications requiring precise, real-time control with minimal latency and maximum flexibility.
Installation
Make sure you can access Franka Desk GUI from your machine's browser by typing in the robot's IP (e.g. 172.16.0.2). Then, install:
pip install aiofranka
This works on:
| Platform | Python |
|---|---|
| Linux x86_64, e.g. Ubuntu 22.04 or newer | 3.10 to 3.12 |
| Apple Silicon Mac with macOS 15 or newer | 3.10 to 3.14 |
To calibrate a camera against the robot (aiofranka camera), add the camera extra, which installs aiocamera and aprilcube:
pip install "aiofranka[camera]"
Or for development:
git clone https://github.com/younghyopark/aiofranka.git
cd aiofranka
pip install -e .
macOS (Apple Silicon)
On macOS, aiofranka installs pylibfranka-macos, an unofficial build of pylibfranka with macOS support from younghyopark/libfranka. It is not affiliated with Franka Robotics. To keep up with the 1 kHz control loop, it keeps one performance core busy while a control loop runs, so plug in the Mac when controlling the robot, and connect the robot via wired Ethernet.
Other Macs need pylibfranka built from source, see the libfranka macOS instructions.
Quick Start
There are two ways to use aiofranka:
Option A: Server mode
Run the 1kHz control loop in a subprocess. Your scripts use a simple sync API — no async/await needed.
- No
async/await— plain Python scripts, easy to integrate with existing codebases - Process-isolated — heavy computation (policy inference, camera processing) can't starve the 1kHz loop
- Automatic lifecycle — server subprocess starts with your script and stops when it exits
import numpy as np
import aiofranka
from aiofranka import FrankaRemoteController
# 1. Unlock the robot (opens brakes + activates FCI)
aiofranka.unlock()
# 2. Create controller and start server subprocess
controller = FrankaRemoteController()
controller.start()
# 3. Use the robot
controller.move([0, 0, 0.0, -1.57079, 0, 1.57079, -0.7853])
controller.switch("impedance")
controller.kp = np.ones(7) * 80.0
controller.kd = np.ones(7) * 4.0
controller.set_freq(50)
for cnt in range(100):
state = controller.state
delta = np.sin(cnt / 50.0 * np.pi) * 0.1
controller.set("q_desired", delta + controller.initial_qpos)
# 4. Stop server and lock robot
controller.stop()
aiofranka.lock()
The server subprocess terminates automatically when your script exits (Ctrl+C, crash, etc.), so it won't leave orphaned processes. controller.start() checks that the robot is unlocked and FCI is active before launching — if not, it prints a status summary and exits cleanly.
Option B: Async mode
Run the 1kHz control loop in-process using asyncio — everything in a single script.
- Single script — no separate server process, simpler deployment
- Direct access — no IPC overhead, full control over the event loop
- Requires async discipline — any blocking call >1ms after
controller.start()will causecommunication_constraints_violation(see Async Mode Guide)
import asyncio
import numpy as np
from aiofranka import RobotInterface, FrankaController
async def main():
robot = RobotInterface("172.16.0.2")
controller = FrankaController(robot)
await controller.start()
await controller.move([0, 0, 0.0, -1.57079, 0, 1.57079, -0.7853])
controller.switch("impedance")
controller.kp = np.ones(7) * 80.0
controller.kd = np.ones(7) * 4.0
controller.set_freq(50)
for cnt in range(100):
delta = np.sin(cnt / 50.0 * np.pi) * 0.1
init = controller.initial_qpos
await controller.set("q_desired", delta + init)
await controller.stop()
if __name__ == "__main__":
asyncio.run(main())
CLI Reference
The CLI handles robot setup, server lifecycle, and diagnostics.
aiofranka start-server [--ip IP] [--no-home] Start the control server
aiofranka unlock [--ip IP] Unlock joints + activate FCI
aiofranka lock [--ip IP] Lock joints + deactivate FCI
aiofranka gravcomp [--ip IP] [--damping] Gravity compensation (freedrive)
aiofranka home [--ip IP] Move the robot to its home pose
aiofranka status [--ip IP] Show robot & server status
aiofranka stop [--ip IP] Stop a running server
aiofranka mode [--ip IP] [program|execute] View/change operating mode
aiofranka config [--ip IP] [--mass M] View/set the active end-effector profile
aiofranka tool identify|load|unload|list|remove Identify and switch tools
aiofranka camera calibrate|fit Locate a fixed camera relative to the robot
aiofranka selftest [--ip IP] [--force] Run safety self-tests
aiofranka log [-n LINES] [-f] View server logs
aiofranka gripper --open|--close Control the Robotiq gripper
aiofranka rt-benchmark [--duration SEC] Benchmark the 1 kHz control loop
unlock / lock
Unlock opens the brakes and activates FCI so the robot is ready for torque control. It first recovers safety errors, runs the self-tests if they are overdue, and switches from Programming back to Execution. Lock does the reverse. Credentials are prompted on first use and saved to ~/.aiofranka/config.json.
# Unlock before running your script
aiofranka unlock
# Lock when you're done
aiofranka lock
You can also do this from Python:
import aiofranka
aiofranka.unlock() # opens brakes + activates FCI
# ... run your control script ...
aiofranka.lock() # closes brakes + deactivates FCI
gravcomp
Runs gravity compensation mode in the foreground. The robot is freely movable by hand. Press Ctrl+C to stop control; the joints remain unlocked with FCI active. Run aiofranka lock when finished.
aiofranka gravcomp # default: zero damping
aiofranka gravcomp --damping 2.0 # add velocity damping
status
Shows robot state (joints locked/unlocked, FCI active/inactive, control token, self-test status, the active end-effector profile) and server status if running.
aiofranka status
stop
Sends a shutdown signal to a running server process. The server deactivates FCI, locks joints, and releases the control token.
aiofranka stop
mode
View or change the operating mode. Execution is needed for FCI control. Programming enables freedrive via the pilot interface button near the end-effector, as Desk's mode switch does: aiofranka mode program deactivates FCI, opens the brakes if they are closed, and hands the control token back to Desk. aiofranka unlock switches back to Execution by itself.
aiofranka mode # view current mode
aiofranka mode program # switch to Programming, to hand-guide the robot
aiofranka mode execute # switch back to Execution, for FCI
config
View or set the end-effector configuration (mass, center of mass, inertia, flange-to-EE transform). Changes are applied via the Franka Desk API to the active end-effector profile; to keep several tools by name, use aiofranka tool.
aiofranka config # view current config
aiofranka config --mass 0.5 --com 0,0,0.03 # set mass + CoM
aiofranka config --translation 0,0,0.1 # set flange-to-EE offset
tool
Desk keeps named end-effector profiles (Settings > End Effector): the mass, center of mass and inertia of the tool on the flange. The robot compensates the gravity of the active profile, and aiofranka merges it into the MuJoCo model when it connects, so the OSC's mass matrix includes the tool too.
aiofranka tool identify gripper # identify the mounted tool, save it as profile "gripper", activate it
aiofranka tool load gripper # activate a profile when its tool is mounted
aiofranka tool unload # activate the built-in "No End Effector" profile
aiofranka tool list # list the profiles, marking the active one
aiofranka tool remove gripper # delete a profile
tool identify moves the robot through 16 poses around the current one (about 3 minutes), approaching each from both sides to cancel joint stiction, and fits the mass and center of mass to the joint torques at rest. Start in an open pose and keep a hand on the e-stop. The poses are checked for collisions of the arm, a cylinder around the tool (--tool-length, --tool-radius, default 0.2 m by 0.1 m) and the floor (--floor, default the mounting plane). It shows the estimate and asks before saving it, offering to edit the mass and center of mass, e.g. to enter a scale reading.
The inertia and the TCP cannot be identified this way; set them in the Desk web UI if needed. Tools lighter than about 200 g are better weighed: the center of mass then comes out only to about a centimeter.
From Python (async mode):
estimate = await controller.identify_payload(tool_length=0.2) # moves the robot
aiofranka.save_tool("gripper", estimate.mass, estimate.com)
aiofranka.load_tool("gripper")
camera
Locates a fixed camera in the robot's base frame, for example to track objects in the robot's coordinates. The arm holds an AprilCube on its flange: print aprilcube's calibration cube (cube.3mf, 1x3x3 with 24 mm tags) and mount it with its connector. Start the camera with aiocamera start, set the cube's mass as the active Desk profile (aiofranka tool identify), then:
aiofranka camera calibrate # move the arm by hand; captures and fits into camera_calibration/<date>/
aiofranka camera fit camera_calibration/20261003_150000 # fit a recorded session again
camera calibrate puts the arm in gravity compensation with light damping (--damping, default 1 Nm s/rad) and shows a live view of the camera image in the terminal: the cube in view, the views captured so far, and which image regions still have none. Move the arm by hand and let it rest: whenever it has been still for 0.7 s at a new pose, at least 5 cm or 10 deg from every captured one, with the cube in view, it records the cube's tag corners in a fresh frame with the flange pose and beeps. Space captures anyway, u removes the last view, q quits keeping the views. Aim for 15 to 25 views spread over the image, near and far, with the wrist turned 20 to 40 deg about at least two axes. Enter fits.
The fit finds the camera's pose in the base frame and the cube's on the flange that best reproject the cube's corners in every view, with the stream's factory intrinsics fixed. Every fifth view is held out of a first fit to report the error on views it has not seen. The session folder keeps views.json and the images, so camera fit can refit it, and calibration.json holds T_base_camera (meters; camera axes right, down, forward), T_ee_cube, the intrinsics and the errors. The camera is the only RealSense color stream in aiocamera unless --stream names one; --cube takes another AprilCube's config.json.
selftest
Run the robot's safety self-tests. The robot will lock joints during the test.
aiofranka selftest # run if due
aiofranka selftest --force # run even if not due
log
View recent server log entries from ~/.aiofranka/server.log.
aiofranka log # last 20 lines
aiofranka log -n 100 # last 100 lines
aiofranka log -f # follow (like tail -f)
Common flags
Most commands accept these flags:
| Flag | Description |
|---|---|
--ip IP |
Robot IP address (default: last used, or 172.16.0.2) |
--username USER |
Franka Desk web UI username (default: saved or prompted) |
--password PASS |
Franka Desk web UI password (default: saved or prompted) |
--protocol http|https |
Web UI protocol (default: https) |
Core Concepts
Server Mode vs Async Mode
| Server mode | Async mode | |
|---|---|---|
| Class | FrankaRemoteController |
FrankaController |
| API style | Synchronous (plain Python) | async/await |
| 1kHz loop runs in | Subprocess (auto-managed) | Your process (asyncio task) |
| Blocking calls OK? | Yes — can't starve the loop | No — must stay under ~1ms |
| State reads | Shared memory (zero-copy) | Direct attribute access |
| Commands | ZMQ IPC (msgpack) | Direct method calls |
| Setup | unlock() + ctrl.start() |
Single script |
| Best for | Heavy workloads (GPU inference, vision pipelines) | Lightweight scripts, rapid prototyping |
Rate Limiting
Use set_freq() to enforce strict timing for command updates:
controller.set_freq(50) # Set 50Hz update rate
# This will automatically sleep to maintain 50Hz timing
for i in range(100):
controller.set("q_desired", compute_target())
State Access
Robot state is continuously updated at 1kHz and accessible via controller.state:
state = controller.state # Thread-safe access
# Contains: qpos, qvel, ee, jac, mm, last_torque
print(f"Joint positions: {state['qpos']}")
print(f"End-effector pose: {state['ee']}") # 4x4 homogeneous transform
Controllers
1. Impedance Control (Joint Space)
Controls joint positions with spring-damper behavior:
controller.switch("impedance")
controller.kp = np.ones(7) * 80.0 # Position gains
controller.kd = np.ones(7) * 4.0 # Damping gains
controller.set("q_desired", target_joint_angles)
Use case: Precise joint-space motions, compliant behavior
2. Operational Space Control (Task Space)
Controls end-effector pose in Cartesian space:
controller.switch("osc")
controller.ee_kp = np.array([300, 300, 300, 1000, 1000, 1000]) # [xyz, rpy]
controller.ee_kd = np.ones(6) * 10.0
desired_ee = np.eye(4) # 4x4 homogeneous transform
desired_ee[:3, 3] = [0.4, 0.0, 0.5] # Position
controller.set("ee_desired", desired_ee)
By default, the OSC controls the flange. To control a point on the tool instead, set the tool center point (TCP) as a translation or a 4x4 pose in the flange frame (async mode, FrankaController):
controller.switch("osc")
controller.set_tcp([0, 0, 0.1034]) # e.g. the Franka Hand fingertips; the arm holds still
The flange frame has its origin at the center of the flange face and z pointing out of it (x red, y green, z blue; right: a TCP 10 cm along z):
Use case: Cartesian trajectories, end-effector tracking
License
aiofranka's original code is available under the MIT License; see LICENSE. The bundled FR3 model and meshes retain their upstream Apache-2.0 and BSD-3-Clause terms in aiofranka/model/LICENSE.
Citation
If you use this library in your research, please cite:
@software{aiofranka,
author = {Park, Younghyo},
title = {aiofranka: Asyncio-based Franka Robot Control},
year = {2025},
url = {https://github.com/younghyopark/aiofranka}
}
Acknowledgments
Metadata
Release files for aiofranka 0.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| aiofranka-0.6.1.tar.gz | 6.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aiofranka-0.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.4 MB
Release files / aiofranka-0.6.1.tar.gz
| Download URL | aiofranka-0.6.1.tar.gz |
|---|---|
| Size | 6.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb0fea6da1cb3610dc5b9a546d6a34af3cc69744cb5fa3895bf15e9c32e2ccf8
|
|
BLAKE2b-256 checksum How to use checksums |
f89f665e442475956e33ca9528228d571dd2dbb937b24c2928c81299d825faba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Release files / aiofranka-0.6.1-py3-none-any.whl
| Download URL | aiofranka-0.6.1-py3-none-any.whl |
|---|---|
| Size | 6.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a4416c7e3b3babfae521a04e12832abe79bfbc95e37c2fa423b8ab001920c4a4
|
|
BLAKE2b-256 checksum How to use checksums |
090db6ab5e431448958128f88bd36f41327280a02c781e47f91472d849c782d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|