update from upstream #1
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
waypoints in FlightTasks. In obstacle avoidace library reset desired avoidance waypoints after publication
to check progress
updateAvoidanceSetpoints->updateAvoidanceDesiredSetpoints
instance protected
loiter mode since it's the failsafe mode
With this change the param SDLOG_MODE can be used for SITL as well.
This prevents a warning message being printed to SITL users because the UAVCAN_ENABLE param does not exist.
When using QGC and/or the Dronecode SDK it was possible to get in a state where the two mavlink instances were both publishing their last heartbeat_time and cause commander to consistently toggle between data link lost and regained. With this fix, we only ever look at the very last heartbeat time and therefore seem to avoid this issue.
This should fix the macOS build.
- mavlink v2.0 in PX4/Firmware (88f2a68): mavlink/c_library_v2@171c837 - mavlink v2.0 current upstream: mavlink/c_library_v2@c6ab045 - Changes: mavlink/c_library_v2@171c837...c6ab045
- platform is optional and matters for Visual Studio builds - `ver` command shows the windows version and was just my first CI test
When sih (simulation in hardware) was compiled for Snapdragon, we got the linking problem below. I'm not sure why, supposedly the symbol `double sin(double)` is missing. undefined PLT symbol _LSin (705) /libpx4.so (symbol.c:303)
It looks like the atomic builtins are not available using QuRT and the Hexagon toolchain, so our best bet is to use `volatile` for the atomics.
…11973) - mavlink v2.0 in PX4/Firmware (0d543e2): mavlink/c_library_v2@d8c4e5d - mavlink v2.0 current upstream: mavlink/c_library_v2@5700013 - Changes: mavlink/c_library_v2@d8c4e5d...5700013
- jMAVSim in PX4/Firmware (7ec6f0d): PX4/jMAVSim@79586de - jMAVSim current upstream: PX4/jMAVSim@ae1593d - Changes: PX4/jMAVSim@79586de...ae1593d ae1593d 2019-04-30 Julian Oes - Merge pull request #100 from PX4/fix-port-default 9de8f86 2019-04-29 Julian Oes - Simulator: fix default for QGC and SDK link d42efaf 2019-04-29 Julian Oes - Merge pull request #99 from PX4/pr-add-sdk-port 7d0bebb 2019-04-26 Julian Oes - Simulator: fix copy paste mistake a94816e 2019-04-26 Julian Oes - Simulator: add MAVLink UDP port for SDK 6a9634b 2019-04-26 Julian Oes - Visualizer3D: ran fix_style.sh
- minimap size and display - title bar show file path and if modified - disable natural language search (sends keystrokes to Bing)
…_CUTOFF. A low gyro cutoff is needed for most medium/large size drones as the structural natural and blade-pass frequencies are low. A higher value is still desirable for small platforms surch as racers or well isolated autopilots and should be tuned by the user. Specific values for config files are untouched. The cutoff filter for the D term is disabled here as the required cutoff frequency for the default D term of the rate controller is higher than the gyro cutoff. In that case, enabling the D term cutoff would just add some undesired phase lag to the derivative.
To be able to still infer the direction of the thrust vector we limit it to a minimal length even if MPC_THR_MIN is set to zero. Note: This is a hotfix for certain specific applications. The direction of the thrust vector in this corner case is very likely to get into the tilt limit which is generally undesired.
Commander initially publishes a tune_control topic set to 0, which can interfere with the startup tone (as happening on the Pixhawk Cube).
- ecl in PX4/Firmware (fa1fbed): PX4/PX4-ECL@c4492b1 - ecl current upstream: PX4/PX4-ECL@a27a43e - Changes: PX4/PX4-ECL@c4492b1...a27a43e a27a43e 2019-05-01 Hamish Willee - Fix up link to EKF docs 3f69189 2019-04-04 Mohammed Kabir - EKF: control: stop vision yaw fusion on timeout
* VTOL trans: changed that now in transition for both MC and FW the corresponding (correct) attitude controller is running * attitude setpoint for stabilized mode is generated by tailsitter.cpp * reset yaw setpoint during transition to avoid big yaw errors after transition back to hover * VT_TYPE parameter: added "reboot required" metadata
visibility.h is included globally in PX4 via cmake compile flags. It contains poisoning the exit() command which is used by gtest to close the test application. Removing the flag for gtest compilation fixes the compile error: gtest.cc:4757:7: error: attempt to use poisoned "exit"
Example: Before when you passed "make tests TESTFILTER=Attitude" and subsequently "make tests TESTFILTER=Atti" it found the string "TESTFILTER=Atti" in "TESTFILTER=Attitude" and hence the check if the configuration is already correct passed. The fix checks for the configuration parameter including the subsequent space separator and after that strips the space away again such that the list VERIFIED_CMAKE_OPTIONS doesn't contain trailing spaces.
This brings support for UDP port 14550 and 14540 for HITL simulation.
This fixes cross-talk between the QGC and SDK UDP ports for HITL.
We forgot to add the option -s for jmavsim_run.sh which starts jMAVSim with the UDP port connecting to the SDK (port 14540).
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.
Test data / coverage
Logs uploaded to http://logs.px4.io or screenshots.
Describe problem solved by the proposed pull request
A clear and concise description of the problem, if any, this feature will solve. E.g. I'm always frustrated when ...
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 context or screenshots for the feature request here.