\page sim_issues List of common issues encountered with the simulator
This is a draft document
This usually happens when the environment has not been setup. Please see the Setting up your Environment section.
This usually happens when the environment has not been setup. Please see the Setting up your Environmant section.
This usually happens when the environment has not been setup. Please see the Setting up your Environment section.
There is a small chance that you will have issues when starting up the simulator. This mainly happens in computers with less computing power. If you are experiencing issues, try launching the world and Astrobee seperately. To do this, you will need to open 2 terminals. Please make sure you setup your environment in both terminals (see Setting up your environment). In the first terminal, run:
roslaunch astrobee sim.launch default:=false rviz:=true
After everything in the first terminal starts up, in the second terminal, run:
roslaunch astrobee spawn.launch dds:=false robot:=sim_pub
If the robot body doesn't show up in RVIZ, please see the Robot Body Doesn't Show up in RVIZ section on how to fix this.
If this doesn't fix the problem, you may need to slow down the simulation to a speed that your computer can handle. Please see the Tolerance Violated Errors section.
If you end up having to launch the world and Astrobee separately, there is a
chance that the robot body will not show up in RVIZ. To fix this, you can toggle
the robot. To do this, please find the robot with the namespace you are using
in the Displays section of RVIZ (bottom left corner) and click the checkbox
located to the right twice (first to turn it off, then to turn it back on). If
you didn't specify a namespace, the namespace is the forward slash character(/)
and if can be found in the Debug section. It should have a red circle with a
white rectangle in the circle in front of the forward slash and the forward
slash should be red but this will go away after toggling it.
This is not an error in our system. Please see the Images section for more information.
Cannot move when in ready and not stopped Command not accepted in op state teleop
use gz stats to make sure you are running at your speed up factor
Make sure the position you are trying to get to is in the world
The only time we have seen this happen is when the op limits are not set correctly. make sure your limits are correct
Wait a little longer before trying to move robot
You don't have GDS as of yet, don't set the the gds flag to false
need to reset ekf or initialize bias, see teleop section
make sure the namespace matches the namespace you launched with