px4-firmware/msg/vehicle_rates_setpoint.msg

uint64 timestamp	# time since system start (microseconds)

float32 roll		# body angular rates in NED frame
float32 pitch		# body angular rates in NED frame
float32 yaw		# body angular rates in NED frame

# For clarification: For multicopters thrust_body[0] and thrust[1] are usually 0 and thrust[2] is the negative throttle demand.
# For fixed wings thrust_x is the throttle demand and thrust_y, thrust_z will usually be zero.
float32[3] thrust_body	# Normalized thrust command in body NED frame [-1,1]
beautify some identation 2018-08-07 10:42:32 -03:00			`uint64 timestamp # time since system start (microseconds)`
vehicle rates sp as msg 2014-12-08 07:23:27 -04:00
beautify some identation 2018-08-07 10:42:32 -03:00			`float32 roll # body angular rates in NED frame`
			`float32 pitch # body angular rates in NED frame`
			`float32 yaw # body angular rates in NED frame`
uORB combine VTOL FW and MC virtual topics (#7008) 2017-04-09 14:17:20 -03:00
VTOL rate control architecture improvements (#10819) * attitude and rate setpoint message: use 3D array for thrust demand * FixedWingAttitudeControl: rework airspeed scaling * move airspeed and scaling calculation into separate method * if vtol in hover and airspeed disabled use minimum airspeed instead of trim airspeed 2018-11-21 21:32:40 -04:00			`# For clarification: For multicopters thrust_body[0] and thrust[1] are usually 0 and thrust[2] is the negative throttle demand.`
			`# For fixed wings thrust_x is the throttle demand and thrust_y, thrust_z will usually be zero.`
			`float32[3] thrust_body # Normalized thrust command in body NED frame [-1,1]`