Day 4 - Revision history

Michael at 20:59, 7 August 2018

2018-08-07T20:59:02Z

Michael at 14:08, 7 August 2018

2018-08-07T14:08:05Z

Michael at 14:07, 7 August 2018

2018-08-07T14:07:03Z

Florian at 13:56, 7 August 2018

2018-08-07T13:56:15Z

Michael at 13:53, 7 August 2018

2018-08-07T13:53:51Z

Michael: Created page with "# First implementation of `/missioncontroller` ROS node (it should publish a `mavros_msg/sendtext` on `/mavros/sendtext/send` topic) # Find o..."

2018-08-07T13:53:25Z

Created page with "# First implementation of <code>/missioncontroller</code> ROS node (it should publish a <code>mavros_msg/sendtext</code> on <code>/mavros/sendtext/send</code> topic) # Find o..."

New page

# First implementation of <code>/missioncontroller</code> ROS node (it should publish a <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>

← Older revision		Revision as of 20:59, 7 August 2018
Line 9:		Line 9:
	#** Updatet it with current mavlink msg header build output		#** 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 submodules of <code>px4-firmware-bambi</code> to make sure it is up-to-date		#** 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 submodules of <code>px4-firmware-bambi</code> to make sure it is up-to-date
		+	#Push on bambi repo a primitive <code>missioncontroller</code> node which arm and lets the quad to take off. Up to now we use <code>/mavros/cmd/takeoff</code> service which only sends MAV_CMD_NAV_TAKEOFF forcing us to set an absolute ground altitude. It would be convenient to use a relative altitude using MAV_CMD_NAV_TAKEOFF_LOCAL message. This can be done using <code>/mavros/cmd/command</code> service which allow to send any <code>COMMAND_LONG</code> MAVlink messages.

@@ Line 8: / Line 8: @@
 #* 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
+#** 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 submodules of <code>px4-firmware-bambi</code> to make sure it is up-to-date

@@ 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>
 #* Add this to your .bashrc:
@@ Line 5: / Line 5: @@
 #*#<code>export PX4_HOME_LON=11.490920</code>
 #*#<code>export PX4_HOME_ALT=1415</code>

← Older revision		Revision as of 13:56, 7 August 2018
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 <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:
		+	#*#<code>export PX4_HOME_LAT=46.452895</code>
		+	#*#<code>export PX4_HOME_LON=11.490920</code>
		+	#*#<code>export PX4_HOME_ALT=1415</code>

← Older revision		Revision as of 13:53, 7 August 2018
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 <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>