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

2026-05-22 01:12:31 +00:00 · 2013-10-30 09:14:57 +01:00
parent bd874afcfd
commit 34d2f318ac
6 changed files with 10 additions and 5 deletions
--- a/ROMFS/px4fmu_common/init.d/10_dji_f330
+++ b/ROMFS/px4fmu_common/init.d/10_dji_f330
@@ -59,6 +59,8 @@ then
 	mavlink start
 	usleep 5000

+	commander start
+
 	sh /etc/init.d/rc.io
 	# Set PWM values for DJI ESCs
 else
--- a/ROMFS/px4fmu_common/init.d/11_dji_f450
+++ b/ROMFS/px4fmu_common/init.d/11_dji_f450
@@ -43,6 +43,8 @@ then
 	mavlink start
 	usleep 5000

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

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

+	commander start
+
 	sh /etc/init.d/rc.io
 else
 	# Start MAVLink (on UART1 / ttyS0)
--- a/ROMFS/px4fmu_common/init.d/rc.custom_io_esc
+++ b/ROMFS/px4fmu_common/init.d/rc.custom_io_esc
@@ -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
--- a/ROMFS/px4fmu_common/init.d/rc.multirotor
+++ b/ROMFS/px4fmu_common/init.d/rc.multirotor
@@ -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)
 #