-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing the correct version of FastRTPS for ROS2 #19
Comments
Being addressed on scripts now, but should be simplified so to only get the |
@TSC21 @LorenzMeier I've been working on a new approach for this with @clalancette that leverages the ROS 2 typesupport packages and is working toward being more generic such that the agent does not have to hard code the topics and types. It works with the binary installed version of fastrtps. Could you take a look at: https://github.com/osrf/ros2_serial_example We're currently backwards compatible with your implementation but expect to add more features and robustness are planning to evolve the protocol. For example: osrf/ros2_serial_example#18 and add dynamic topic support: osrf/ros2_serial_example#13 instead of just having the yaml file defining the topics as we have now. |
@tfoote really interesting! Could it be something that could back the agent implementation on this package? Meaning a package that is added as a dependency of this package that then subscribes to the uorb data being published after serialized by CDR? |
Yes, at the moment it should be a drop in replacement for the agent in this package. |
Alright. I will take a look at it. Thank you |
This is already addressed on the containers and documentation. |
The install script for installing eProsima/FastRTPS installs the wrong version of FastRTPS for ROS Bouncy. (1.5.0 instead of 1.6.0) which causes
fastrtpsgen
to complain that it does not recognize the command line arguement-I
when you build the ros2 branch of px4_ros_com.For ROS2 Bouncy you should install 1.6.0 and for ROS2 Crystal you should install 1.7.0.
The text was updated successfully, but these errors were encountered: