0fa3bd4691
ms5611: use px4_getopt instead of getopt
...
- px4_getopt is threadsafe
- getopt does not do argument reordering (ms5611 start -T 5607 did not work)
2016-07-29 14:50:03 +02:00
1b0f41e36e
Added support to MS5611 Driver for MS5607
2016-07-29 14:50:03 +02:00
fa421a91e2
Add missing teest targets for MindPX
2016-07-29 14:10:44 +02:00
6ab9dc0acf
Testing cleanup from Daniel Agar
2016-07-29 13:49:14 +02:00
99aa5f49fc
FW ALTCTL requires altitude
2016-07-29 13:48:21 +02:00
6aa935fed6
FW don't allow ACRO or RATTITUDE
2016-07-29 13:48:21 +02:00
e70223c2be
Allow transition commands also in manual if no switch is used
2016-07-29 13:43:24 +02:00
1f1839d978
sensors: fixed code style
...
Signed-off-by: Roman <bapstroman@gmail.com >
2016-07-29 13:28:09 +02:00
9ece090dbe
vtol_att_control: use transition switch instead of aux1
...
Signed-off-by: Roman <bapstroman@gmail.com >
2016-07-29 13:28:09 +02:00
499d362b8b
added transition switch
2016-07-29 13:28:09 +02:00
302719527a
nuttx defconfig: increase nr of file descriptors, due to mavlink shell
2016-07-29 13:07:17 +02:00
e8d44da2c0
Tools: add mavlink_shell.py script to start a shell over mavlink
2016-07-29 13:07:17 +02:00
2241ab9cac
mavlink: add a shell using SERIAL_CONTROL MAVLink message
2016-07-29 13:07:17 +02:00
78a9472b25
px4iofirmware: astyle
2016-07-29 12:46:17 +02:00
dcb7c0e4c2
px4iofirmware: correct newline
2016-07-29 12:46:17 +02:00
79a1b84b09
px4iofirmware: clean up override decision
...
The override checking was scattered across two places and is now unified
in controls_tick(). The part in mixer_tick only decides which mixer (or
none) to use give the override flag.
2016-07-29 12:46:17 +02:00
de76c398ca
px4io: whitespace fixes
2016-07-29 12:46:17 +02:00
ec035b7268
px4iofirmware: no override in multirotor mode
...
This fixes a bug where multirotors got into override mode when the FMU
is dead/not responding.
The main bug was that the check was for FMU_OK || MANUAL_OVERRIDE_OK
in order to get further in the override checks.
Also a mixer_tick was called inside the controls_tick even though these
are called in px4io.c after each other anyway.
2016-07-29 12:46:17 +02:00
57b3bbf657
px4iofirmware: don't set FMU_OK flags immediately
...
The FMU_OK flags are later checked anyway based on
system_state.fmu_data_received_time.
2016-07-29 12:46:17 +02:00
31d5c59ab7
px4iofirmware: remove unused define
2016-07-29 12:46:17 +02:00
a9a5f3a19e
px4io: add FMU fail test mode
...
In order to test what happens in px4iofirmware when the FMU stops
sending PWM or control commands, I added a test mode. When the test mode
is activated, no controls are sent.
2016-07-29 12:46:17 +02:00
55d21242fe
Snapdragon: keep copying mainapp.config for now
...
mainapp.config can't be renamed to px4.config just yet because it would
clash with the name used for the DSP side.
2016-07-29 11:15:10 +02:00
b6a9ff756c
Rename mainapp to px4.
2016-07-29 11:05:01 +02:00
3b7ba915a8
small refactor ( #5155 )
2016-07-28 14:49:37 -07:00
9f5b081257
Wrap help line to fit through mini-dm. ( #5157 )
...
It currently gets cut off on mini-dm, split it into multiple lines
so all of it comes through.
2016-07-28 14:47:57 -07:00
4b414d96eb
Init _mission_throttle
2016-07-28 16:44:27 +02:00
0ce08ed9f8
Code style
2016-07-28 16:44:27 +02:00
ce3749d04f
Make tecs init airspeed mode dependent
2016-07-28 16:44:26 +02:00
0cf77a30b1
Init tecs with transition airspeed for vtols without airspeed sensor
2016-07-28 16:44:26 +02:00
415fbae31e
Fix build for HW w/o mux
2016-07-28 08:50:59 +02:00
50a14cfd29
tap_esc: disable the _mode param, use the number of configured channels instead
...
Not sure why the Mode enum exists in the first place...
2016-07-28 08:50:59 +02:00
3a0f4c84a5
motor_test: add iterate command
2016-07-28 08:50:59 +02:00
cbcbce3a28
tap_esc: use correct number of outputs
2016-07-28 08:50:59 +02:00
6245a9b134
motor_test: make -m & -p optional (select all motors/0 output if not given)
2016-07-28 08:50:59 +02:00
d660fb094b
tap_esc: add RPMSTOPPED macro, make sure driver starts with stopped motors
2016-07-28 08:50:59 +02:00
d6d3a56116
tap_esc: add buffer size check for _esc_feedback.esc[]
2016-07-28 08:50:59 +02:00
c55c978145
tap_esc: reset outputs only when armed really changed (not on each topic update)
2016-07-28 08:50:59 +02:00
4045068187
tap_esc: properly initialize _outputs
2016-07-28 08:50:59 +02:00
8602ff7856
tap_esc: fix code style, IS_armed -> _is_armed
2016-07-28 08:50:59 +02:00
3f9f320f18
tap_esc: improve error handling & reporting
2016-07-28 08:50:59 +02:00
a8e28c7232
tap_esc: fix argument ordering in memset
2016-07-28 08:50:59 +02:00
632e4630b1
TAP:ESC motors and LED working - The code is still hardcoded for 4 ESC
...
But the basics are working. N.B. To Stop the moros a value of 0 need to be
sent. LED color mask are misleeding - LED is On or Off per ESC.
2016-07-28 08:50:59 +02:00
a71cfe92f1
fmu: whitespace fix
2016-07-28 08:49:22 +02:00
664092b7d4
fmu: support ESC calibration
...
The FMU was lacking support to do the ESC calibration. This is needed
for Pixracer.
2016-07-28 08:49:22 +02:00
3289e0cee6
fmu: don't disarm with disarmed set
...
If disarmed PWM values have been set, we can't accept a disarm command.
If we did, the PWM output stop alltogether after the high pulse of the
ESC calibration.
2016-07-28 08:49:22 +02:00
d63870ad71
fmu: don' de-initialize
...
Once the PWM outputs are initialized, there is no point in
de-initializing them again.
2016-07-28 08:49:22 +02:00
f4e35873a1
DriverFramework: updated submodule ( #5148 )
...
This brings fixes for Edison which should not have any influence on
Snapdragon or Raspberry Pi.
2016-07-27 23:47:53 -07:00
c4eb65862f
Reduce esc calibration pwm timeout ( #5011 )
2016-07-27 01:52:20 -07:00
a9cb2d2fbe
navigator mission don't report loiter if landed
2016-07-27 10:39:07 +02:00
c4cb916afa
Fix sdlog2/logger path/file name overflows. ( #5138 )
...
* logger: prevent logpath buffer overflows
The handling of the log path had the potential to cause buffer
overflows, especially on POSIX platforms where the paths are often much
longer than just 64 chars.
* sdlog2: prevent logpath buffer overflows
When the log folder path was created, this was done with the unsafe
sprintf function instead of snprintf. This caused buffer overflows in
SITL but the overflow was usually not detected until recent testing of
some work in progress.
2016-07-27 00:55:29 -07:00
Beat Küng