Difference between revisions of "Day 4"
From Bambi
Line 1: | Line 1: | ||
− | # First implementation of <code>/missioncontroller</code> ROS node (it should publish a <code>mavros_msg/sendtext</code> on <code>/mavros/sendtext/send</code> topic) | + | # First implementation of <code>/missioncontroller</code> ROS node (it should publish a take off <code>mavros_msg/sendtext</code> on <code>/mavros/sendtext/send</code> topic) |
# Find out that the starting position of PX4 simulation is hard-coded in <code>/Tools/sitl_gazebo/include/gazebo_gps_plugin.h</code> | # Find out that the starting position of PX4 simulation is hard-coded in <code>/Tools/sitl_gazebo/include/gazebo_gps_plugin.h</code> | ||
#* Add this to your .bashrc: | #* Add this to your .bashrc: | ||
Line 5: | Line 5: | ||
#*#<code>export PX4_HOME_LON=11.490920</code> | #*#<code>export PX4_HOME_LON=11.490920</code> | ||
#*#<code>export PX4_HOME_ALT=1415</code> | #*#<code>export PX4_HOME_ALT=1415</code> | ||
+ | # New repository config: | ||
+ | #* Created repository <code>mavlink-library-v2</code> as a fork in BambiSaver repo to use it as a submodule in PX4 Firmware | ||
+ | #** Updatet it with current mavlink msg header build output | ||
+ | #** N.B Every time .xml messsage definition is updated we should update the forked repository pushing the content of<code>bambi/build/mavlink/include/v2.0</code>. Then it is required to update submodule of <code>px4-firmware-bambi</code> to make sure it is up-to-date |
Revision as of 16:07, 7 August 2018
- First implementation of
/missioncontroller
ROS node (it should publish a take offmavros_msg/sendtext
on/mavros/sendtext/send
topic) - Find out that the starting position of PX4 simulation is hard-coded in
/Tools/sitl_gazebo/include/gazebo_gps_plugin.h
- Add this to your .bashrc:
export PX4_HOME_LAT=46.452895
export PX4_HOME_LON=11.490920
export PX4_HOME_ALT=1415
- Add this to your .bashrc:
- New repository config:
- Created repository
mavlink-library-v2
as a fork in BambiSaver repo to use it as a submodule in PX4 Firmware- Updatet it with current mavlink msg header build output
- N.B Every time .xml messsage definition is updated we should update the forked repository pushing the content of
bambi/build/mavlink/include/v2.0
. Then it is required to update submodule ofpx4-firmware-bambi
to make sure it is up-to-date
- Created repository