ros2_kortex
- Software
- Robot arms and industry
- Driver or SDK
ROS 2 package to control Kinova Gen3 and Gen3 lite robot arms through the Kortex API, with URDF models, drivers, and MoveIt configurations.
- Closed core
Made by Kinova Robotics, Canada (checked on github.com/Kinovarobotics (opens in a new tab)).
Source on GitHub: github.com/Kinovarobotics/ros2_kortex (opens in a new tab). Facts read at commit b2aa46b (opens in a new tab).
Licenses
- Code
- BSD-3-Clause (opens in a new tab)
Read by Robotheca from LICENSE (opens in a new tab) (BSD-3-Clause) at commit b2aa46b (opens in a new tab), on 16 Oct 2026.
- Commercial use
- Unknown
It needs closed parts under their own terms: read them before any commercial use.
One part it needs is closed
- Needs KINOVA KORTEX API (prebuilt): The kortex_api package downloads the API as a prebuilt library from Kinova's server during the build (kortex_api/CMakeLists.txt); its source is not in the repository.
Labels
- Closed coreIt needs closed parts: KINOVA KORTEX API (prebuilt).
What it does
- Provides the official ROS 2 interface to Kinova Kortex robots, built on the Kortex API.
- Includes URDF and mesh descriptions for Gen3 and Gen3 lite arms with optional Robotiq grippers.
- Its driver node communicates with a physical Gen3 or Gen3 lite robot over the network.
- Offers launch files for bringup on real hardware or with fake hardware, and Gazebo simulation.
- Ships MoveIt 2 configurations for motion planning with Gen3 and Gen3 lite arms.
- Can command the arm via joint trajectory messages or Twist messages through a twist controller.
Written by Robotheca from the project's README (opens in a new tab) at commit b2aa46b.
Getting started
- Difficulty
- Intermediate
- How to start
- The project's README (opens in a new tab)
Maintenance
- Status
- Active: a commit in the last 90 days
- Newest commit
- 18 Sept 2026 on main
- Latest release
- None published on GitHub
Checked on GitHub on 16 Oct 2026.
Links
Robots on Robotheca that use it
No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.
Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.