Skip to content
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

rviz does not start when using RTI Connext #916

Closed
AndreasAZiegler opened this issue Jul 9, 2019 · 7 comments
Closed

rviz does not start when using RTI Connext #916

AndreasAZiegler opened this issue Jul 9, 2019 · 7 comments
Assignees
Labels
1 - High High Priority bug Something isn't working
Milestone

Comments

@AndreasAZiegler
Copy link

Bug report

Required Info:

  • Operating System:
    • Ubuntu 18.10
  • Installation type:
    • binaries
  • Version or commit hash:
  • DDS implementation:
    • RTI Connext

Steps to reproduce issue

Expected behavior

Rviz starts

Actual behavior

I get the following console output

andreasziegler@AndreasZiegler:~/ros/ros2_turtlebot3_ws$ ros2 run rviz2 rviz2 -d $(ros2 pkg prefix nav2_bringup)/share/nav2_bringup/launch/nav2_default_view.rviz
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-andreasziegler'
[INFO] [rviz2]: Stereo is NOT SUPPORTED
[INFO] [rviz2]: OpenGl version: 4.6 (GLSL 4.6)
[INFO] [rviz2]: Stereo is NOT SUPPORTED

Stack trace is attached.
my_log_file.txt

@crdelsey
Copy link
Contributor

crdelsey commented Jul 9, 2019

@AndreasAZiegler We have briefly tried RTI Connext and found there are limits in that DDS implementation that prevent us from creating enough nodes to run the full navigation stack. I believe that is what is happening in this issue and #915

I will try to reproduce this with a simplified example and file this upstream.

A few questions to make sure I have the same configuration:

  1. What type of license are you using? Is it the 30 day trial?
  2. Have you made any configuration changes to connext?
  3. Are you running with the ROS_DOMAIN_ID environment variable set to avoid interference with others on your network?

@crdelsey crdelsey self-assigned this Jul 9, 2019
@crdelsey crdelsey added 1 - High High Priority bug Something isn't working labels Jul 9, 2019
@crdelsey crdelsey added this to the July 2019 milestone Jul 9, 2019
@AndreasAZiegler
Copy link
Author

  1. We have a commercial license from rti but I used the normal debian package (and copied our license file)
  2. No
  3. No, I did not set ROS_DOMAIN_ID as I was not aware of this. How can I use this? As we have quite a lot of other devices using plain rit Connext DDS it could actually be worth a try.

@crdelsey
Copy link
Contributor

Here's the info on ROS_DOMAIN_ID https://index.ros.org/doc/ros2/Contributing/ROS-2-On-boarding-Guide/#choose-a-dds-domain-id

We ran into problems with that. Each developer would interfere with the others on the network producing strange results.

@SteveMacenski
Copy link
Member

@AndreasAZiegler @crdelsey this ticket doesn't seem to directly relate to this project, can we close or redirect the issue to the appropriate projects (Rviz)?

@AndreasAZiegler
Copy link
Author

I'm fine if someone redirects this issue to the appropriate project. In case someone following this issue comes up with a solution I would be glad if he/she would write about the solution here (as well).

@mkhansenbot
Copy link
Collaborator

@AndreasAZiegler - I think this is a duplicate of this issue:
ros2/rviz#437

@SteveMacenski
Copy link
Member

@mkhansen-intel so it is, closing here then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - High High Priority bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants