pixhawk_and_motion_capture_communication
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
pixhawk_and_motion_capture_communication [2018/11/09 14:34] – leogeorgescu | pixhawk_and_motion_capture_communication [2018/11/09 14:49] (current) – leogeorgescu | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | <fs x-large> | + | <fs x-large> |
\\ | \\ | ||
**Author:** Leonardo Georgescu\\ | **Author:** Leonardo Georgescu\\ | ||
Line 33: | Line 33: | ||
2) One of the terminals will be used to connect to the wifi. First, ensure that the Odroid is connected to "DASL Warehouse2." | 2) One of the terminals will be used to connect to the wifi. First, ensure that the Odroid is connected to "DASL Warehouse2." | ||
{{:: | {{:: | ||
- | Then type out " | + | Then type out " |
+ | {{:: | ||
+ | The image above shows the position of the markers on the drone. | ||
+ | 3) If the connection is successful, the terminal should look as the one below. In the image there are two termainals. The bottom one is testing the connection by " | ||
+ | {{:: | ||
+ | 4) Another way to test the communication is to use another terminal to search up rostopic and see if the vrpn_client shows up. Whenever accessing any ros function, ensure that you are in the catkin folder \\ | ||
+ | {{:: | ||
+ | 5) The next tutorial will cover accessing Pixhawk data, as well as having the pixhawk flight controller read the position from the Mocap.\\ | ||
+ | For further questions, email me at [email protected]. |
pixhawk_and_motion_capture_communication.txt · Last modified: 2018/11/09 14:49 by leogeorgescu