b0ee1579a9
local_position_estimator: fix typo in params
2017-04-06 11:48:35 +02:00
04303dcf72
PreflightCheck: use orb_unsubscribe instead of px4_close
2017-04-06 11:48:35 +02:00
a6eb0053c5
TECS default FW_T_HRATE_FF 0.8
2017-04-05 09:31:20 +02:00
22d0e507c6
TECS fix height demand change
2017-04-05 09:31:20 +02:00
0158f1d506
VTOL Standard transition improvements ( #6904 )
...
* FW actuators fully on the entirety of front and back transition
* back transition ramp up to full MC weight half way through back transition
* increase maximum front and back transition times
* navigator don't reset transition altitude
2017-04-02 19:39:39 -04:00
1d681b0356
Update URL in airspeed calibration error message
...
When a FW/VTOL system detects a missing airspeed sensor, it produces an error message.
This patch uses the new relevant URLs in the PX4 documentation.
Fixes #4549
2017-04-03 00:25:24 +02:00
e8e4e5be49
land detector : add stbs for altitude
2017-04-02 21:52:18 +02:00
5f135acf33
Land detector: Add mode for rovers
2017-04-02 21:52:18 +02:00
d1c3b771ee
Update navigator_main.cpp
...
fix a spell error
2017-04-02 12:15:10 +02:00
2a175aa2f9
logger: use nullptr instead of NULL
2017-04-01 20:19:52 +02:00
bfcbe4b6c3
log_writer_file: rename perf counters
...
To be more consistent with the rest of the system
2017-04-01 20:19:52 +02:00
190c14c186
logger: add preflight & postflight process usage & perf counters to the log
...
For the process usage: we need to measure over a certain period of time,
then we can use the results. To avoid blocking, this does:
- after log is started, initialze the load counters, then one second later
add the results to the log
- after disarming: continue logging for one more second, then add the process
load to the log and stop logging.
- to avoid a delay, 'logger stop' will stop immediately and not log
postflight process usage.
2017-04-01 20:19:52 +02:00
e75f5a4642
perf_counter: add perf_print_counter_buffer & perf_iterate_all
...
These can be used to print the perf counters to a buffer.
2017-04-01 20:19:52 +02:00
446c734edc
perf_counter: use a mutex to protect concurrent access to the perf_counters linked list
...
perf_counters is read from and written to by different threads and thus
requires synchronization. Without it we risk accessing invalid memory.
There are still remaining issues (see comment in code), they will not lead
to a crash however.
2017-04-01 20:19:52 +02:00
4b01e5b6b6
printload: add print_load_buffer() method
...
Instead of printing to an fd, this prints to a buffer and calls a callback
for each line. To avoid code duplication, the print_load has been refactored
to print to a buffer first, then print to an fd. The overhead is not
noticable, and the behavior of print_load is unchanged.
2017-04-01 20:19:52 +02:00
9f3043f9ca
printload: store total_runtime in a separate loop
...
Because during the printf, the total_runtime could be changed by another
task. This is still not entirely race-free though.
2017-04-01 20:19:52 +02:00
23d0355979
printload: reduce memory usage of print_load_s
...
assuming CONFIG_MAX_TASKS = 32, this saves 256B of RAM
2017-04-01 20:19:52 +02:00
c46274043f
printload: use sched_lock to protect access to tcb
...
what could have gone wrong before? A scheduling switch during the printload
could have led to a task exit, rendering the tcb invalid. After switching
back, printload would access invalid memory.
This keeps the sched_lock() section as small as possible, just grabbing the
tcb variables we need.
2017-04-01 20:19:52 +02:00
4b8bedef48
avoid double promotions
2017-04-01 20:19:28 +02:00
3c1d785d86
mavlink_mission: set INT frame correctly
...
Also when formatting malvink mission items from internal mission items,
the INT flag should be obeyed.
2017-04-01 20:07:55 +02:00
80ce1b6dd8
mavlink_mission: support INT altitude frames
...
The relative altitude flag was not set correclty when waypoints are sent
using the INT protocol.
2017-04-01 20:07:55 +02:00
982fe91fa8
Commander: fix LED status bug when system is armed
2017-04-01 11:39:05 +02:00
419c474d53
mc_pos_control: manual input temporary yaw fix
2017-03-30 16:43:43 +02:00
358bcb6ae0
visibility.h: add #pragma GCC poison getenv setenv putenv
...
Just to make sure that it will never be used on NuttX. This is not an
architectural limitation, just a memory optimization, since we call
clearenv() on NuttX.
2017-03-29 23:02:09 +02:00
4a7e02c640
systemlib/visibility.h: remove this file
...
This is duplicated in src/include/visibility and is directly included via
compiler flag '-include'
2017-03-29 23:02:09 +02:00
79d15ad2f0
mavlink stream camera trigger broadcast DO_DIGICAM
2017-03-26 14:05:38 +02:00
679b59b8d4
lpe : default fusion flags for GPS-only use
2017-03-26 14:05:23 +02:00
16515e1d1e
VTOL standard transition use FW_PSP_OFF ( #6728 )
...
* VTOL back transition maintain FW_PSP_OFF
* VTOL Front transition FW_PSP_OFF rampup
2017-03-25 00:24:59 -04:00
f5ffdba4cc
Move uORB Subscription getter to header file ( #6891 )
2017-03-24 15:47:22 -04:00
8a6b6f9be5
Send MAVLink DO_DIGICAM_CONTROL on camera trigger ( #6815 )
2017-03-24 13:24:09 -04:00
5abdb8fbe9
Fixed spelling - onshot->oneshot
2017-03-23 08:28:15 +01:00
b01768addc
px4iofirmware mixer uses new Oneshot API
...
As discusssed in https://github.com/PX4/Firmware/pull/6678#discussion_r104177663
this take the safe approach to only call up_pwm_update on a valid mix
it does keep intatct the riginal author (OA) had an intent.
2017-03-23 08:28:15 +01:00
6309642c37
px4iofirmware registers uses new Oneshot API
...
1) Use up_pwm_retrigger to triger onshot
2) Updated comment to explain why a rate of zero makes sense
to set oneshot mode.
3) Updated copyright
2017-03-23 08:28:15 +01:00
9e3488af46
don't update servos if mixer_mix_threadsafe() failed to run
2017-03-23 08:28:15 +01:00
2d5588ae02
simplify oneshot mode selection; use zero PWM rate as indicator
...
cleanup and remove unused (new) params
2017-03-23 08:28:15 +01:00
aa9fbbedd5
add oneshot mode capability
...
change fmu to task
increase fmu_servo task priority to max and enable true oneshot
use lowest FMU priority which minimizes jitter
constrain oneshot updates to control group 0 events
2017-03-23 08:28:15 +01:00
be500723cd
mc_pos_control: gradual vel fix for slope
2017-03-22 15:21:34 +01:00
20a47a1a72
mc_pos_control: limit if just xy distance close to target
2017-03-22 15:21:34 +01:00
f9551c12de
mc_pos_control: param fix and gradual vel fix
2017-03-22 15:21:34 +01:00
72fb7a5062
mc_pos_control: added gradual landing speed logic
...
depending on two altitudes that can get set as parameter
the logic linearly slows down from higher land altitude 1 to slower land altitude 2
2017-03-22 15:21:34 +01:00
7434bcc693
mc_pos_control: fixed rebase and refactor errors
2017-03-22 15:21:34 +01:00
cd8cc1beaa
mc_pos_control: use blockparam, change variable name, delete unused variables
2017-03-22 15:21:34 +01:00
4c4f214ec7
mc_pos_control: target_threshold value change
...
mc_pos_control: reorder if statement
mc_pos_control: add get function for cruising speed
2017-03-22 15:21:34 +01:00
0d6f994145
mc_pos_control: slow down in auto when close to target
...
mc_pos_control: move limit vel xy after velocity controller
2017-03-22 15:21:34 +01:00
8e5a573cb3
mc_pos_control: add default only if there is no previous setpoint
2017-03-22 15:21:34 +01:00
fd3889b5a6
mc pos control: auto handling such that it does not use slewrate when goint to pos
2017-03-22 15:21:34 +01:00
5e2f18ebaa
mc_pos_control: added separate velocity control setpoint slewrate for deceleration
...
to improve the smooth user experience while accelerating
but not have any delay when braking
2017-03-22 15:21:34 +01:00
b32e5e7ec0
mc_pos_control: fixed all pull request complaints
...
mainly changing parameters to BlockParams, reorder them and comment
2017-03-22 15:21:34 +01:00
470c3fdc06
mc_pos_control: refactoring only in manual velocity setpoint generation
2017-03-22 15:21:34 +01:00
713ba45876
mcpos_control: remove duplicate deadzone parameters
2017-03-22 15:21:34 +01:00
Beat Küng