forked from PX4/PX4-Autopilot
-
Notifications
You must be signed in to change notification settings - Fork 1
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
upgrade repository #1
Merged
Merged
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
Updated the babyshark default parameters for improved flight performance, as well as two MPC parameters in vtol_defaults for smoother hovering with VTOLS" Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
- user defines a cone half angle which defines the RTL altitude behavior - if vehicle is outside the cone it will climb until it intersects the cone and then return at this altitude. - if vehicle is inside the cone or above the predefined return altitude (RTL_RETURN_ALT) then it will return at the current altitude Signed-off-by: RomanBapst <bapstroman@gmail.com>
Signed-off-by: RomanBapst <bapstroman@gmail.com>
- ecl in PX4/Firmware (590b55c): PX4/PX4-ECL@a036cf8 - ecl current upstream: PX4/PX4-ECL@e175118 - Changes: PX4/PX4-ECL@a036cf8...e175118 e175118 2019-06-28 bresch - EKF - Initialize _deadrekon_time_exceeded to true. If no sample have been received, deadrekoning and local position should be invalid.
- this limits console output at boot
…cruise speed. The linear mapping from position error to cruise velocity is changed by a combination of that linear mapping and a nonlinear function containing the maximum acceleration and jerk to avoid overshoots at waypoints due to overoptimistic breaking distance.
…position control, improved land detector, included autopilot rotation) Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
Signed-off-by: RomanBapst <bapstroman@gmail.com>
- this prevents low level board support from using PX4 logging, uORB, etc
On all of these boards '$USE_IO = no' will hold.
A board only needs to define: #define RC_SERIAL_PORT "/dev/ttyS4" Then it can optionally define one or more of the following: #define RC_SERIAL_SWAP_RXTX #define RC_SERIAL_SINGLEWIRE #define RC_INVERT_INPUT(_invert_true) px4_arch_gpiowrite(GPIO_SBUS_INV, _invert_true)
The parameter will only be available if the board defines an 'RC' serial port in SERIAL_PORTS (in default.cmake).
The 'if [ $LOG_FILE = /dev/null ]' block can be removed, because STARTUP_TUNE is already set in that case.
…config Not all m7 boards support double, as for example the STM32F745.
The combination of 'if mycmd' and a logical expression is not supported in NuttX.
…ious task to the new task This is done to allow proper initialization of the new FlightTask and give it a chance to continue the setpoints without discontinuity. The function checkSetpoints replaces the setpoints containing NANs with an estimate of the state. The estimate is usually the current estimate of the EKF or zero. The transition FlightTask also provides an estimate of the current acceleration to properly initialize the next FlightTask after back-transition. This avoid having to initialize the accelerations to zero knowing that the actual acceleration is usually far from zero.
…ilored to the specific needs and avoid checking all the setpoints
Work-around for #12485. This can be reverted after the root-cause is fixed.
* Set/unset rcS vars at beginning and end of rcS script and reduce a few LOC checking SYS_AUTOCONFIG with improved logic. * Restore current placement of set/unset vars in rcS script to leave only the SYS_AUTOCONFIG logic modification. * Replace set AUTOCNF no after inadvertent deletion.
NuttX 7.28 seemed to handle this gracefully, but officially passing NULL results in undefined behavior, and with 7.29 leads to a hardfault. This happens on configs with flash-based params, on the first unsuccessful import attempt.
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.
Please use PX4 Discuss or Slack to align on pull requests if necessary. You can then open draft pull requests to get early feedback.
Describe problem solved by the proposed pull request
A clear and concise description of the problem this proposed change will solve. E.g. For this use case I ran into...
Test data / coverage
How was it tested? What cases were covered? Logs uploaded to https://review.px4.io/ and screenshots of the important plot parts.
Describe your preferred solution
A clear and concise description of what you have implemented.
Describe possible alternatives
A clear and concise description of alternative solutions or features you've considered.
Additional context
Add any other related context or media.