px4-firmware/msg/vehicle_local_position_setp...

# Local position setpoint in NED frame
# setting something to NaN means the state should not be controlled

uint64 timestamp	# time since system start (microseconds)

float32 x		# in meters NED
float32 y		# in meters NED
float32 z		# in meters NED
float32 yaw		# in radians NED -PI..+PI
float32 yawspeed	# in radians/sec
float32 vx		# in meters/sec
float32 vy		# in meters/sec
float32 vz		# in meters/sec
float32[3] acceleration # in meters/sec^2
float32[3] jerk # in meters/sec^3
float32[3] thrust	# normalized thrust vector in NED

# TOPICS vehicle_local_position_setpoint trajectory_setpoint
log velocity - and acceleration/thrust setpoint 2015-02-06 17:05:35 -04:00			`# Local position setpoint in NED frame`
msg: vehicle_local_position_setpoint comment about usage of NaN 2017-11-08 10:43:02 -04:00			`# setting something to NaN means the state should not be controlled`
port more uorb headers to msg 2015-01-28 02:54:58 -04:00
beautify some identation 2018-08-07 10:42:32 -03:00			`uint64 timestamp # time since system start (microseconds)`
add timestamp field to uORB msgs; sync timestamp whenever possible 2018-08-06 21:30:05 -03:00
beautify some identation 2018-08-07 10:42:32 -03:00			`float32 x # in meters NED`
			`float32 y # in meters NED`
			`float32 z # in meters NED`
			`float32 yaw # in radians NED -PI..+PI`
FlightTasks: switch field name from thr to thrust + some code spacing 2018-01-12 08:47:38 -04:00			`float32 yawspeed # in radians/sec`
beautify some identation 2018-08-07 10:42:32 -03:00			`float32 vx # in meters/sec`
			`float32 vy # in meters/sec`
			`float32 vz # in meters/sec`
vehicle_local_position_setpoint: make acceleration and jerk arrays 2019-10-22 11:41:52 -03:00			`float32[3] acceleration # in meters/sec^2`
			`float32[3] jerk # in meters/sec^3`
FlightTasks: switch field name from thr to thrust + some code spacing 2018-01-12 08:47:38 -04:00			`float32[3] thrust # normalized thrust vector in NED`
Auto traj - Add Trajectory logging - move the update after the integration: a new computed jerk has an impact at the next epoch only - add jerk reduction in case of too large integration time: when a jerk of "min_jerk" during dt is too much - add jerk reduction if the integration time is larger than the predicted one and that integrating that jerk would lead to an acceleration overshoot - rename some variables 2018-10-25 10:29:45 -03:00
			`# TOPICS vehicle_local_position_setpoint trajectory_setpoint`