ROS 2 Dashing and Gazebo

4 次查看（过去 30 天）
Robert Corby
Robert Corby 2020-12-2
移动：Jagadeesh Konakalla 2024-7-8
Hi,
I am doing the installation of the ROS 2 Dashing and Gazebo as seen here
I am wokring on windows and have the VM installed and sucessfully have the ros_melodic_dashing_gazebov9.vmx operating.
When trying to use the worlds on my desktop, they simply open a terminal windows for a split second and then close again. It seems that they crash or Gazebo runs into issues and fails to open any of the worlds.
I have also tried this in conjunciton with the differetial drive example here . Which indicates to use
export SVGA_VGPU10=0
before opening the world, however this does not work either.
Any suggestions as to what is the problem?
Thanks,
Rob
  8 个评论
显示 6更早的评论
Robert Corby
Robert Corby 2020-12-3
It baffles me!
I had actually come across that forum posting, that you liked, already and it didn't work for me.
Is there other methodsof launching these shortcuts or world files that I should try?
I attempted to launch some of the other shortcuts straight off the desktop and also using the shell commands:
Gazebo Office. desktop shortcut launch:
However, using the shell commands, it launched just fine!
Then I ran it a second time with the desktop shortcut and it too launched perfectly? I am baffled hahaha
An interesting trial was with the 'Gazebo Warehouse Robot' which actually is my goal world to run as this is the model I am trying to control.
When running using the desktop shortcut, it simply flashes a terminal window for a few second and closes again.
However, using the individual shell commands, Gazebo launches for a brief moment (nothing renders) but a multitude of warnings display in the terminal:
I do not know personally, what these warnings mean.
My VM is using 4.3GB of Memory, 3 Processors, Display has been used both with accelerated 3d graphics and without and seems to perfrom better with it activated.
This is a tough problem!
Rob
Robert Corby
Robert Corby 2020-12-3
Should I be worried about this?

请先登录，再进行评论。

请先登录，再回答此问题。

回答（1 个）

Cam Salzberger
Cam Salzberger 2020-12-4
移动：Jagadeesh Konakalla 2024-7-8
The "roscore" not found error is the correct behavior for the default terminal, actually. ROS needs to be "sourced" to put its various tools and libraries on the path, but you generally shouldn't have both ROS and ROS 2 sourced in the same terminal (except if you are going to use ros1_bridge). So if you want to access the ROS functionality, use the "ROS Melodic Terminal" shortcut instead of the default terminal, which will source the right folder for you. If you want to use ROS 2, you can call:
source /opt/ros/dashing/setup.bash
Those error messages with Gazebo are not supremely helpful either. In the Gazebo Office world output, you should be able to safely ignore the complaint about "rosdep". I see that output as well, but it has no impact. The error that Gazebo is giving just seems to be an irregular crash that some people experience more than others. I've seen a couple of similar posts here and here, so you could try their suggested workarounds.
Also, since the error is so generic, it would probably help to take a look at the log files mentioned to see if there is anything there that stands out.
At this point, you probably need more direct assistance. I'd suggest contacting Tech Support with all of the error messages (copied as text instead of images, if possible) and log files. They should be able to provide more in-depth assistance.
If you get an answer that works, though, be sure to post it back here!
-Cam

类别

在 Help Center 和 File Exchange 中查找有关 Network Connection and Exploration 的更多信息

标签

产品


版本

R2020b

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by