Upstream merge 240620 #272
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
* Add support for illuminators - Add MAV_TYPE and MAV_COMPONENT enums for illuminators - Remove MAV_CMD_ILLUMINATOR_ON_OFF from wip - Add command to configure illuminator settings - Add messages to report illuminator status and information * Update common.xml Address PR comments and add `enable` field in `ILLUMINATOR_STATUS` to indicate if the illuminator is on or off * Update common.xml Address PR comments and fix formatting * Update common.xml Address PR comments (remove PID/VID), add illuminator firmware version, and add illuminator error flags * Update common.xml * Update common.xml Address PR comments: remove `serial_number` and `firmware_version` from `ILLUMINATOR_INFORMATION` and use `COMPONENT_INFORMATION_BASIC` instead * Update common.xml and development.xml Address PR comments: move COMPONENT_INFORMATION_BASIC from development to common and remove ILLUMINATOR_INFORMATION * 1. Resolve conflight: sync to most-up-to-date master and assign a new message id 440 to ILLUMINATOR_STATUS 2. Fix type and add `ILLUMINATOR_ERROR_FLAGS_THERMISTOR_FAILURE` error flag
* common.xml: deprecate MAV_CMD_SET_PARAMETER I don't think anybody actually implements this. ArduPilot doesn't. PX4 doesn't seem to. QGC doesn't seem to MissionPlanner doesn't. MAVProxy doesn't * Update message_definitions/v1.0/common.xml --------- Co-authored-by: Hamish Willee <[email protected]>
Add an EditorConfig to make sure editors know how to correctly edit and save files. Also strip trailing whitespace in some files that don't need it, as configured in the EditorConfig file.
* Improved docs from XML generation_toolchain - Make replaced-by a link - Fix message field desc - Make enums in param values into links - Fixes following testing - Add deprecated desc, if exists - Add todo if we ever get WIP tags with text in them - Make the main lists to dicts, to allow easier merging - Merge XMLs - Fix up ordering of items - Make more robust - can spot new fields - Improve table layout - Add max, min, invalid, instance, default, to fields - Add highlighting for WIP/Deprecated - Minor fix to intros - Add placeholder for building dialect tree - Add summary of stuff in THIS file - Flake8 Lint - Workflow to deploy docs + dependencies file * Update workflow to commit PR
* Fix typo for commands max value * Fix increment None
* FUEL_STATUS message proposal * Update message_definitions/v1.0/development.xml * Update message_definitions/v1.0/development.xml * development: change FUEL_STATUS id to fix duplication error (mavlink#2112) * Update message_definitions/v1.0/development.xml * Update message_definitions/v1.0/development.xml --------- Co-authored-by: Nuno Marques <[email protected]>
* gps: add status and resilience information Add fields to report resilience and status information from GNSS receivers back to ground control stations for representation in the user interface. * gps: separate GNSS integrity information Move the changes to the `GPS_RAW_INT` message into a separate message that supports multiple GNSS receivers. Update the enum values to better support all GNSS receivers. * gps(integrity): add RAIM info to `GNSS_INTEGRITY` message * gps(integrity): change `GNSS_INTEGRITY` message `id` field to instanced Change the `id` field on the `GNSS_INTEGRITY` message to make use of the instance support in the MAVLink schema. * gps(integrity): move integrity message to `development.xml` * gps(integrity): add jamming mitigated and spoofing critical Change the enums for jamming and spoofing so jamming includes a state for mitigated interference and spoofing no longer includes a message for critical spoofing. * gps(integrity): add units to `GNSS_INTEGRITY` RAIM fields * gps(integrity): add qualitative indicators to `GNSS_INTEGRITY` message Add qualitative fields for GNSS signal quality, incoming corrections quality and overall system status. GNSS receivers or drivers can compute these based on other data. They can be useful before takeoff and during flight as a reliable overview of important GNSS components. * gps(integrity): update quality indicators for unsupported drivers Add support for drivers that can't or don't want to provide the quality indicator information * gps(integrity): use invalid attribute to indicate invalid values Instead of having implicit invalid values, use the `invalid` attributes. Also add invalid values to the RAIM data as it may not always be supplied or available from receivers. * code review - invalid value for uint8 is 255 * Apply suggestions from code review * Update message_definitions/v1.0/development.xml --------- Co-authored-by: Hamish Willee <[email protected]>
Adds documentation that field `squawk` of ADSB_VEHICLE message is encoded in decimal, not in octal.
ThomasDebrunner
approved these changes
Jun 20, 2024
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.