This repository has been archived by the owner on Mar 10, 2023. It is now read-only.
forked from ros-drivers/advanced_navigation_driver
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Advanced Navigation ROS Driver Notes.txt
146 lines (120 loc) · 9.23 KB
/
Advanced Navigation ROS Driver Notes.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
/*********************************************/
/* Advanced Navigation */
/* ROS Driver */
/* Packet to Published Message Example */
/* */
/* Copyright 2017, Advanced Navigation */
/* */
/*********************************************/
/*********************************************/
/* Introduction */
/*********************************************/
This is an example using the Advanced Navigation Spatial SDK to create a ROS driver that reads and decodes the anpp packets (in this case packet #20 and packet #27) and publishes the information as ROS topics / messages.
It should work on all Advanced Navigation INS devices.
This example has been developed and tested using Ubuntu Linux v16.04 LTS and ROS Lunar. Installation instructions for ROS can be found here: http://wiki.ros.org/lunar/Installation/Ubuntu.
If you require any assistance using this code, please email [email protected].
/*********************************************/
/* Build Instructions */
/*********************************************/
ROS driver build instructions from: http://www.clearpathrobotics.com/assets/guides/ros/Creating%20publisher.html#creating-a-workspace-package
1. Open a new Terminal window and type: "mkdir ~/ros[enter]".
2. Type: "mkdir ~/ros/src[enter]".
3. Type: "cd ~/ros/src[enter]".
4. Type: "catkin_init_workspace[enter]".
5. Type: "catkin_create_pkg advanced_navigation_driver roscpp std_msgs[enter]".
6. Copy the supplied "src" directory and the "package.xml" file into the "~/ros/src/advanced_navigation_driver" directory. It should be OK to overwrite the existing "package.xml" file if you are following these instructions explicitly. If installing into your own pre-existing catkin workspace it may be necessary to manually merge the contents of these files.
7. Modify the "package.xml" file in ~/ros/src/an_driver directory as required.
8. Copy the supplied "CMakeLists.txt"file into the "~/ros/src/advanced_navigation_driver" directory, or modify the exisitng CMakeLists.txt file in the "~/ros/src/advanced_navigation_driver" directory by adding two lines at the end (you may need to modify the paths to suit your installation):
add_executable(advanced_navigation_driver src/an_driver.cpp src/spatial_packets.c src/an_packet_protocol src/rs232/rs232.c)
target_link_libraries(advanced_navigation_driver ${catkin_LIBRARIES})
9. Type: "cd ~/ros[enter]".
10. Type: "catkin_make[enter]".
/*********************************************/
/* Device Configuration */
/*********************************************/
To use this example code, your Advanced Navigation device should be already configured to output anpp packets #20 and #27.
/*********************************************/
/* Run Instructions */
/*********************************************/
1. Open a new Terminal window and type: "sudo adduser user_name dialout[enter]". This should only need to be done once.
2. Plug in the USB to RS232 adapter cable that is connected to the Advanced Navigation device.
3. In the Terminal window type: "dmesg | grep tty [enter]" to confirm the name of the com port (should be something like "ttyUSB0").
4. Type: "roscore[enter]" to start ROS Master.
5. Open a new Terminal window and type: "source ~/ros/devel/setup.bash[enter]".
6. If your com port is named "ttyUSB0" and your baud rate is set to 115200 bps, type: "rosrun advanced_navigation_driver advanced_navigation_driver [enter]". If your com port or baud rate are different then type: "rosrun advanced_navigation_driver advanced_navigation_driver /dev/your_com_port_name your_baud_rate [enter]".
7. Open a new Terminal window and type: "rosnode list[enter]" to list the available nodes. You should see these listed:
/an_device_node
/rosout
8. Type: "rostopic list[enter]" to list the published topics. You should see these listed:
/an_device/FilterStatus
/an_device/Imu
/an_device/NavSatFix
/an_device/SystemStatus
/an_device/Twist
9. Type: "rostopic echo /an_device/Imu[enter]"to see the "Imu" messages being published.
10. Open a new Terminal window and type: "rostopic echo /an_device/NavSatFix[enter]"to see the "NavSatFix" messages being published.
11. Open a new Terminal window and type: "rostopic echo /an_device/Twist[enter]"to see the "Twist" messages being published.
12. Open a new Terminal window and type: "rostopic echo /an_device/FilterStatus[enter]"to see the "Filter Status" messages being published.
13. Open a new Terminal window and type: "rostopic echo /an_device/SystemStatus[enter]"to see the "System Status" messages being published.
14. You need to subscribe to these topics in your code to get access to the data in the messages.
/*********************************************/
/* Published Topics */
/*********************************************/
an_device/NavSatFix
an_device/Twist
an_device/Imu
an_device/SystemStatus
an_device/FilterStatus
/*********************************************/
/* Published Messages: an_device/NavSatFix */
/*********************************************/
sensor_msgs / NavSatFix / Header / Stamp / Sec // Packet 20, Field 3, Unix time
sensor_msgs / NavSatFix / Header / Stamp / Nsec // Packet 20, Field 4, Unix time microseconds * 1000
sensor_msgs / NavSatFix / Header / Frame_ID // Fixed to 0
sensor_msgs / NavSatFix / Status / Status // Packet 20, Field 2, Translated from anpp fix type
sensor_msgs / NavSatFix / Status / Service // Fixed to 1 (GPS)
sensor_msgs / NavSatFix / Latitude // Packet 20, Field 5, Converted from radians to degrees
sensor_msgs / NavSatFix / Longitude // Packet 20, Field 6, Converted from radians to degrees
sensor_msgs / NavSatFix / Altitude // Packet 20, Field 7, Metres
sensor_msgs / NavSatFix / Position_Covariance // Packet 20, Fields 21, 22, 23, Variance on the diagonals only, converted from standard deviation metres
sensor_msgs / NavSatFix / Position_Covariance_Type // Fixed to 2 (diagonal known)
/*********************************************/
/* Published Messages: an_device/Twist */
/*********************************************/
geometry_msgs / Twist / Linear / X // Packet 20, Field 8, Metres per second
geometry_msgs / Twist / Linear / Y // Packet 20, Field 9, Metres per second
geometry_msgs / Twist / Linear / Z // Packet 20, Field 10, Metres per second
geometry_msgs / Twist / Angular / X // Packet 20, Field 18, Radians per second
geometry_msgs / Twist / Angular / Y // Packet 20, Field 19, Radians per second
geometry_msgs / Twist / Angular / Z // Packet 20, Field 20, Radians per second
/*********************************************/
/* Published Messages: an_device/Imu */
/*********************************************/
sensor_msgs / Imu / Orientation / X // Packet 20, Fields 15, 16, 17, Converted from radians to quaternions
sensor_msgs / Imu / Orientation / Y // Packet 20, Fields 15, 16, 17, Converted from radians to quaternions
sensor_msgs / Imu / Orientation / Z // Packet 20, Fields 15, 16, 17, Converted from radians to quaternions
sensor_msgs / Imu / Orientation / W // Packet 20, Fields 15, 16, 17, Converted from radians to quaternions
sensor_msgs / Imu / Orientation_Covariance // Packet 27, Fields 2, 3, 4, Anpp Packet 27 Field 1 is for the W axis which is not requested
sensor_msgs / Imu / Angular_Velocity / X // Packet 20, Field 18, Radians per second, same as geometry_msgs / Twist / Angular / X
sensor_msgs / Imu / Angular_Velocity / Y // Packet 20, Field 19, Radians per second, same as geometry_msgs / Twist / Angular / Y
sensor_msgs / Imu / Angular_Velocity / Z // Packet 20, Field 20, Radians per second, same as geometry_msgs / Twist / Angular / Z
sensor_msgs / Imu / Linear_Acceleration / X // Packet 20, Field 11, Metres per second per second
sensor_msgs / Imu / Linear_Acceleration / Y // Packet 20, Field 12, Metres per second per second
sensor_msgs / Imu / Linear_Acceleration / Z // Packet 20, Field 13, Metres per second per second
/**********************************************/
/* Published Messages: an_device/SystemStatus */
/**********************************************/
diagnostic_msgs / Diagnostic_Status / Name // Fixed to "System Status"
diagnostic_msgs / Diagnostic_Status / Level // Packet 20, Field 1, Set to 0 (OK) or 2 (ERROR)
diagnostic_msgs / Diagnostic_Status / Message // Packet 20, Field 1, Varies
/**********************************************/
/* Published Messages: an_device/FilterStatus */
/**********************************************/
diagnostic_msgs / Diagnostic_Status / Name // Fixed to "Filter Status"
diagnostic_msgs / Diagnostic_Status / Level // Packet 20, Field 2, Set to 0 (OK) or 1 (WARN)
diagnostic_msgs / Diagnostic_Status / Message // Packet 20, Field 2, Varies
/**********************************************/
/* Messages Not Published */
/**********************************************/
sensor_msgs / Imu / Angular_Velocity_Covariance
sensor_msgs / Imu / Linear_Acceleration_Covariance