dark0707
/
px4-firmware
forked from Archive/PX4-Autopilot
1
0
Fork 0
Code Pull Requests Activity

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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ROMFS/px4fmu_common/init.d/10_dji_f330
View File

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

2
ROMFS/px4fmu_common/init.d/11_dji_f450
View File

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

2
ROMFS/px4fmu_common/init.d/15_tbs_discovery
View File

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

2
ROMFS/px4fmu_common/init.d/16_3dr_iris
View File

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

2
ROMFS/px4fmu_common/init.d/rc.custom_io_esc
View File

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

5
ROMFS/px4fmu_common/init.d/rc.multirotor
View File

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