-
Notifications
You must be signed in to change notification settings - Fork 227
Add a test to check if trajectory message is received #805
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
base: master
Are you sure you want to change the base?
Conversation
7d1e8ce
to
fc384b8
Compare
I had problems in my up-to-date rolling devcontainer to receive the topic, so I wrote a test for that. It seems that something changed in rclcpp/fastrtps on rolling making the send_trajectory node broken? Because it succeeds on jazzy here. @mikelikesrobots @sea-bass which environments did you use? |
I used Jazzy with CycloneDDS on my end. I almost never use FastDDS due to its reliability, and also due to the rename my binary install on my home PC actually makes my nodes crash if I use this middleware. (I've been too lazy to clean reinstall) |
Another thing to verify: Are there any QoS differences in the publisher/subscriber pair in this example's JTC uses so does the r6bot_controller :
... however, the example publisher does not: ros2_control_demos/example_7/reference_generator/send_trajectory.cpp Lines 28 to 29 in 1dc20c1
SystemDefaultsQos ?
|
yes there are, the I tried now with cyclone on rolling, with
I haven't rebuilt the stack, but that shouldn't be necessary? |
could be improved by checking if the robot actually moves