https://github.com/silanus23/hold_and_weld
ROS 2 framework for automated dual-arm robotic welding systems that perform holding and welding simultaneously.
https://github.com/silanus23/hold_and_weld
dual-arm-planar-manipulator industrial moveit2 robotics ros2 welding
Last synced: 3 months ago
JSON representation
ROS 2 framework for automated dual-arm robotic welding systems that perform holding and welding simultaneously.
- Host: GitHub
- URL: https://github.com/silanus23/hold_and_weld
- Owner: silanus23
- License: apache-2.0
- Created: 2025-12-23T13:50:20.000Z (6 months ago)
- Default Branch: main
- Last Pushed: 2026-03-03T23:10:50.000Z (3 months ago)
- Last Synced: 2026-03-04T02:22:54.956Z (3 months ago)
- Topics: dual-arm-planar-manipulator, industrial, moveit2, robotics, ros2, welding
- Language: Python
- Homepage:
- Size: 1.62 MB
- Stars: 4
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Hold and Weld
ROS 2 framework for automated dual-arm robotic welding systems that perform holding and welding simultaneously.
## Overview
A modular system for coordinating gripper and welding robots to autonomously manipulate and weld
workpieces. This repository currently targets **ROS 2 Jazzy**.
## Features
- Automated weld path generation from seam geometry and saving that as a json file
- Dual-robot coordination with collision avoidance
- Action-based architecture for flexible workflows
- Support for multiple joint types (T-joint, butt-joint, corner joint, lap joint, edge joint)
## Architecture
## Packages
- **hold_and_weld_description** - Robot URDFs, meshes, and models
- **hold_and_weld_planning** - Python tools for weld path generation and geometry processing
- **hold_and_weld_application** - C++ action servers and workflow coordination
## Design Philosophy
This project is designed with the following principles in mind:
- **Separation of concerns**
Planning, description, and application logic are split into independent packages to allow
iteration and testing without cross-coupling.
- **Action-driven orchestration**
Long-running and stateful robot operations are modeled as ROS 2 actions to support
feedback, cancellation, and extensibility.
- **Simulation-first development**
All core functionality is designed to be testable in simulation before deployment on real hardware.
- **Robot-agnostic extensibility**
The system aims to support different robot models and configurations with minimal code changes,
relying on URDF and configuration files rather than hardcoded assumptions.
- **Incremental autonomy**
Advanced components such as geometry reasoning and behavior trees are introduced progressively,
only after a stable execution pipeline is established.
## Planned Milestones
### Milestone 1 – Core Stability
- [ ] Realistic models for external-axis torch and gripper
- [ ] Action server for moving a robot to a target pose
- [ ] Utilize execute action messages instead only triggering ones.
- [ ] Making task yaml monolithic and main source for every package
- [ ] Replacing time based delay
### Milestone 2 – Configuration & Extensibility
- [ ] Guidelines for adding robots and jobs
- [ ] Test coverage for all supported weld joint types
- [ ] Adding reachability test by adding jacobian calculations
### Milestone 3 – Advanced Autonomy
- [ ] Behavior Tree–based task orchestration
- [ ] URDF-driven geometry engine
## Conceptual Design Notes (Future Work)
This section documents design considerations and architectural directions explored during development and is not a commitment to specific implementations.
### Geometry Engine
Currently the system can extract weld line coordinates and workpiece poses from URDFs alone.
This iteration depends on defining weld geometry from URDFs and only calculates flat surfaces.
Future work includes making this geometry independent from joint types, choosing non-colliding
orientations from multiple possibilities, extending to curved surfaces while maintaining
work/travel angles, and being able to work with mesh files. Eventually this system should be
capable of creating contemporary art installations with arbitrary weld geometries.
### Behavior Tree
Currently there is a `dual_robot_coordinator` node that is responsible for orchestrating nodes.
A behavior tree integration and making current action servers, node will help user to create
multiple step, arbitrary number of robot and object scenes. On top of this a behavior tree can
help user to create conditional check nodes to avoid failure situations of real life like a
gripping failure mid mission.
## Known Issues
- Currently gripper system is showing inconsistencies due to model problems.
- JSON system can create problems that can be solved by building from cache after creating json. This problem
will be solved by adding json parserer independent from colcon.
- Current version is tested in in butt_joint and T-joint only more test cases from contributors are welcomed
lap_joint's logic could be better in urdf generator.
## License
Apache-2.0
## Author
Berkan Tali (berkantali23@outlook.com)
GitHub: @silanus23