7b531bcaef
Failure Detector - Play TONE_PARACHUTE_RELEASE_TUNE when force failsafe is set
2019-06-05 16:53:08 +02:00
d655c33faa
IO mixer - Change default mixer to DISARMED and allow to set outputs to failsafe if FMU does not respond and if flight termination circuit breaker is not set
2019-06-05 16:53:08 +02:00
6fb1b4886c
IO - Send flight termination circuit breaker state to IO through PX4IO_P_SETUP_ENABLE_FLIGHTTERM
2019-06-05 16:53:08 +02:00
796631db20
PX4IO driver - use "curcuit_breaker_enabled" function instead of manually checking its value
2019-06-05 16:53:08 +02:00
19bf080313
PX4ioFirmware - Clean should_arm, should_arm_nothrottle and should_always_enable_pwm indentation for better understanding
2019-06-05 16:53:08 +02:00
ba93f9b983
FailureDetector - Update failure detector logic in commander.
2019-06-05 16:53:08 +02:00
664fff4a24
Px4io Driver - Remove unimplemented prototype
2019-06-05 16:53:08 +02:00
b64a2a884b
Circuit Breaker - Disable flight termination circuit breaker by default (reverts ab40008) -> Allow flight termination
2019-06-05 16:53:08 +02:00
50d75dc7a6
IOFirmware - Properly clear the alarm flags
2019-06-05 16:53:08 +02:00
cf15cef066
Param "User Flight Profile" : improve documentation
2019-06-05 06:45:43 -07:00
d8a4d70fce
Add Param "User Flight Profile"
...
This param has no effect within the Firmware.
The param can be used for example:
* in log post processing to have context about the flight
* in ground stations to adapt the UI automatically
2019-06-05 06:45:43 -07:00
1d5684823d
disable -fassociative-math (within -funsafe-math-optimizations)
2019-06-05 14:54:29 +02:00
e7d0cabb52
logger: fix uninitialized member variable
...
This was reported by Coverity Scan.
2019-06-05 14:46:03 +02:00
d5298fccbd
PWM_REV - Clarify use case. The user shoul not be tempted to use that
...
parameter to reverse the direction of a rotor.
2019-06-05 09:10:06 +02:00
f2b4480e6b
GPS driver update to uORB::Subscription
2019-06-05 08:18:02 +02:00
bece63866d
platforms: remove px4_backtrace
2019-06-05 08:16:19 +02:00
35074aaffd
posix: remove segfault handler
...
I could not get a core dump without removing the segfault handler, hence
this change.
2019-06-05 08:16:19 +02:00
f3620f7018
Remove all leftover PX4_BACKTRACE calls
2019-06-05 08:16:19 +02:00
5273e2af04
Tools: remove decode_backtrace.py
...
This hasn't been used in a while and didn't quite work with the
backtraces produced anyway.
2019-06-05 08:16:19 +02:00
a1b96ba3a5
mpu9250 delete unused perf counters
2019-06-04 20:31:47 -04:00
26e041c43c
WQ increase stacks from 1200 to 1250 bytes
2019-06-04 20:24:51 -04:00
574f7e9f00
batt_smbus move to new WQ
2019-06-04 19:54:06 -04:00
3faab909d7
commander move most orb subscriptions to uORB::Subscription
2019-06-04 18:44:51 -04:00
777b615cf9
land_detector move to PX4 WQ hp_default
2019-06-04 18:10:21 -04:00
53aa4130a8
land_detector move orb subscriptions to uORB::Subscription
2019-06-04 18:10:21 -04:00
2320088541
use position controller parameters for limitation instead of acceleration/jerk
2019-06-04 16:47:33 +02:00
c497d94616
publish a minimal message for logging/debugging
2019-06-04 16:47:33 +02:00
09e1d4888c
use velocity component in bin direction instead of norm
2019-06-04 16:47:33 +02:00
33cd032c35
camelcase function name, initialize c++11 style
2019-06-04 16:47:33 +02:00
e7d17cc265
consider acceleration ramp-up time
2019-06-04 16:47:33 +02:00
ab792093e1
fix wrong if clause
2019-06-04 16:47:33 +02:00
23c23e3aa5
clean up
2019-06-04 16:47:33 +02:00
f50a1d58b0
bugfixes and cleanup
2019-06-04 16:47:33 +02:00
4212ae8b87
sign bug fix and clean up
2019-06-04 16:47:33 +02:00
60befdce5b
change collision prevention algorithm
2019-06-04 16:47:33 +02:00
8427cd3051
constant acceleration breaking for collision prevention
2019-06-04 16:47:33 +02:00
6f9598c76a
topic_listener: document how to exit
...
This was left out when the feature was added.
2019-06-04 09:24:00 -04:00
ceac68e69d
uORB remove unused SubscriptionInterval and SubscriptionIntervalData
2019-06-04 09:17:34 -04:00
d68dcb9cf7
log_writer_file: increase stack size by 20 bytes
...
Seems to be due to the console buffer.
2019-06-04 11:57:54 +02:00
0d71eeccbf
console buffer: write to log as 'boot_console_output' message
2019-06-04 11:57:54 +02:00
08b8ee4831
replace fprintf(stderr with PX4_{INFO/WARN}
2019-06-04 11:57:54 +02:00
d947818654
console: add simple dmesg functionality (enable only on v5)
2019-06-04 11:57:54 +02:00
2307c7c390
Geofence - Rename _warning_action_on to _geofence_warning_action_on
...
since it is only set by the geofence logic. Simplify conditions in IF
statements.
2019-06-04 08:35:56 +02:00
f8f967f073
Geofence - Change from "re-engage geofence failsafe every 10s when
...
outside the fence" to "engage geofence failsafe on transition". This
way, the pilot is not stucked in the non flight zone and can switch to
a manual mode and fly back or trigger RTL.
2019-06-04 08:35:56 +02:00
427b2e6636
Geofence - Do not trigger geofence failsafe while in low battery
...
failsafe action.
Also move geofence flags from static variables declared into the if
statement to private members of the class.
2019-06-04 08:35:56 +02:00
a707403eaf
mc_att_ctrl: added yawrate control from offboard.
...
This commit adds Roll Pitch Yawrate Thrust (RPYrT) setpoint control to the
PX4 stack, enabling the UAV to follow specific yawrates sent from
offboard. It also introduces individual body_rate flags, along the
lines of mavros.
Tested on a MoCap enabled flight arena in KTH Royal Institute of
Technology, Stockholm. The MAV receives RPYrT setpoints from an
external PID controller to stabilize around position setpoints.
The UAV is also externally disturbed to assess the stability to
external unmodeled events.
Fixed Kabir comments.
Removed deprecated ignore_bodyrate.
Fixed integration test.
2019-06-04 08:26:09 +02:00
ac002db25c
MAVLink/Commander: @Pedro-Roque's offboard yawrate handling
2019-06-04 08:26:09 +02:00
579cbbb42c
mavlink move to new lightweight uORB::Subscription
2019-06-03 17:06:21 -04:00
2c63e335e9
uORB::Subscription subscribe directly to uORB device node object
2019-06-03 17:06:21 -04:00
2d1c60bc85
SITL offboard ATT test reduce Z boundary requirement
...
- fixes #12155
2019-06-03 12:31:12 -04:00
bresch