Fixed commander and IO startup sequence, in-air restart is operational in this shape

This commit is contained in:
Lorenz Meier 2013-10-30 09:14:57 +01:00
parent bd874afcfd
commit 34d2f318ac
6 changed files with 10 additions and 5 deletions

View File

@ -59,6 +59,8 @@ then
mavlink start
usleep 5000
commander start
sh /etc/init.d/rc.io
# Set PWM values for DJI ESCs
else

View File

@ -43,6 +43,8 @@ then
mavlink start
usleep 5000
commander start
sh /etc/init.d/rc.io
else
# Start MAVLink (on UART1 / ttyS0)

View File

@ -43,6 +43,8 @@ then
mavlink start
usleep 5000
commander start
sh /etc/init.d/rc.io
else
# Start MAVLink (on UART1 / ttyS0)

View File

@ -43,6 +43,8 @@ then
mavlink start
usleep 5000
commander start
sh /etc/init.d/rc.io
else
# Start MAVLink (on UART1 / ttyS0)

View File

@ -61,6 +61,8 @@ then
mavlink start -d /dev/ttyS1 -b 115200
usleep 5000
commander start
sh /etc/init.d/rc.io
else
fmu mode_pwm

View File

@ -13,11 +13,6 @@ sh /etc/init.d/rc.sensors
#
sh /etc/init.d/rc.logging
#
# Start the commander.
#
commander start
#
# Start GPS interface (depends on orb)
#