- I don't see the odometry at the mavros/local_position/odom topic
- Check remote configuration if valid. Both ROS_MASTER_URI and ROS_IP should be set to valid values
- I don't see the odomtery in rviz but i can see it in rostopic echo.
- Rviz on docker is particular about whether or not it initiated the master. So TF frames don't come sometimes. To solve it either just restart rviz once or make sure that the ros master starts up with rviz. This solves it always.
- I don't see the camera sensor topic /camera/pose or it's axis in rviz.
- this means that the sw/planning/racer_if.py file failed to send or recieve transforms. Check the tf tree if everything is up and running and connected.
- I see the sensor pose and odometry but i don't see the occupancy map
- There could be many reasons but as a first check the following topics if they're populated
- depth image topic. (/iris_depth_camera/camera/depth/image_rect_raw) or anything that you expect to recieve on.
- odometry topic: mavros/local_position/odom
- sensor pose topic: /camera/pose
- If you're on a remote networking setup, check if the unix time is synced between the robot and your pc. The command:
date +%s. If not then follow these instructions to do it. - check these variables in the fuel parameters given in algorithm.xml and see if they make sense and work with each other
- map_size_x
- map_size_y
- map_size_z
- sdf_map/ground_height
- sdf_map/box_min_x
- sdf_map/box_min_y
- sdf_map/box_min_z
- sdf_map/box_max_x
- sdf_map/box_max_y
- sdf_map/box_max_z
- I get the error that the package 'px4' wasn't found
- the setup_paths.bash script failed for some reason. Basically the script sets the internal path of the sitl_gazebo-classic ros package, and some environment variables. with some digging you can easily find how to do this manually for your setup as well.
- I get a segmentation fault in the exploration node
- You are at god's own mercy. best of luck
- While hardware testing, i get the error 'Global data lost for over half a second'
- There is something up with either the wifi router at the lab or time syncing between your pc and the drone OBC.
- For time syncing check the link mentioned before.
- For wifi router, ping the jetson from your pc and see if is under 20-30 ms. If you see very high and erratic ping times like 200ms, check issue #__ (TODO add issue for realsense pwr mgmt here).
- On a vscode remote docker container, I run roscore but nothing happens
- Check issue #13