Please ask about problems and questions regarding this tutorial on answers.ros.org. Don't forget to include in your question the link to this page, the versions of your OS & ROS, and also add appropriate tags. |
IMU
Description: Using IMU sensor which is minimu9 v3 on the evarobot.Tutorial Level: BEGINNER
Next Tutorial: Kinect
Starting IMU
Connect via SSH to the Evarobot.
> ssh pi@evarobotDSK > sudo -s
Execute evarobot_minimu9.launch file.
# evarobot > roslaunch evarobot_minimu9 evarobot_minimu9.launch
In order to sync ros masters,
# evarobot > roslaunch master_discovery_fkie master_discovery.launch
# evarobot > roslaunch master_sync_fkie master_sync.launch
Reading IMU via Terminal
Execute synchronisation nodes, to reach evarobot ros master.
# pc > roslaunch master_discovery_fkie master_discovery.launch
# pc > roslaunch master_sync_fkie master_sync.launch
You can echo imu_data topic,
# pc > rostopic echo /imu_data
To get information about bumper topic
# pc > rostopic info /imu_data
Writing a Simple Subscriber for IMU
Use the catkin_create_pkg script to create a new package called 'evarobot_imu_subs' which depends on sensor_msgs, roscpp, and rospy:
> cd ~/catkin_ws/src > catkin_create_pkg evarobot_imu_subs sensor_msgs rospy roscpp
Create a src directory in the evarobot_imu_subs package directory.
> mkdir -p ~/catkin_ws/src/evarobot_imu_subs/src
Create the src/imu_listener.cpp file within the evarobot_imu_subs package.
> cd ~/catkin_ws/src/evarobot_imu_subs/src > gedit imu_listener.cpp
And paste the following inside imu_listener.cpp:
1 #include "ros/ros.h"
2 #include "sensor_msgs/Imu.h"
3
4 /**
5 * This tutorial demonstrates simple receipt of IMU sensor data over the ROS system.
6 */
7
8 /**
9 * Callback function executes when new topic data comes.
10 * Task of the callback function is to print data to screen.
11 */
12 void chatterCallback(const sensor_msgs::Imu::ConstPtr& msg)
13 {
14 ROS_INFO("Imu Seq: [%d]", msg->header.seq);
15 ROS_INFO("Imu Orientation x: [%f], y: [%f], z: [%f], w: [%f]", msg->orientation.x,msg->orientation.y,msg->orientation.z,msg->orientation.w);
16 }
17
18 int main(int argc, char **argv)
19 {
20 /**
21 * The ros::init() function needs to see argc and argv so that it can perform
22 * any ROS arguments and name remapping that were provided at the command line.
23 * For programmatic remappings you can use a different version of init() which takes
24 * remappings directly, but for most command-line programs, passing argc and argv is
25 * the easiest way to do it. The third argument to init() is the name of the node.
26 *
27 * You must call one of the versions of ros::init() before using any other
28 * part of the ROS system.
29 */
30 ros::init(argc, argv, "imu_listener");
31
32 /**
33 * NodeHandle is the main access point to communications with the ROS system.
34 * The first NodeHandle constructed will fully initialize this node, and the last
35 * NodeHandle destructed will close down the node.
36 */
37 ros::NodeHandle n;
38
39 /**
40 * The subscribe() call is how you tell ROS that you want to receive messages
41 * on a given topic. This invokes a call to the ROS
42 * master node, which keeps a registry of who is publishing and who
43 * is subscribing. Messages are passed to a callback function, here
44 * called chatterCallback. subscribe() returns a Subscriber object that you
45 * must hold on to until you want to unsubscribe. When all copies of the Subscriber
46 * object go out of scope, this callback will automatically be unsubscribed from
47 * this topic.
48 *
49 * The second parameter to the subscribe() function is the size of the message
50 * queue. If messages are arriving faster than they are being processed, this
51 * is the number of messages that will be buffered up before beginning to throw
52 * away the oldest ones.
53 */
54 ros::Subscriber sub = n.subscribe("imu_data", 1000, chatterCallback);
55
56 /**
57 * ros::spin() will enter a loop, pumping callbacks. With this version, all
58 * callbacks will be called from within this thread (the main one). ros::spin()
59 * will exit when Ctrl-C is pressed, or the node is shutdown by the master.
60 */
61 ros::spin();
62
63 return 0;
64 }
> cd .. > gedit CMakeLists.txt
The generated CMakeLists.txt should look like this
cmake_minimum_required(VERSION 2.8.3) project(evarobot_imu_subs) find_package(catkin REQUIRED COMPONENTS sensor_msgs roscpp rospy ) catkin_package() include_directories( ${catkin_INCLUDE_DIRS} ) add_executable(imu_listener src/imu_listener.cpp) add_dependencies(imu_listener sensor_msgs_generate_messages_cpp) target_link_libraries(imu_listener ${catkin_LIBRARIES} )
Now run catkin_make
> cd ~/catkin_ws/ > catkin_make
To run imu_listener,
> rosrun evarobot_imu_subs imu_listener