Skip to content

Just to test the transforms and sensor fusing with ROS localisation

Notifications You must be signed in to change notification settings

gutsy-robot/ros_localisation_evarobot

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

You need to have the evarobot simulator for running this example.

You can install it by:

apt-get install ros-indigo-evarobot-*

After you have installed the simulator and other dependencies.

roslaunch evarobot_gazebo evarobot.launch

In another terminal,

roslaunch ros_localization_evarobot dual_ekf_navsat_example.launch 

In a seperate terminal go to the bag directory of the project and do a:

rosbag play gps_only.bag

I have used the evarobot sim, because it has an IMU already mounted on the robot, so I don't need to write manual transforms from base_link to imu_link. When using this in our car, we will have the transforms(once we finish writing them) between these links, so we should be fine.

Also, I have filtered out the sensor_msgs/NavStat msgs from the rosbags given on the ROS Localisation repo:

			https://github.com/cra-ros-pkg/robot_localization

Because while using the simulator I already have an odom source and IMU msgs, so I don't need those msgs from the rosbag as they will conflict in case I directly play them. When we run this on the car we don't need the rosbag we will just the GPS sensor for getting the lat, longs.

Also, we would have a different odom source(visual odomotery). This example is only an attempt to show how we can configure the .yaml and launch files for our case.

Hope this was helpful!

About

Just to test the transforms and sensor fusing with ROS localisation

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published