a76c82f5f2
airframes: update 4050 generic 250 racer defaults
...
- P and D gains are too high for a racer
- default I gain is too low (0.25 is still quite low)
- use the thrust curve param instead of TPA
- improve responsiveness in Manual & increase max tilt angle to 60 degrees
- enable one-shot
- enable high-rate logging profile
- disable RC filter
7 years ago
a99f75dde2
Mavlink set last sent timestamp to space out initial publication
...
- remove QURT defines no longer required
7 years ago
98465171aa
ecl: include fix for bug affecting use of high frequency optical flow data
7 years ago
c84d35e3d7
mc_pos_control: rework height limiter to stay in velocity mode
7 years ago
d26da5fa3b
mc_pos_control: Improve maximum height limiter
...
Implements a better method of determining when to switch from velocity to altitude control to keep height limit from being exceeded.
This method removes the overshoot and transients in height caused by the switching of the previous algorithm.
7 years ago
f0a1cd197e
mc_pos_control: formatting fixes
7 years ago
b77845a3c0
mc_pos_control: Fix bug in calculation of altitude limit
...
The correction for stopping distance applied to the maximum altitude limiter uses the vertical velocity estimate and gives the same offset for both positive (down) and negative (up) velocity.
This calculation has been corrected and simplified and variable names changes to make the functionality clearer.
7 years ago
967b27f131
ecl: rework optical flow selection logic
...
Fixes a race condition introduced by use of _is_dead-reckoning.
Only runs flow use logic when there is flow data available
7 years ago
e3a6528a80
ecl: include fixes to flow selection logic
7 years ago
366e36a07b
ekf2: Update parameter description
7 years ago
d46ee571ce
ecl: test changes to pr-ekfOptFlowFixes
7 years ago
9a83f55c6a
ecl: test PX4/ecl/pull/452
7 years ago
c1169eb38b
mc_pos_control : update to use new navigation limits architechture
7 years ago
8f5ceac936
ekf2 : use INFINITY when altitude limiting is not needed
7 years ago
1a2f9dd37a
land_detector : use INFINITY when altitude limiting is not needed
7 years ago
31aa1cbf01
simulator : publish optical flow limits over uORB
7 years ago
e8f1d50758
mavlink : update for compatibility with new navigation limits architechture
7 years ago
1d1dec0a8b
inav : update for compatibility with new navigation limits architechture
7 years ago
9483885ed9
lpe : update for compatibility with new navigation limits architechture
7 years ago
6a9377846f
ekf2 : update to use new navigation limits architechture
7 years ago
8299f571c8
msg : add height limits to local position
7 years ago
7f1686171b
sensors : add parameter for maximum flow rate
7 years ago
32a7097018
px4flow : publish sensor limits over uORB
7 years ago
230d6c5aa2
msg : add sensor limits to optical flow message
7 years ago
b3c5e53333
Unify optical flow height limiting
7 years ago
0113212b34
mc_pos_control: Update parameter descriptions
7 years ago
9e567cadd6
ekf2: Update parameter description
7 years ago
0dc2377c2f
mc_pos_control: format fixes
7 years ago
9fb674929c
commander: do not check global position when using flow in POSCTL
7 years ago
2c325414f9
mc_pos_control: limit maximum height when reliant on optical flow data
7 years ago
9028592c5f
mc_pos_control: control height above ground when reliant on optical flow
7 years ago
98597dcffc
commander: allow position uncertainty to grow when operator can correct for drift
7 years ago
e5d428bd65
msg: add definitions for estimator status control mode bit positions
7 years ago
aee05d0ac5
FMU: Increase stack space as needed (shown by instrumentation) to retain a 300 bytes buffer.
7 years ago
a62a71f48f
gps: reopen the gps port on failed auto-detection
...
work-around for https://github.com/PX4/Firmware/issues/9461
7 years ago
f87fa9131b
FMUv5: Fix RGB led usage - these are individual status leds.
7 years ago
02eaf2ce28
FMUv5: Fix safety switch led
...
Both IO and FMU are connected to the safety switch for default models. This needs later to be broken out to a config option for builds that do not contain an IO.
7 years ago
9f414e82f6
Subsystem_info status flags & checks: Add comment to indicate that the IMU+MAG consistency checks need to be performed AFTER the individual checks are complete
7 years ago
e12b470cac
Subsystem_info status flags & checks: Small fixes according to @bkueng's review
7 years ago
0b71c52225
Subsystem_info status flags & checks: Suppress sensor failover warnings in Hardware in the loop (HITL)
7 years ago
302cb0a285
Subsystem_info status flags & checks: Moved the set_health_flags helper functions out of the /lib/ folder and into the module/commander folder because they are actually only needed there
7 years ago
bd2af289f5
Subsystem_info status flags & checks: Code style fixes and cleanup to avoid strcmp() as suggested by @LorenzMeier
7 years ago
e4d863b95f
Subsystem_info status flags & checks: Separate the functionality to a) set the health flags inside commander and b) to publish them from external modules
7 years ago
a807d34a7a
Remove distance sensor checks again. These checks should be handled by EKF2 and should thus be added there later
7 years ago
be4ba32cf0
vl53lxx distance sensor: Remove subsystem_info calls because all sensors are now checked inside commander
7 years ago
075009be2f
Subsystem_info status flags & checks: 1) Set health flags in commander directly instead of publishing via uORB 2) move publish_subsystem_info into lib/ folder"
7 years ago
f5847a4a7b
Subsystem_info status flags & checks: Switch back to uORB for inter-process communication, handle GPS checks completely inside ekf2, add distance_sensor checks
7 years ago
6f1f414b49
Subsystem_info status flags & checks : Initial commit, updating the health flags in a centralized way mostly in commander and the votedSensorsUpdate function.
7 years ago
40e6a5a39b
fmu-v5: fix ms5611
7 years ago
2ab5dc2951
fmu-v5: remove i2c3 as bus expansion because used just for internal mag (ONBOARD)
7 years ago
Beat Küng
Daniel Agar
Paul Riseborough
Mohammed Kabir
Lorenz Meier
Philipp Oettershagen
DanielePettenuzzo