THE USEFUL PART
- Qualcomm announced an intention to acquire PickNik; do not read that as confirmation of a completed deal.
- Isaac ROS 5.0 is a developer release, not an automatic capability upgrade for every robot.
- Check the exact operating system, hardware and driver combination before changing a working installation.
September 23 and 28: Qualcomm and PickNik
The most consequential robot news is sometimes about the software between a command and a moving arm. Qualcomm announced its intention to acquire PickNik on September 23. In its September 28 response, Open Robotics welcomed the proposal and reported assurances that MoveIt would remain open. These are statements about the planned transaction and future support, not evidence that the acquisition has closed.
For an owner or lab, our practical question is narrower than the corporate headline: who maintains the version that your robot actually runs? Record the package, release, licence and support contact. Keep a separate entry for any paid integration or service. An open project and a commercial support agreement answer different ownership questions.
September 22: Isaac ROS 5.0
NVIDIA released Isaac ROS 5.0 at ROSCon in Toronto on September 22. Its announcement describes GPU-accelerated packages, support for ROS Lyrical and agent-oriented setup and manipulation workflows. Open Robotics also published a same-day account of the release and the collaboration behind it. The news concerns tools for building robot applications; it does not establish that an existing consumer robot can install them.
Start with the release documentation for the specific camera, compute board and driver you intend to use. Our suggested first experiment is a recorded sensor input with a known expected output. Only then move to a controlled physical task. This makes a software change easier to assess without confusing a successful installation with useful robot behaviour.
September 22: a broader ROS platform choice
The Open Source Robotics Alliance announced Tier 1 support for Red Hat Enterprise Linux and Tier 3 support for Fedora. Its explanation distinguishes the higher tier by continuous integration, packaging and prioritised maintenance. That is a support-policy development. Readers still need the platform matrix for their chosen ROS distribution; the announcement is not a compatibility promise for every robot or every historical release.
If your supplier supports one tested image, ask whether moving to a different distribution changes that support. There is little value in a newer platform if the camera driver or recovery procedure your project needs is missing. Treat a platform migration as its own decision, with a reason, an owner and a route back to the working setup.
What to do with this news
Keep a short before-and-after record: the task, current software versions, supported hardware, expected improvement and one repeatable check. If you cannot name a useful change, bookmark the announcement and leave the working system alone. For a new purchase, request the same information from the supplier before choosing a robot simply because its product page mentions ROS.
This briefing was published and source-checked on October 3, 2026. It covers the dated September announcements above, not a hands-on benchmark or a complete survey of robotics news. Use our software-record worksheet as the next step. The linked robot profiles offer ownership context and do not imply that these releases have been tested on those models.