ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

The incompatibility is not just about a new version of the master. (So far most releases haven't changed the master). The primary reason for incompatibility of communication between versions of ROS is that the message definitions may have changed. Which is not something which can be trivially fixed. There are bag migration rules which could be applied in a python process and do translations, but maintaining support for arbitrary combinations of versions is a very large burden which we cannot support at the moment.

I would suggest that if you really need newFeatureX in an older platform that you backport newFeatureX to the older platform instead of trying to get both versions to be compatible. If you compile it against the older version of ROS that's great. The farther you diverge for the tested and integrated system the more effort it will require on your part.

Another solution which might be possible would be to create a translation node which can talk to both systems and republish communications from one to another. This might be possible in python with a lot of work, but I wouldn't recommend even trying.