Lorenz Meier
7b94a2da80
ROMFS: Exclude uncommon board configs (ZMR250)
5 years ago
Lorenz Meier
41f9df6cf8
ROMFS: Exclude uncommon board configs (Nanomind)
5 years ago
Lorenz Meier
59ee1f0a29
ROMFS: Exclude uncommon board configs (Tilt Quad)
5 years ago
Lorenz Meier
b5daf5799d
ROMFS: Exclude uncommon board configs (Teal)
5 years ago
Lorenz Meier
ed4ed50786
ROMFS: Exclude uncommon board configs (Clover4)
5 years ago
Lorenz Meier
4ee4b830ab
ROMFS: Exclude uncommon board configs (Crazyflie)
5 years ago
Lorenz Meier
d8ed4c7b3d
ROMFS: Exclude uncommon board configs (Generic Ground)
5 years ago
Lorenz Meier
428ce42966
ROMFS: Exclude uncommon board configs (Axialracing AX10)
5 years ago
Lorenz Meier
a394a68e47
ROMFS: Exclude uncommon board configs (Traxxas Stampede)
5 years ago
Lorenz Meier
8bc3418892
ROMFS: Exclude uncommon board configs (AION Robotics)
5 years ago
Lorenz Meier
ebd188bca9
ROMFS: Exclude uncommon board configs (DFrobot GPX Asurada)
5 years ago
Lorenz Meier
37cc9604bc
ROMFS: Exclude uncommon board configs (Quad +)
5 years ago
Lorenz Meier
fd73580db8
ROMFS: Exclude uncommon board configs (UUV Generic)
5 years ago
Lorenz Meier
56de232bae
ROMFS: Exclude uncommon board configs (UUV HippoCambus)
5 years ago
Lorenz Meier
54c3e72f0c
ROMFS: Exclude uncommon board configs (Hexa X)
5 years ago
Lorenz Meier
d68caed742
ROMFS: Exclude uncommon board configs (Draco R)
5 years ago
Lorenz Meier
942097a0ce
ROMFS: Exclude uncommon board configs (Hexa +)
5 years ago
Lorenz Meier
7b0c8ec3fc
ROMFS: Exclude uncommon board configs (Octo X)
5 years ago
Lorenz Meier
e93d23985c
ROMFS: Exclude uncommon board configs (Octo +)
5 years ago
Lorenz Meier
75491ed298
ROMFS: Exclude uncommon board configs (VTOL Tailsitter)
5 years ago
Lorenz Meier
a3419a0130
ROMFS: Exclude uncommon board configs (VTOL Octo)
5 years ago
Lorenz Meier
4176627539
ROMFS: Exclude uncommon board configs (Babyshark)
5 years ago
Lorenz Meier
f7666a8b74
ROMFS: Exclude uncommon board configs (Convergence)
5 years ago
Lorenz Meier
65ea2bc981
ROMFS: Exclude uncommon board configs (Claire)
5 years ago
Lorenz Meier
8d0f9d8601
ROMFS: Exclude uncommon board configs (Ranger)
5 years ago
Lorenz Meier
1300930d85
ROMFS: Exclude uncommon board configs (QuadRanger)
5 years ago
Lorenz Meier
f663515f49
ROMFS: Exclude uncommon board configs (VTOL AAVVT)
5 years ago
Lorenz Meier
207ae6d83c
ROMFS: Exclude uncommon board configs (VTOL Standard Delta)
5 years ago
Lorenz Meier
1e1762401e
ROMFS: Exclude uncommon board configs (VTOL AAERT)
5 years ago
Lorenz Meier
dc41771c1a
ROMFS: Exclude uncommon board configs (Quad+)
5 years ago
Lorenz Meier
6cd669836c
ROMFS: Exclude uncommon board configs (Firefly 6)
5 years ago
Lorenz Meier
af9b073c9a
ROMFS: Exclude uncommon board configs (Steadidrine Mavrik)
5 years ago
Lorenz Meier
440067870a
ROMFS: Exclude uncommon board configs (Octo COX)
5 years ago
Lorenz Meier
f3e4aec45a
ROMFS: Exclude uncommon board configs (Hexa COX)
5 years ago
Lorenz Meier
079772823a
ROMFS: Exclude uncommon board configs (TBS Endurance)
5 years ago
Lorenz Meier
65052717fe
ROMFS: Exclude uncommon board configs (Steadidrone Q4D)
5 years ago
Lorenz Meier
83c0d4607e
ROMFS: Exclude uncommon board configs (3DR Iris)
5 years ago
Lorenz Meier
df49d1d815
ROMFS: Exclude uncommon board configs (TBS Dicovery)
5 years ago
Lorenz Meier
4f2d39cb15
SITL plane: Do not configure trigger
...
We have a plane_cam configuration for survey applications instead.
5 years ago
Lorenz Meier
39e473f988
Gazebo plane model: Enable tighter turns
...
This helps to fly smaller / faster test missions.
5 years ago
Lorenz Meier
76b3c18625
Add dedicated survey camera plane model
...
This is to allow us to test triggering properly in SITL
5 years ago
Lorenz Meier
320cc8bae6
POSIX SITL: Enable trigger control in plane model
...
This allows to test plane survey missions with the camera trigger included in SITL.
5 years ago
Daniel Agar
0eca583ecf
sensors: move baro aggregation to new sensors/vehicle_air_data
5 years ago
Daniel Agar
093e9ba1ce
mc_rate_control: use vehicle_angular_acceleration topic instead of differentiating
...
* mc_rate_control: use vehicle_angular_acceleration topic
* IMU_DGYRO_CUTOFF change default to 30 Hz
* improve IMU_DGYRO_CUTOFF param documentation (updated from MC_DTERM_CUTOFF)
5 years ago
Daniel Agar
5d33b9e999
delete Outback Challenge (OBC) AUTO_RTGS (datalink loss) and AUTO_RCRECOVER (rc loss)
5 years ago
Daniel Agar
f9794e99f8
move hover_thrust_estimator to new module (mc_hover_thrust_estimator)
...
* MC_HTE: unitialize with hover_thrust parameter
* MC_HTE: constrain hover thrust setter between 0.1 and 0.9
* MC_HTE: integrate with land detector and velocity controller
* MCHoverThrustEstimator: Always publish an estimate even when not fusing measurements. This is required as the land detector and the position controller need to receive a hover thrust value.
* MC_HTE: use altitude agl threshold to start the estimator
local_position.z is relative to the origin of the EKF while dist_bottom
is above ground
Co-authored-by: bresch <brescianimathieu@gmail.com>
5 years ago
Beat Küng
e627fed117
fmu-v2: disable perf command and some airframes
...
to reduce FLASH size
5 years ago
Matej Frančeškin
b8970673c6
Fixed Mavlink FTP tests
5 years ago
Katrin
116de6d25f
Airframe and mixer for rover DF Robot GPX:Asurada ( #14244 )
...
Added Airframe and mixer for rover DF Robot GPX:Asurada
Co-authored-by: Julian Oes <julian@oes.ch>
Co-authored-by: Lorenz Meier <lorenz@px4.io>
5 years ago
Julian Oes
874c6f385b
commander: unify offboard timeouts
...
The implementation before this change had two timeouts, a hard-coded
timeout of 0.5 seconds as well as a by param configurable timeout with
certain failsafe actions set.
This change aims to fix two problems:
1. The hard-coded offboard timeout can be triggered easily with sped up
lockstep simulation. Since i t is hard-coded it can't be adapted to
the speed factor.
2. The offboard signal can time out but no action will be taken just
yet. This means we end up in an in-between stage where no warning or
failsafe action has happened yet, even though certain flags are set
to a timeout state.
This patch aims to fix this by unifying the two timeouts to the existing
configurable param. The convoluted double timeout logic is replaced by a
simple hysteresis.
For anyone that has previously not changed the default timeout param (0),
the param will now be changed to 0.5 seconds which reflects the
previously hardcoded time. For anyone with a specific timeout
configured, the behaviour should remain the same.
Also, going forward, timeouts lower than 0.5 seconds should be possible.
5 years ago