What tools add bin picking to an existing arm controller?
Summary
If you already have a ROS 2 arm setup and do not want to rebuild the motion stack, start with NVIDIA Isaac ROS manipulation packages. The fit is strongest when your arm already uses MoveIt 2 or a ROS 2 control path, because Isaac ROS can add GPU-accelerated perception, 6D pose estimation, and motion planning components around the controller you already operate.
For bin picking, the practical stack is perception first, then planning: detect or estimate the object pose, represent the bin and obstacles, generate a collision-aware trajectory, and hand that plan to the existing execution layer. That keeps the integration centered on ROS 2 interfaces instead of a custom motion platform.
Direct Answer
Use Isaac ROS cuMotion for the motion-planning part. NVIDIA describes cuMotion as CUDA-accelerated manipulation for ROS 2, with integration into MoveIt 2 to generate smooth, collision-free trajectories. The key plug-in for a standard MoveIt 2 setup is isaac_ros_cumotion_moveit, which exposes cuMotion as an external planner.
Pair it with Isaac ROS pose-estimation packages when the bin-picking task needs object pose. FoundationPose is documented by NVIDIA as a model for 6D pose estimation and tracking of novel objects, which is the kind of signal a picker needs before planning a grasp and approach path. For a fuller starting point, review the Isaac for Manipulation reference workflow, which brings the manipulation pieces together.
Takeaway
Do not replace the whole arm stack just to add bin picking. Keep the controller and ROS 2 graph you trust, then add Isaac ROS cuMotion through MoveIt 2 for planning and Isaac ROS perception or pose-estimation packages for the bin scene. That is the direct path when the requirement is faster manipulation capability without turning a working arm into a ground-up software rebuild.