forked from PX4/PX4-Autopilot
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP]: deprecate DriverFramework mpu9250 driver #19
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dagar
force-pushed
the
pr-mpu9250_DriverFramework_deprecate
branch
4 times, most recently
from
July 28, 2019 04:32
95c31f1
to
6d2edfc
Compare
…ance (PX4#11894) * Migrate variable initialization from constructor list to declaration uniform initialization, format whitespace, alphabetize/group/order variables and methods in ulanding.cpp. * Refactor the uLanding driver to utilize the ScheduledWorkQueue.
dagar
force-pushed
the
pr-mpu9250_DriverFramework_deprecate
branch
17 times, most recently
from
July 28, 2019 23:43
d950697
to
ae0ae74
Compare
- generally better attitude tracking - much better altitude control immediately after takeoff (hover throttle offset) - faster landing detection Signed-off-by: RomanBapst <[email protected]>
- we have set the maximum yaw-rate MC_YAWRATE_MAX to 200 degrees and it makes senses to leave a bit of margin between what the user can demand and what the limits of the vehicle are Signed-off-by: RomanBapst <[email protected]>
- vehicle will fly less aggressive - it does not make sense to set the lower acceleration limit to something that exceeds gravity if most of the vehicles do not support reverse thrust Signed-off-by: RomanBapst <[email protected]>
Signed-off-by: RomanBapst <[email protected]>
* fixes UAVCAN MAG calibration application after reboot
* This fix is necessary because usually uORB structs get initialized with all zeros and then get filled with the fields that are actually in use. * The number 0 for the mode slot was already commanding to switch to the mode in slot one even though for example the joystick input via mavlink does not use this mechanism at all.
- nuttx in PX4/Firmware (210dbb5): PX4/NuttX@257e173 - nuttx current upstream: PX4/NuttX@b4013dc - Changes: PX4/NuttX@257e173...b4013dc b4013dc 2019-08-01 David Sidrane - [BACKPORT] stm32l4:serial add HW HS on UART 4 & 5 4380c12 2019-08-01 David Sidrane - [BACKPORT] stm32h7:serial add HW HS on UART 4 & 5 0ff3e6c 2019-08-01 David Sidrane - [BACKPORT] stm32:serial add HW HS on UART 4 & 5 316126f 2019-07-31 David Sidrane - [BACKPORT] stm32f7:serial add HW HS on UART 4 & 5
- v2.0 in PX4/Firmware (d0f1a55): mavlink/c_library_v2@18cf6ff - v2.0 current upstream: mavlink/c_library_v2@7283284 - Changes: mavlink/c_library_v2@18cf6ff...7283284 7283284 2019-07-26 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/9c1d1feec0f2bd7ee7f408bed53f3de90a16c537 51a62d5 2019-07-23 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/06e378b91a620d20d99fe1476d57bc41e7210b18 477a5b6 2019-07-11 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/6e06b09b9ceb1d03c8f54e91494ab84901d33d9c 2a9615b 2019-07-10 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/e2c91dcc8c389a02a5e2f02b18662a951af7a33d cd2a362 2019-07-07 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/8b75e0a5a74429c98aa0b33a8b65fe3a7384d38d beb7890 2019-06-27 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/95031e31a5eec47dc951fc09e2939071b8cf3c2b 614164b 2019-06-27 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/595037a9fbd95ab51d84497f7d1cff3f998ba76e
dagar
force-pushed
the
pr-mpu9250_DriverFramework_deprecate
branch
3 times, most recently
from
August 2, 2019 03:36
c508591
to
0c9eb2f
Compare
* deprecate a goto statement * migrate to uniform initialization in LidarLite base class.
dagar
force-pushed
the
pr-mpu9250_DriverFramework_deprecate
branch
from
August 2, 2019 04:34
cc2cea8
to
6b0cf38
Compare
- DriverFramework in PX4/Firmware (eda49a4): PX4/DriverFramework@06277ef - DriverFramework current upstream: PX4/DriverFramework@c7d2fe2 - Changes: PX4/DriverFramework@06277ef...c7d2fe2 c7d2fe2 2019-07-23 Andrii Beregovenko - Fix missing symbol from librobotcontrol
dagar
force-pushed
the
pr-mpu9250_DriverFramework_deprecate
branch
3 times, most recently
from
August 2, 2019 20:33
b625196
to
c54c43e
Compare
dagar
force-pushed
the
pr-mpu9250_DriverFramework_deprecate
branch
from
August 2, 2019 20:38
c54c43e
to
846cdc2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.