This is an error report.
Screenshot of the error
Error details
We're not able to get any reading from gazebo, when we type rosnode list, we can't see /gazebo. Also roscore has to be started manually.
1 Like
I guess you’ve already tried restarting the simulation?
Yes, I’ve tried that already
Hi @Shivani.s, welcome to the community!
What about when you do ros2 topic list?
This is an issue that will most likely be fixed by logging out, closing the browser for around 10 minutes, and logging back in. I say this because this is not a system wide issue.
Which exercise or example are you trying to follow? What are you trying to do? Please tell us the specific command in the notebook that is not working.
I tried logging out but the error is still there, and since I’m using ROS1 when i try rostopic list I get an error message saying ERROR: Unable to communicate with master!
I’m trying to do ROS basics in 5 days, the 5th chapter and whenever I try using any rosrun command the simulation does not run for all exercises.
I think you are mixing things up. Can you point to a specific example that is not working, taking a screenshot of the whole screen, including the notebook and the terminal?
rosrun is meant for running a ROS node, and it is up to that node whether or not to control a simulation.
Please start from the beginning of that chapter and show us the command that does not work (with screenshots as indicated above).
In this exercise the simulation does not work as its supposed to.
/gazebo is not present in in the rosnode list
when running this command I get this error and simulation does not run as it did before and all exercise that worked before does not work now
Thank you for providing these examples; they were very helpful.
It seems your VM is defective. Now I’m going to force-close this VM so that another one will be assigned to you.
- Please wait until you see the message “No course or rosject running” on the simulation page, then
- go home and relaunch the course.
Please let us know if the problem was solved.
Hi,
I didn’t get that message after waiting so the problem is still present.
I found that you modified some ROS environment variables in your .bashrc file. That was the problem.
Please do not modify any ROS params unless specifically told to so, or you know what you are doing and won’t complain later :D.
Anyways, it’s fixed now.
Thank you, it works now. I think I accidentally changed it without realising.
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.