Backend
Keeping the Franka Emika Panda alive: a ROS 2 stack with a reliable position interface
arXiv cs.RO0 views
arXiv:2608.19740v2 Announce Type: replace Abstract: This paper presents an open-source software stack that restores ROS 2 support for the Franka Emika Panda robot while resolving the long-standing unreliability of its external position control interface. We first analyze the root causes of unstable position control and show that the observed vibrations and protective stops arise from the timing of the external control loop and sampling jitter, rather than from limitations of the robot itself. Building on this analysis, we introduce an asynchronous hardware interface that decouples real-time communication from the ROS 2 control loop, a rate-matching mechanism for slower command sources, and a position-domain reference generation strategy that produces reliable, smooth position commands. Experimental validation shows that the proposed architecture reliably tracks velocity references by reducing motion artifacts introduced by the official implementation, and the stack is validated across motion planning, compliance control, position-controlled manipulation, and haptic teleoperation on two independent Panda platforms. By restoring a modern, reliable, and open ROS 2 ecosystem for the Panda, this work lowers the barrier to developing safe, responsive, and reproducible human-robot collaboration applications that integrate planning, perception, interaction, and shared autonomy. Code and videos are available on our website at https://sites.google.com/unisa.it/fer-ros2.
Source:https://arxiv.org/abs/2608.19740PreviousAdaptive-WAM: Quality-Guided Early-Exit Planning from Intermediate Video-Diffusion FeaturesNextLearning and Transferring Closed-Loop Robot Software
Related posts
Kubernetes Multi-Tenancy: Designing a Shared Cluster
0dev.to

Your Login Works. Now Prove Who Did What
0dev.to
Our Customers Received Fake Delivery Texts in the Same Thread as Our Real Ones
0dev.to
Your New Contract Says You Cannot Join a Competitor for a Year
0dev.to
Our "tell us what you'd pay" form sends nothing to the client, and the price in the answer is resolved on the server
0dev.to
We started shipping to Norway and Ansible wrote it into our config as false
0dev.to