Development with robot control ROS 2 middleware
What led to the introduction of the service?
One of our customers had the following problem:
Due to the fact that the robotics middleware, ROS (Robot Operating System), has shifted to ROS 2, they sought to develop a product that uses ROS 2. However, generic devices did not yet support ROS 2, so they had to propose the in-house development of the system. In addition, since they are in the transition period from ROS to ROS 2, they looked into robot control using ROS and ROS 2 together.
Issues before introduction
Examples of use after introduction
As a medium to propose their own development, they were able to develop a demonstration product that realized robot control with ROS 2.
Effectiveness and achieved results
The issue of generic devices not supporting ROS 2 was resolved by making low-cost microcomputers costing less than 2,000 yen behave as ROS 2 nodes and turning them into IoT devices. In addition, by using the ros1_bridge package, they were able to propose a platform where ROS and ROS 2 can coexist. Using the ros1_bridge package, they are also currently transitioning from ROS to ROS 2.
System development knowledge
Achieving robot control using generic devices.