If you work in robotics, you know the drill.
You spend weeks designing a beautiful, mechanically sound robot in CAD. Then, you need to simulate it in Gazebo or control it with ROS 2.
Suddenly, your engineering masterpiece becomes a nightmare of XML tags. You are staring at a robot.urdf file at 2 AM, trying to figure out why your inertia tensor has negative diagonal values, why your LiDAR is floating three meters above the chassis, or why your generic <ros2_control> hardware interface is throwing errors.
We’ve all been there. The gap between Visual Rigging and Mathematical Kinematics is the most frustrating bottleneck in robotics simulation.
That’s why I built LinkForge: The Linter & Bridge for Robotics.
What is LinkForge?
LinkForge is an open-source ecosystem designed to turn Blender 4.2+ into a production-grade robotics IDE.
It allows you to model your robot as naturally as sculpting a 3D scene, while acting as a strict safety net to guarantee the output is rigorous, mathematically sound code ready for ROS 2 and Gazebo.
Instead of writing XML, you use a native Blender interface to:
- Define Physics: Automatically calculate perfect mass properties and inertia tensors for complex arbitrary meshes.
- Attach Sensors: Visually place Cameras, LiDARs, IMUs, and Contact sensors.
- Configure Control: Set up
ros2_controlCommand and State interfaces (Position, Velocity, Effort) directly on your joints. - Lint & Export: Catch simulation-breaking errors before you export your final URDF/XACRO.
Why not just use existing exporters?
There are a few historical URDF exporters for Blender and SolidWorks. However, as ROS 2 has matured, the requirements for simulation have become stricter.
LinkForge was built completely from scratch with a Hexagonal Architecture to solve three major problems with older tools:
1. The "Garbage In, Garbage Out" Problem
Older exporters blindly translate whatever is in your 3D viewport into XML. If you accidentally detach a link, or if your collision mesh causes a physics engine singularity, you won't find out until Gazebo crashes.
LinkForge introduces The Linter for Robotics. Before it lets you export, the core Python engine validates your kinematic graph. It catches negative inertias, circular dependency chains, and invalid joint limits instantly.
2. Native ros2_control Generation
Writing <ros2_control> blocks by hand is tedious. LinkForge includes a dedicated control dashboard. You simply check the joints you want to actuate, choose your interfaces, and LinkForge generates the perfect, standard-compliant XACRO macros for your hardware interfaces.
3. Headless CI/CD Capabilities
Because LinkForge uses a Hexagonal Architecture, the core engine (linkforge-core) is completely decoupled from the Blender UI.
While artists and engineers use the Blender add-on visually, you can also install the core engine locally on your Linux CI/CD servers. You can run automated tests to validate the physics of your robot models every time someone opens a Pull Request on your repository! (And yes, an official standalone PyPI package is on our near-term roadmap!)
Fully Open Source (And Seeking Contributors!)
LinkForge is built by roboticists, for roboticists. We are licensed under GPLv3 to ensure the tool remains forever free and community-driven.
Whether you are building a simple differential drive robot for a university project, or a complex quadruped for research, LinkForge will save you hours of XML debugging.
Try it out today:
- Check out the GitHub Repository. If you find it useful, I’d be honored if you left a Star ⭐!
- Read the Official Documentation & Tutorials.
- Download it directly inside Blender via the Get Extensions menu!
If you are a Python or Rust developer interested in kinematics, or if you just have ideas on how to improve the URDF workflow, we are actively looking for contributors to help shape our upcoming roadmap (which includes SRDF Support!). Come say hi in our GitHub Discussions!
Let's stop hand-coding XML, and get back to building robots. 🤖✨
Top comments (0)