test #2
Open
test #2
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
…TOCNF replacement)
…9:10 UTC 2021
- public_regulated_data_types in PX4/Firmware (5e242d3): https://github/commit/7f5489e6e916cc8b13db0582dcf9930e225594b9
- public_regulated_data_types current upstream: https://github/commit/53a7dbbf85554e11517c13ad91b9efb871599ad1
- Changes: https://github/compare/7f5489e6e916cc8b13db0582dcf9930e225594b9...53a7dbbf85554e11517c13ad91b9efb871599ad1
53a7dbb 2021-03-31 Pavel Kirienko - Change wording in uavcan.pnp.NodeIDAllocationData to reflect the less static nature of UAVCAN v1 (PX4#111)
c3aa82f 2021-03-23 Pavel Kirienko - Update Readiness as discussed at the DS-015 call
fcc1062 2021-03-16 Pavel Kirienko - Doc amendment for uavcan.register.Access: mapping between registers and environment variables (PX4#109)
342f358 2021-02-22 Pavel Kirienko - Remove misleading comment in battery.Status.0.2
1baa9cb 2021-02-22 Pavel Kirienko - Add link to Nunaweb and synchronize the description with the front page (PX4#108)
- sitl_gazebo in PX4/Firmware (2a0a747): PX4/PX4-SITL_gazebo-classic@e703e27 - sitl_gazebo current upstream: PX4/PX4-SITL_gazebo-classic@5761bd6 - Changes: PX4/PX4-SITL_gazebo-classic@e703e27...5761bd6 5761bd6 2021-04-05 Jaeyoung-Lim - Switch tailsitter sdf version to 1.6
- starting this earlier is a minor improvement for things like lights and buzzers on UAVCAN or parameter sync over mavlink
This helps in debugging slow CI.
This adds VTOL mission tests to the CI integration tests. This depends on MAVSDK v0.38.0.
This way it shouldn't matter where the test is run.
…when they provide a landing target with an unsupported coordinate frame. Updated Simulator::handle_message_landing_target to warn users when they provide a landing target that is not relative to a captured image.
The mavlink message FOLLOW_TARGET has additional fields that are not being parsed here. See https://mavlink.io/en/messages/common.html#FOLLOW_TARGET for more details.
Co-authored-by: Benjamin Linne <[email protected]>
Signed-off-by: Alex Mikhalev <[email protected]>
- ecl in PX4/Firmware (a300d32): PX4/PX4-ECL@a7b8afe - ecl current upstream: PX4/PX4-ECL@29243ac - Changes: PX4/PX4-ECL@a7b8afe...29243ac 29243ac 2021-05-05 bresch - yaw_reset: reduce minimum vector length to compute yaw error aad4840 2021-05-02 Kabir Mohammed - EKF: increase allowed difference between flow and gyro ODRs
[BACKPORT] binnfmt:Fix return before close ELF fd stm32h7: serial: use dma tx semaphore as resource holder [BACKPORT] stm32h7:Serial Add RX and TX DMA [BACKPORT] drivers/serial: fix Rx interrupt enable for cdcacm [BACKPORT] stm32h7:Allow for reuse of the OTG_ID GPIO [BACKPORT] stm32f7:Allow for reuse of the OTG_ID GPIO
... rather than across it
The calibration is not found in HITL mode. Therefore, I suggest to ignore this step and assume the calibration is fine. This mostly fixes the preflight check indicator in QGC, arming was (for some reason?) already possible.
This means that the preflight check indicator in QGC is green for HITL.
Otherwise ekf2 might not start if HITL isn't started within 30 seconds.
- update clean to recurse all build directories and use build system clean - git clean is used to remove submodule generated build artifacts that are left in the source tree - distclean now discards all build directories and any gitignored filess that were generated in source directories (but not top level)
stm32, F7 and H7
This fixes the simulation stalling after 30mins due to an int overflow.
Signed-off-by: RomanBapst <[email protected]>
- if geofence action is not none, then don't allow arming outside of geofence Signed-off-by: RomanBapst <[email protected]>
Signed-off-by: RomanBapst <[email protected]>
Signed-off-by: Silvan Fuhrer <[email protected]>
… feedback) Signed-off-by: Silvan Fuhrer <[email protected]>
Signed-off-by: Silvan Fuhrer <[email protected]>
Signed-off-by: Silvan Fuhrer <[email protected]>
Signed-off-by: Silvan Fuhrer <[email protected]>
Signed-off-by: Silvan Fuhrer <[email protected]>
The MB rover will wait as long as possible to compute a navigation solution, possibly lowering the navigation rate all the way to 1 Hz while doing so.
The allocation got changed to px4_cache_aligned_alloc
This avoids incremental build errors when switching between branches with a different set of airframes. E.g: Aborting due to missing @type tag in file: 'Firmware/build/px4_fmu-v5_default/etc/init.d/airframes/13030_generic_vtol_quad_tiltrotor'
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 this pull request
A clear and concise description of the problem this proposed change will solve.
E.g. For this use case I ran into...
Describe your 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.
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.
Additional context
Add any other related context or media.