29d4d7c9fe
Update NuttX with stm32h7 sdmmc backport
5 years ago
c37ba26a2f
mavlink: remove outdated comment
5 years ago
2c5b8a9491
mavlink: handle stream not updated
...
Our answer does not just depend on whether the stream was found but
whether we actually were able to send out an update.
5 years ago
efb10a2fbc
mavlink: address review comments
5 years ago
7d1b451e39
mavlink: add missing copyright header, pragma once
5 years ago
afafc541d8
mavlink: use send() instead of using reset flag
...
I think we can just directly use send() and don't need to use the
workaround of resetting the send flag to trigger one send.
Also, we don't need to override it if we don't need to check any params.
5 years ago
b54c44bd37
mavlink: don't send streams with interval 0
...
We only need to send them immediately if the interval is < 0 meaning
unlimited.
5 years ago
3815e608f4
mavlink: create stream if needed and trigger once
...
Instead of creating the stream and deleting it again, we now create it
with a rate of 0 and trigger it once.
This should avoid heap fragmentation by continous allocations.
5 years ago
acdc15e2cd
mavlink: create stream even if rate is 0
...
This allows to send a message exactly once if requested.
5 years ago
bb032a9c46
mavlink: remove incorrect outdated comment
...
Default is -2, so the comments seems wrong.
5 years ago
80f91b0f6a
mavlink: add support for legacy requests back in
5 years ago
b4cbd93b7c
mavlink: new args to request message, omit param1
...
We can omit param1 because it is already used for the message_id, so
it's basically duplicate information and won't get used anywhere.
5 years ago
27b6c209e0
mavlink: Move request message logic to function
5 years ago
62bf0a6cf8
added streams to mavlink messages
5 years ago
edbe7e3ef0
added FLIGHT_INFORMATION stream
5 years ago
e1f4a70c0e
added AUTOPILOT_VERSION and PROTOCOL_VERSION streams
5 years ago
aef2a5755e
moving storage_information stream to separate file
5 years ago
9ce9fe38de
use storage_id 1
5 years ago
fd09198c7e
implemented MAV_CMD_REQUEST_MESSAGE for STORAGE_INFORMATION
5 years ago
25bfcf0497
README: remove experimental/legacy boards
5 years ago
08e1532bd0
README: fix 404 link
5 years ago
6c96748e54
boards: pixhawk mini add unused MPU9250 CS & DRDY pins
5 years ago
9e509a4bec
navigator: RTL minor whitespace and style fixes
5 years ago
aca6be8b5c
navigator: RTL destination throttle dataman access
5 years ago
7aac0c5ac3
platforms/nuttx/NuttX/nuttx back ports for H7
5 years ago
73bb18a053
px4_fmu-v6x: Limit Slew rate So IMU works with DMA
...
The defualt in NuttX is OSPEED of 50Mhz. This is realy a slew
rate control. At the default high slew rate the overshoot was
.7 Volts. On a ICM20649 this was causing the device to output
garbage. All 0s
N.B. A passive scope or Logic analyser's probes load will mask
the failure. Useed a FET probe to verify the issue.
5 years ago
5d90c31632
Added PX4 FmuV6X
5 years ago
9beca65600
stm32_common:board_mcu_version expand to include STM32H7[4|5]
...
Todate I have not fould a way to differentiate a 74 from a 75.
as all parts map to Device ID 0x450: STM32H742, STM32H743/753
and STM32H750.
One the CPU is fully differentiate in Nuttx, this can be a
#ifdef.
5 years ago
19cf2f47ac
stm32h7:adc read & clear EOC on init
5 years ago
bd1f69fb76
stm32_common:board_hw_rev_ver Support 16 Bit ADC
5 years ago
2c9a522f71
stm32_common:adc read & clear EOC on init
5 years ago
37c1837ceb
PX4:stm32_common/ToneAlarmInterfacePWM.cpp Extend for STM32H7
5 years ago
11585dfb67
ekf2: decrease default GPS horizontal velocity noise
5 years ago
8d47b36f1e
Makefile: fix j for clang-tidy calls
5 years ago
6afdc2c376
build: use ninja default for -jN unless set
...
It makes sense to trust ninja on selecting the number of cores. This is
also sensible in order not to change existing setups.
5 years ago
0ec9287457
build: actually pass number of cores to ninja
...
Without this ninja supposedely builds with the default of the system
which is 10 for my 4 core, 8 thread CPU. With this argument, you can now
actually set it.
This has the benefit that the Gazebo plugins can be built with less
cores in order to avoid running out of RAM.
5 years ago
340e651d97
Build: properly read -j argument
...
The previous check for the -j argument was not actually working.
Therefore, the build always used 4 cores, unless when building with
ninja when presumably the ninja default was used.
5 years ago
08fdc90175
mission: keep current heading if close to ROI while heading sp is invalid
5 years ago
a9dacae57e
sensors/vehicle_angular_velocity: limit scheduling to IMU_GYRO_RATEMAX
5 years ago
96f043cd62
sensors/vehicle_acceleration: limit scheduling to IMU_INTEG_RATE
5 years ago
b36845330e
ms5611: prevent starting as ms5607 type on ms5611 hardware
...
- an ms5611 using the ms5607 calculations will return impossibly high barometric pressure (~2000 mbar)
5 years ago
b139f48fef
sensors: throttle mavlink emergency log messages
...
- in rare situations sending these messages multiple times in close succession can actually cause a loop of additional sensor timeouts
5 years ago
51a36f0b61
sensors/vehicle_imu: improve initial sensor interval monitoring
...
- add perf counters for monitoring
5 years ago
e34bdb4be9
move IMU integration out of drivers to sensors hub to handle accel/gyro sync
...
- IMU integration move from drivers (PX4Accelerometer/PX4Gyroscope) to sensors/vehicle_imu
- sensors: voted_sensors_update now consumes vehicle_imu
- delete sensor_accel_integrated, sensor_gyro_integrated
- merge sensor_accel_status/sensor_gyro_status into vehicle_imu_status
- sensors status output minor improvements (ordering, whitespace, show selected sensor device id and instance)
5 years ago
86cd1d0802
Hex CubeOrange: fix comment for TONE_ALARM_CHANNEL pin
5 years ago
b5ff82bccc
Hex CubeOrange: remove CAN Silence Silent mode pins
5 years ago
fd600d7eed
Hex CubeOrange: remove LSM303D
5 years ago
43279f18ba
bmp388: fix variable shadowing warning
5 years ago
9b2527549b
mavsdk_tests: relax timeout for offboard goto
...
This probably makes sense because we ask for more accuracy, so it will
take longer to reach a position.
5 years ago
bc1960ef2b
mavsdk_tests: make offboard tests more accurate
...
By making the acceptance radius smaller we should potentially also be
more accurate while landing and fail less.
5 years ago
David Sidrane
Julian Oes
David Jablonski
Daniel Agar
Dusan Zivkovic
Mirko Denecke
Beat Küng