Revision history [back]

there is currently no explicit command line tool which converts from ros1 to ros2. however, the current rosbag2 cli allows to replay ros1 bag files and can thus be used to record a new ros2 bag file based on the replay of ros1.

you can find a bit of documentation here on how to replay ros1 bag files: https://github.com/ros2/rosbag2/tree/master/rosbag2_bag_v2_plugins

that being said, the api is functional enough to replay ros1 bag files and i believe it shouldn't be too hard to develop a real conversion tool for it based on that API.

there is currently no explicit command line tool which converts from ros1 to ros2. however, the current rosbag2 cli allows to replay ros1 bag files and can thus be used to record a new ros2 bag file based on the replay of ros1.

you can find a bit of documentation here on how to replay ros1 bag files: https://github.com/ros2/rosbag2/tree/master/rosbag2_bag_v2_pluginshttps://github.com/ros2/rosbag2/tree/1a3782d81cc34f2f279b16cb75df7f71a1a86851/rosbag2_bag_v2_plugins

that being said, the api is functional enough to replay ros1 bag files and i believe it shouldn't be too hard to develop a real conversion tool for it based on that API.

there is currently no explicit command line tool which converts from ros1 to ros2. however, the current rosbag2 cli allows to replay ros1 bag files and can thus be used to record a new ros2 bag file based on the replay of ros1.

you can find a bit of documentation here on how to replay ros1 bag files: https://github.com/ros2/rosbag2/tree/1a3782d81cc34f2f279b16cb75df7f71a1a86851/rosbag2_bag_v2_pluginshttps://github.com/ros2/rosbag2/blob/1a3782d81cc34f2f279b16cb75df7f71a1a86851/rosbag2_bag_v2_plugins/README.md

that being said, the api is functional enough to replay ros1 bag files and i believe it shouldn't be too hard to develop a real conversion tool for it based on that API.

there is currently no explicit command line tool which converts from ros1 to ros2. however, the current rosbag2 cli allows to replay ros1 bag files and can thus be used to record a new ros2 bag file based on the replay of ros1.

you can find a bit of documentation here on how to replay ros1 bag files: https://github.com/ros2/rosbag2/blob/1a3782d81cc34f2f279b16cb75df7f71a1a86851/rosbag2_bag_v2_plugins/README.md

that being said, the api is functional enough to replay ros1 bag files and i believe it shouldn't be too hard to develop a real conversion tool for it based on that API.

there is currently no explicit command line tool which converts from ros1 to ros2. however, the current rosbag2 cli allows to replay ros1 bag files and can thus be used to record a new ros2 bag file based on the replay of ros1.

you can find a bit of documentation here on how to replay ros1 bag files: https://github.com/ros2/rosbag2_bag_v2/blob/master/README.md

In order to use the plugins, again, the ROS 1 installation must be sourced before sourcing the ROS 2 installation. You can then just use the plugin through the regular interface. For instance, on the command line write: write:

For playing, one can similarly write: ... ros2 bag play -s rosbag_v2 <path_to_bagfile> If there is ROS 1 data where no topic matching exists to ROS 2 these topics are ignored when replying. When calling ros2 bag info, one can see a list of mismatching topics: ...

that being said, the api is functional enough to replay ros1 bag files and i believe it shouldn't be too hard to develop a real conversion tool for it based on that API.

there is currently no explicit command line tool which converts from ros1 to ros2. however, the current rosbag2 cli allows to replay ros1 bag files and can thus be used to record a new ros2 bag file based on the replay of ros1.

you can find a bit of documentation here on how to replay ros1 bag files: https://github.com/ros2/rosbag2_bag_v2/blob/master/README.md

In order to use the plugins, again, the ROS 1 installation must be sourced before sourcing the ROS 2 installation. You can then just use the plugin through the regular interface. For instance, on the command line write:

interface. ... For playing, one can similarly write: ... ros2 bag play -s rosbag_v2 <path_to_bagfile> If there is ROS 1 data where no topic matching exists to ROS 2 these topics are ignored when replying. When calling ros2 bag info, one can see a list of mismatching topics: ...

that being said, the api is functional enough to replay ros1 bag files and i believe it shouldn't be too hard to develop a real conversion tool for it based on that API.

there is currently no explicit command line tool which converts from ros1 to ros2. however, the current rosbag2 cli allows to replay ros1 bag files and can thus be used to record a new ros2 bag file based on the replay of ros1.

you can find a bit of documentation here on how to replay ros1 bag files: https://github.com/ros2/rosbag2_bag_v2/blob/master/README.md

In order to use the plugins, again, the ROS 1 installation must be sourced before sourcing the ROS 2 installation. You can then just use the plugin through the regular interface. ... ...

For playing, one can similarly write: write:

ros2 bag play -s rosbag_v2 <path_to_bagfile>
 

If there is ROS 1 data where no topic matching exists to ROS 2 these topics are ignored when replying. When calling ros2 bag info, one can see a list of mismatching topics: ...

that being said, the api is functional enough to replay ros1 bag files and i believe it shouldn't be too hard to develop a real conversion tool for it based on that API.