px4_autopilot/boards/av/x-v1/init/rc.board_mavlink

#!/bin/sh
#
# av_x1-v1 specific board MAVLink startup script.
#------------------------------------------------------------------------------

# AV-X: start MAVLink to companion (connected to TX2)
mavlink start -d /dev/ttyS5 -b 500000 -m osd
mavlink stream -d /dev/ttyS5 -s HIGHRES_IMU -r 250
mavlink stream -d /dev/ttyS5 -s CAMERA_TRIGGER -r 100
mavlink stream -d /dev/ttyS5 -s LOCAL_POSITION_NED -r 50


# AV-X: start MAVLink UDP port 14570
mavlink start -x -u 14570
ROMFS split rc.board into defaults, sensors, and extras 6 years ago			`#!/bin/sh`
			`#`
Mavlink startup script per board -moved rc.mavlink to the boards optional rc additions (now it's called rc.board_mavlink) to handle board specific mavlink needs (mavlink over usb, ethernet, additional streams, etc.) -mavlink module will be responsible to usb defaults, therefore less args are needed to be passed to mavlink module if one wants to use mavlink over usb. -the way to check if connection is usb is by it's designated variable and not by config mode. 6 years ago			`# av_x1-v1 specific board MAVLink startup script.`
			`#------------------------------------------------------------------------------`
ROMFS split rc.board into defaults, sensors, and extras 6 years ago
			`# AV-X: start MAVLink to companion (connected to TX2)`
fix for AV board mavlink streams 6 years ago			`mavlink start -d /dev/ttyS5 -b 500000 -m osd`
			`mavlink stream -d /dev/ttyS5 -s HIGHRES_IMU -r 250`
			`mavlink stream -d /dev/ttyS5 -s CAMERA_TRIGGER -r 100`
			`mavlink stream -d /dev/ttyS5 -s LOCAL_POSITION_NED -r 50`

ROMFS split rc.board into defaults, sensors, and extras 6 years ago
			`# AV-X: start MAVLink UDP port 14570`
			`mavlink start -x -u 14570`