px4-firmware/msg/camera_trigger.msg

uint64 timestamp	# time since system start (microseconds)
uint64 timestamp_utc # UTC timestamp

uint32 seq		# Image sequence number
bool feedback	# Trigger feedback from camera

uint32 ORB_QUEUE_LENGTH = 2

# TOPICS camera_trigger
add timestamp field to uORB msgs; sync timestamp whenever possible 2018-08-06 21:30:05 -03:00			`uint64 timestamp # time since system start (microseconds)`
camera_trigger : completely refactor state handling 2017-05-01 14:05:50 -03:00			`uint64 timestamp_utc # UTC timestamp`
camera trigger : mavlink stream 2015-05-21 09:11:52 -03:00
camera_trigger : completely refactor state handling 2017-05-01 14:05:50 -03:00			`uint32 seq # Image sequence number`
camera_trigger.msg: add feedback field to understand if message camera from trigger or capture driver 2018-08-25 09:46:36 -03:00			`bool feedback # Trigger feedback from camera`
camera trigger and camera capture publish on two different topics and camera feedback module uses CAM_CAP_FBACK param to choose between the two. 2018-09-18 04:51:43 -03:00
Fix camera trigger via MAVLink when camera capture feedback is enabled - camera_trigger module always publishes the camera_trigger msg (independent of the camera feedback) - Use camera_trigger msg and set the feedback flag - Subscribing modules determine if the message is relevant based on the feedback message 2021-10-07 06:03:55 -03:00			`uint32 ORB_QUEUE_LENGTH = 2`

camera_trigger: remove camera trigger secondary camera_trigger: publish trigger when capture feedback is not enabled 2021-09-22 05:57:25 -03:00			`# TOPICS camera_trigger`