diff --git a/.github/workflows/android-linux-qt6.6.3.yml b/.github/workflows/android-linux-qt6.6.3.yml index 8c3f14369b7..8ff8a64270a 100644 --- a/.github/workflows/android-linux-qt6.6.3.yml +++ b/.github/workflows/android-linux-qt6.6.3.yml @@ -7,6 +7,8 @@ on: - 'Stable*' tags: - 'v*' + paths-ignore: + - 'docs/**' # Do not trigger for any changes under docs pull_request: paths: - '.github/workflows/android-linux-qt6.6.3.yml' diff --git a/.github/workflows/android-linux.yml b/.github/workflows/android-linux.yml index 7d7a753b469..b6c21711416 100644 --- a/.github/workflows/android-linux.yml +++ b/.github/workflows/android-linux.yml @@ -7,6 +7,8 @@ on: - 'Stable*' tags: - 'v*' + paths-ignore: + - 'docs/**' # Do not trigger for any changes under docs pull_request: paths: - '.github/workflows/android-linux.yml' diff --git a/.github/workflows/android-macos.yml b/.github/workflows/android-macos.yml index a026eb16b19..98c56137d7c 100644 --- a/.github/workflows/android-macos.yml +++ b/.github/workflows/android-macos.yml @@ -7,6 +7,8 @@ on: - 'Stable*' tags: - 'v*' + paths-ignore: + - 'docs/**' # Do not trigger for any changes under docs pull_request: paths: - '.github/workflows/android-macos.yml' diff --git a/.github/workflows/android-windows.yml b/.github/workflows/android-windows.yml index 2ee3628f844..fc89cab3cbf 100644 --- a/.github/workflows/android-windows.yml +++ b/.github/workflows/android-windows.yml @@ -7,6 +7,8 @@ on: - 'Stable*' tags: - 'v*' + paths-ignore: + - 'docs/**' # Do not trigger for any changes under docs pull_request: paths: - '.github/workflows/android-windows.yml' diff --git a/.github/workflows/crowdin_download.yml b/.github/workflows/crowdin_docs_download.yml similarity index 87% rename from .github/workflows/crowdin_download.yml rename to .github/workflows/crowdin_docs_download.yml index b9dc1dccabe..28b7769e878 100644 --- a/.github/workflows/crowdin_download.yml +++ b/.github/workflows/crowdin_docs_download.yml @@ -3,6 +3,8 @@ name: Crowdin - Download Guide Translations # https://github.com/crowdin/github-action/tree/master on: + schedule: + - cron: '0 0 * * 0' # Runs every Sunday at 00:00 UTC workflow_dispatch: permissions: @@ -20,15 +22,16 @@ jobs: - name: crowdin action uses: crowdin/github-action@v2 with: - config: 'crowdin_docs.yml' + config: 'docs/crowdin_docs.yml' upload_sources: false upload_translations: false download_translations: true localization_branch_name: l10n_crowdin_docs_translations + crowdin_branch_name: master create_pull_request: true pull_request_title: 'New QGC guide translations (Crowdin)' pull_request_body: 'New QGC guide Crowdin translations by [Crowdin GH Action](https://github.com/crowdin/github-action)' - pull_request_base_branch_name: 'main' + pull_request_base_branch_name: 'master' env: # A classic GitHub Personal Access Token with the 'repo' scope selected (the user should have write access to the repository). GITHUB_TOKEN: ${{ secrets.PX4BUILDBOT_ACCESSTOKEN }} diff --git a/.github/workflows/crowdin_docs_upload.yml b/.github/workflows/crowdin_docs_upload.yml new file mode 100644 index 00000000000..ae644c80903 --- /dev/null +++ b/.github/workflows/crowdin_docs_upload.yml @@ -0,0 +1,44 @@ +name: Crowdin - Upload Guide sources (en) + +# https://github.com/crowdin/github-action/tree/master + +on: + push: + branches: + - master + paths: + - 'docs/en/**' + pull_request: + types: + - closed + branches: + - master + paths: + - 'docs/en/**' + workflow_dispatch: + +jobs: + upload-to-crowdin: + if: github.event.pull_request.merged == true || github.event_name == 'push' || github.event_name == 'workflow_dispatch' + runs-on: ubuntu-latest + + steps: + - name: Checkout + uses: actions/checkout@v4 + - name: crowdin push + uses: crowdin/github-action@v2 + with: + config: 'docs/crowdin_docs.yml' + upload_sources: true + upload_translations: false + download_translations: false + crowdin_branch_name: master + env: + # A classic GitHub Personal Access Token with the 'repo' scope selected (the user should have write access to the repository). + GITHUB_TOKEN: ${{ secrets.PX4BUILDBOT_ACCESSTOKEN }} + + # A numeric ID, found at https://crowdin.com/project//tools/api + CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_DOCS_PROJECT_ID }} + + # Visit https://crowdin.com/settings#api-key to create this token + CROWDIN_PERSONAL_TOKEN: ${{ secrets.PX4BUILDBOT_CROWDIN_PERSONAL_TOKEN }} diff --git a/.github/workflows/docker-linux.yml b/.github/workflows/docker-linux.yml index 03c924b26c1..985e1e8d7df 100644 --- a/.github/workflows/docker-linux.yml +++ b/.github/workflows/docker-linux.yml @@ -7,6 +7,8 @@ on: - 'Stable*' tags: - 'v*' + paths-ignore: + - 'docs/**' # Do not trigger for any changes under docs pull_request: paths: - '.github/workflows/docker-linux.yml' diff --git a/.github/workflows/linux.yml b/.github/workflows/linux.yml index e8e8c1c2ee3..c001eba45c5 100644 --- a/.github/workflows/linux.yml +++ b/.github/workflows/linux.yml @@ -7,6 +7,8 @@ on: - 'Stable*' tags: - 'v*' + paths-ignore: + - 'docs/**' # Do not trigger for any changes under docs pull_request: paths: - '.github/workflows/linux.yml' diff --git a/.github/workflows/macos.yml b/.github/workflows/macos.yml index e6ef15950d1..a5b11ee8591 100644 --- a/.github/workflows/macos.yml +++ b/.github/workflows/macos.yml @@ -7,6 +7,8 @@ on: - 'Stable*' tags: - 'v*' + paths-ignore: + - 'docs/**' # Do not trigger for any changes under docs pull_request: paths: - '.github/workflows/macos.yml' diff --git a/.github/workflows/windows.yml b/.github/workflows/windows.yml index a84aaae9fed..0c5488bd254 100644 --- a/.github/workflows/windows.yml +++ b/.github/workflows/windows.yml @@ -7,6 +7,8 @@ on: - 'Stable*' tags: - 'v*' + paths-ignore: + - 'docs/**' # Do not trigger for any changes under docs pull_request: paths: - '.github/workflows/windows.yml' diff --git a/cmake/find-modules/FindGStreamer.cmake b/cmake/find-modules/FindGStreamer.cmake index 58ebf3bc6e1..781c3656b0e 100644 --- a/cmake/find-modules/FindGStreamer.cmake +++ b/cmake/find-modules/FindGStreamer.cmake @@ -233,6 +233,9 @@ endif() if(ANDROID) target_link_options(GStreamer::GStreamer INTERFACE "-Wl,-Bsymbolic") + if(${ANDROID_ABI} STREQUAL "armeabi-v7a" OR ${ANDROID_ABI} STREQUAL "x86") + target_link_options(GStreamer::GStreamer INTERFACE "-Wl,-z,notext") + endif() endif() if(QGC_GST_STATIC_BUILD) diff --git a/crowdin_docs.yml b/docs/crowdin_docs.yml similarity index 92% rename from crowdin_docs.yml rename to docs/crowdin_docs.yml index 0e1091d7960..c3d35d94a3d 100644 --- a/crowdin_docs.yml +++ b/docs/crowdin_docs.yml @@ -1,6 +1,6 @@ "project_id_env": "CROWDIN_PROJECT_ID" "api_token_env": "CROWDIN_PERSONAL_TOKEN" -"base_path": "." +"base_path": "../" "preserve_hierarchy": true diff --git a/docs/ko/SUMMARY.md b/docs/ko/SUMMARY.md index b1ac96f407e..9493285e911 100644 --- a/docs/ko/SUMMARY.md +++ b/docs/ko/SUMMARY.md @@ -2,14 +2,24 @@ - [Overview](qgc-user-guide/index.md) - [Quick Start](qgc-user-guide/getting_started/quick_start.md) - - [Download and Install](qgc-user-guide/getting_started/download_and_install.md) + - [Download and Install (Daily 5.0)](qgc-user-guide/releases/daily_builds.md) - [Support](qgc-user-guide/support/support.md) -- [Fly](qgc-user-guide/fly_view/fly_view.md) +- [Fly View](qgc-user-guide/fly_view/fly_view.md) + - [Toolbar](qgc-user-guide/fly_view/fly_view_toolbar.md) + - [Fly Tools](qgc-user-guide/fly_view/fly_tools.md) + - [Instrument Panel](qgc-user-guide/fly_view/instrument_panel.md) + - [Attitude/Compass](qgc-user-guide/fly_view/hud.md) + - [Camera Tools](qgc-user-guide/fly_view/camera_tools.md) + - [Video](qgc-user-guide/fly_view/video.md) + - [Video Overlay](qgc-user-guide/fly_view/video_overlay.md) - [Replay Flight Data](qgc-user-guide/fly_view/replay_flight_data.md) - - [Video Overlay](qgc-user-guide/fly_view/video_overlay.md) -- [Plan](qgc-user-guide/plan_view/plan_view.md) +- [Mavlink Actions](qgc-user-guide/custom_actions/custom_actions.md) + +- [3D View](qgc-user-guide/viewer_3d/viewer_3d.md) + +- [Plan Flight](qgc-user-guide/plan_view/plan_view.md) - [GeoFence](qgc-user-guide/plan_view/plan_geofence.md) - [Rally Points](qgc-user-guide/plan_view/plan_rally_points.md) - [Pattern](qgc-user-guide/plan_view/pattern.md) @@ -19,7 +29,7 @@ - [Fixed Wing Landing Pattern](qgc-user-guide/plan_view/pattern_fixed_wing_landing.md) - [Pattern Presets](qgc-user-guide/plan_view/pattern_presets.md) -- [Vehicle Setup](qgc-user-guide/setup_view/setup_view.md) +- [Vehicle Configuration](qgc-user-guide/setup_view/setup_view.md) - [Firmware](qgc-user-guide/setup_view/firmware.md) - [Airframe](qgc-user-guide/setup_view/airframe.md) - [Airframe (ArduPilot)](qgc-user-guide/setup_view/airframe_ardupilot.md) @@ -61,15 +71,13 @@ - [Releases](qgc-user-guide/releases/index.md) - [Release Notes](qgc-user-guide/releases/release_notes.md) - - [v4.0 (Additional Notes)](qgc-user-guide/releases/stable_v4.0_additional.md) - - [v3.3 (Detailed)](qgc-user-guide/releases/stable_v3.3_long.md) - - [v3.2 (Detailed)](qgc-user-guide/releases/stable_v3.2_long.md) + - [QGC v4 Release Notes](qgc-user-guide/releases/release_note_stable_v4.md) + - [QGC v3 Release Notes](qgc-user-guide/releases/release_note_stable_v3.md) - [Daily Builds](qgc-user-guide/releases/daily_builds.md) - [Daily Build New Features](qgc-user-guide/releases/daily_build_new_features.md) - [Privacy Policy](qgc-user-guide/releases/privacy_policy.md) - [Troubleshooting](qgc-user-guide/troubleshooting/index.md) - - [Setup Problems](qgc-user-guide/troubleshooting/qgc_setup.md) - [Usage Problems](qgc-user-guide/troubleshooting/qgc_usage.md) - [Connection problems](qgc-user-guide/troubleshooting/vehicle_connection.md) @@ -80,11 +88,11 @@ - [Developer's Guide](qgc-dev-guide/index.md) - [Getting Started with source & builds](qgc-dev-guide/getting_started/index.md) - [Build using Containers](qgc-dev-guide/getting_started/container.md) - - [Using QGC on CentOS](qgc-dev-guide/getting_started/cent_os.md) + - [Navigating the Source Code](qgc-dev-guide/navigating_source.md) + - [Class Hierarchy](qgc-dev-guide/classes/index.md) - [QGC Release/Branching Process](qgc-dev-guide/release_branching_process.md) - [Communication Flow](qgc-dev-guide/communication_flow.md) - [Plugin Architecture](qgc-dev-guide/firmware_plugin.md) - - [Class Hierarchy](qgc-dev-guide/classes/index.md) - [User Interface Design](qgc-dev-guide/user_interface_design/index.md) - [Multi-Device Design Pattern](qgc-dev-guide/user_interface_design/multi_device_pattern.md) - [Font and Colour Palette](qgc-dev-guide/user_interface_design/font_palette.md) @@ -114,7 +122,6 @@ - [Release/Branching Process For Custom Builds](qgc-dev-guide/custom_build/release_branching_process.md) - [MAVLink](qgc-dev-guide/custom_build/mavlink.md) - [Code Submission](qgc-dev-guide/contribute/index.md) - - [Developer Call](qgc-dev-guide/contribute/dev_call.md) - [Coding Style](qgc-dev-guide/contribute/coding_style.md) - [Unit Tests](qgc-dev-guide/contribute/unit_tests.md) - [Pull Requests](qgc-dev-guide/contribute/pull_requests.md) diff --git a/docs/ko/index.md b/docs/ko/index.md index 500c3ad82a5..5c1063b3d1a 100644 --- a/docs/ko/index.md +++ b/docs/ko/index.md @@ -1,7 +1,7 @@ --- layout: home hero: - name: QGroundControl Guide + name: QGroundControl Guide (Daily Build 5.0) tagline: For beginners, experienced users, and developers actions: - theme: brand diff --git a/docs/ko/qgc-dev-guide/command_line_options.md b/docs/ko/qgc-dev-guide/command_line_options.md index 42e7e20dd94..edfabb64b20 100644 --- a/docs/ko/qgc-dev-guide/command_line_options.md +++ b/docs/ko/qgc-dev-guide/command_line_options.md @@ -30,16 +30,16 @@ Linux Terminal: The options/command line arguments are listed in the table below. -| Option | Description | -| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| `--clear-settings` | Clears the app settings (reverts _QGroundControl_ back to default settings). | -| `--logging:full` | Turns on full logging. See [Console Logging](../../qgc-user-guide/settings_view/console_logging.html#logging-from-the-command-line). | -| `--logging:full,LinkManagerVerboseLog,ParameterLoaderLog` | Turns on full logging and turns off the following listed comma-separated logging options. | -| `--logging:LinkManagerLog,ParameterLoaderLog` | Turns on the specified comma separated logging options | -| `--unittest:name` | (Debug builds only) Runs the specified unit test. Leave off `:name` to run all tests. | -| `--unittest-stress:name` | (Debug builds only) Runs the specified unit test 20 times in a row. Leave off :name to run all tests. | -| `--fake-mobile` | Simulates running on a mobile device. | -| `--test-high-dpi` | Simulates running _QGroundControl_ on a high DPI device. | +| Option | Description | +| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `--clear-settings` | Clears the app settings (reverts _QGroundControl_ back to default settings). | +| `--logging:full` | Turns on full logging. See [Console Logging](../../qgc-user-guide/settings_view/console_logging.html#logging-from-the-command-line). | +| `--logging:full,LinkManagerVerboseLog,ParameterLoaderLog` | Turns on full logging and turns off the following listed comma-separated logging options. | +| `--logging:LinkManagerLog,ParameterLoaderLog` | Turns on the specified comma separated logging options | +| `--unittest:name` | (Debug builds only) Runs the specified unit test. Leave off `:name` to run all tests. | +| `--unittest-stress:name` | (Debug builds only) Runs the specified unit test 20 times in a row. Leave off :name to run all tests. | +| `--fake-mobile` | Simulates running on a mobile device. | +| `--test-high-dpi` | Simulates running _QGroundControl_ on a high DPI device. | Notes: diff --git a/docs/ko/qgc-dev-guide/custom_build/mavlink.md b/docs/ko/qgc-dev-guide/custom_build/mavlink.md index 6423c43a4bb..24883618f8e 100644 --- a/docs/ko/qgc-dev-guide/custom_build/mavlink.md +++ b/docs/ko/qgc-dev-guide/custom_build/mavlink.md @@ -10,6 +10,6 @@ In order to add support for a new set of messages you should add them to [develo To modify the version of MAVLink used by QGC: - Replace the pre-build C library at [/qgroundcontrol/libs/mavlink/include/mavlink](https://github.com/mavlink/qgroundcontrol/tree/master/libs/mavlink/include/mavlink). - - By default this is a submodule importing https\://github.com/mavlink/c_library_v2 + - By default this is a submodule importing https://github.com/mavlink/c_library_v2 - You can change the submodule, or [build your own libraries](https://mavlink.io/en/getting_started/generate_libraries.html) using the MAVLink toolchain. - You can change the whole dialect used by setting it in [`MAVLINK_CONF`](https://github.com/mavlink/qgroundcontrol/blob/master/QGCExternalLibs.pri#L52) when running _qmake_. diff --git a/docs/ko/qgc-dev-guide/custom_build/release_branching_process.md b/docs/ko/qgc-dev-guide/custom_build/release_branching_process.md index 44890d6b03a..9023e149488 100644 --- a/docs/ko/qgc-dev-guide/custom_build/release_branching_process.md +++ b/docs/ko/qgc-dev-guide/custom_build/release_branching_process.md @@ -8,7 +8,7 @@ The best place to start is understanding the mechanism QGC uses to do it's own r ## Custom build/release types -Regular QGC has two main build types: Stable and Daily. The build type for a custom build is more complex. Throughout this discussion we will use the term "upstream" to refer to the main QGC repo (https\://github.com/mavlink/qgroundcontrol). Also when we talk about a "new" upstream stable release, this means a major/minor release, not a patch release. +Regular QGC has two main build types: Stable and Daily. The build type for a custom build is more complex. Throughout this discussion we will use the term "upstream" to refer to the main QGC repo (https://github.com/mavlink/qgroundcontrol). Also when we talk about a "new" upstream stable release, this means a major/minor release, not a patch release. ### Synchronized Stable diff --git a/docs/ko/qgc-dev-guide/custom_build/resource_override.md b/docs/ko/qgc-dev-guide/custom_build/resource_override.md index 2c8fa94eba1..37a3fdd7d01 100644 --- a/docs/ko/qgc-dev-guide/custom_build/resource_override.md +++ b/docs/ko/qgc-dev-guide/custom_build/resource_override.md @@ -1,8 +1,12 @@ # Resource Overrides -A "resource" in QGC source code terminology is anything found in the [qgroundcontrol.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgroundcontrol.qrc) and [qgcresources.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgcresources.qrc) file. By overriding a resource you can replace it with your own version of it. This could be as simple as a single icon, or as complex as replacing an entire Vehicle Setup page of qml ui code. +A "resource" in QGC source code terminology is anything found in Qt resources file: -Be aware that using resource overrides does not isolate you from upstream QGC changes like the plugin architecture does. In a sense you are directly modify the upstream QGC resources used by the main code. +- [qgroundcontrol.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgroundcontrol.qrc) and +- [qgcresources.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgcresources.qrc) file. +- [InstrumentValueIcons.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/resources/InstrumenValueIcons/InstrumentValueIcons.qrc) + +By overriding a resource you can replace it with your own version of it. This could be as simple as a single icon, or as complex as replacing an entire Vehicle Setup page of qml ui code. Be aware that using resource overrides does not isolate you from upstream QGC changes like the plugin architecture does. In a sense you are directly modify the upstream QGC resources used by the main code. ## Exclusion Files @@ -14,7 +18,7 @@ You must include the custom version of the overriden resouce in you custom build ## Generating the new modified versions of standard QGC resource file -This is done using the `updateqrc.py` python script. It will read the upstream `qgroundcontrol.qrc` and `qgcresources.qrc` file and the corresponding exclusion files and output new versions of these files in your custom directory. These new versions will not have the resources you specified to exclude in them. The build system for custom builds uses these generated files (if they exist) to build with instead of the upstream versions. The generated version of these file should be added to your repo. Also whenever you update the upstream portion of QGC in your custom repo you must re-run `python updateqrc.py` to generate new version of the files since the upstream resources may have changed. +This is done using the resource update python scripts:`python updateqrc.py` and `python updateinstrumentqrc.py`. It will read the upstream resouce files and the corresponding exclusion files and output new versions of these files in your custom directory. These new versions will not have the resources you specified to exclude in them. The build system for custom builds uses these generated files (if they exist) to build with instead of the upstream versions. The generated version of these file should be added to your repo. Also whenever you update the upstream portion of QGC in your custom repo you must re-run the scripts to generate new versions of the files since the upstream resources may have changed. ## Custom Build Example diff --git a/docs/ko/qgc-dev-guide/file_formats/plan.md b/docs/ko/qgc-dev-guide/file_formats/plan.md index 20babe1a5c7..41ea7195356 100644 --- a/docs/ko/qgc-dev-guide/file_formats/plan.md +++ b/docs/ko/qgc-dev-guide/file_formats/plan.md @@ -30,11 +30,11 @@ The main fields are: | Key | Description | | ------------------------------ | ------------------------------------------------------------------------------------------------- | -| `version` | The version for this file. Current version is 1. | -| `fileType` | Must be `"Plan"`. | +| `version` | The version for this file. Current version is 1. | +| `fileType` | Must be `"Plan"`. | | `groundStation` | The name of the ground station which created this file (here _QGroundControl_) | -| [`mission`](#mission) | The mission associated with this flight plan. | -| [`geoFence`](#geofence) | (Optional) Geofence information for this plan. | +| [`mission`](#mission) | The mission associated with this flight plan. | +| [`geoFence`](#geofence) | (Optional) Geofence information for this plan. | | [`rallyPoints`](#rally_points) | (Optional) Rally/Safe point information for this plan | ## Mission Object {#mission} @@ -82,15 +82,15 @@ The list may be a mix of both [SimpleItem](#mission_simple_item) and [ComplexIte The following values are required: -| Key | Description | -| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `version` | The version for the mission object. Current version is 2. | -| `firmwareType` | The firmware type for which this mission was created. This is one of the [MAV_AUTOPILOT](https://mavlink.io/en/messages/common.html#MAV_AUTOPILOT) enum values. | -| `globalPlanAltitudeMode` | The global plan-wide altitude mode setting. This is used by plan items that don't specify an `"AltitudeMode"`. | -| `vehicleType` | The vehicle type for which this mission was created. This is one of the [MAV_TYPE](https://mavlink.io/en/messages/common.html#MAV_TYPE) enum values. | +| Key | Description | +| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `version` | The version for the mission object. Current version is 2. | +| `firmwareType` | The firmware type for which this mission was created. This is one of the [MAV_AUTOPILOT](https://mavlink.io/en/messages/common.html#MAV_AUTOPILOT) enum values. | +| `globalPlanAltitudeMode` | The global plan-wide altitude mode setting. This is used by plan items that don't specify an `"AltitudeMode"`. | +| `vehicleType` | The vehicle type for which this mission was created. This is one of the [MAV_TYPE](https://mavlink.io/en/messages/common.html#MAV_TYPE) enum values. | | `cruiseSpeed` | The default forward speed for Fixed wing or VTOL vehicles (i.e. when moving between waypoints). | -| `hoverSpeed` | The default forward speed for multi-rotor vehicles. | -| `items` | The list of mission item objects associated with the mission . The list may contain either/both [SimpleItem](#mission_simple_item) and [ComplexItem](#mission_complex_item) objects. | +| `hoverSpeed` | The default forward speed for multi-rotor vehicles. | +| `items` | The list of mission item objects associated with the mission . The list may contain either/both [SimpleItem](#mission_simple_item) and [ComplexItem](#mission_complex_item) objects. | | `plannedHomePosition` | The planned home position is shown on the map and used for mission planning when no vehicle is connected. The array values shown above are (from top): latitude, longitude and AMSL altitude. | The format of the simple and complex items is given below. @@ -123,16 +123,16 @@ A simple item represents a single MAVLink [MISSION_ITEM](https://mavlink.io/en/m The field mapping is shown below. -| Key | Description | -| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `type` | `SimpleItem` for a simple item | -| `AMSLAltAboveTerrain` | Altitude value shown to the user. | -| `Altitude` | | -| `AltitudeMode` | | -| `autoContinue` | [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).autoContinue | +| Key | Description | +| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type` | `SimpleItem` for a simple item | +| `AMSLAltAboveTerrain` | Altitude value shown to the user. | +| `Altitude` | | +| `AltitudeMode` | | +| `autoContinue` | [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).autoContinue | | `command` | The command ([MAV_CMD](https://mavlink.io/en/messages/common.html#MAV_CMD)) for this mission item - see [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).command. | | `doJumpId` | The target id for the current mission item in DO_JUMP commands. These are auto-numbered from 1. | -| `frame` | [MAV_FRAME](https://mavlink.io/en/messages/common.html#MAV_FRAME) (see [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).frame) | +| `frame` | [MAV_FRAME](https://mavlink.io/en/messages/common.html#MAV_FRAME) (see [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).frame) | | `params` | [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).param1,2,3,4,x,y,z (values depends on the particular [MAV_CMD](https://mavlink.io/en/messages/common.html#MAV_CMD)). | ### Complex Mission Item {#mission_complex_item} @@ -176,14 +176,14 @@ The object definition for a `Survey` complex mission item is given below. Complex items have these values associated with them: -| Key | Description | -| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Key | Description | +| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `version` | The version number for this `survey` definition. Current version is 3. | -| `type` | `ComplexItem` (this is a complex item). | -| `complexItemType` | `survey` | -| [`TransectStyleComplexItem`](#TransectStyleComplexItem) | The common base definition for Survey and CorridorScan complex items. | -| `angle` | The angle for the transect paths (degrees). | -| `entryLocation` | ? | +| `type` | `ComplexItem` (this is a complex item). | +| `complexItemType` | `survey` | +| [`TransectStyleComplexItem`](#TransectStyleComplexItem) | The common base definition for Survey and CorridorScan complex items. | +| `angle` | The angle for the transect paths (degrees). | +| `entryLocation` | ? | | `flyAlternateTransects` | If true, the vehicle will skip every other transect and then come back at the end and fly these alternates. This can be used for fixed wing aircraft when the turnaround would be too acute for the vehicle to make the turn. | | `polygon` | The polygon array which represents the polygonal survey area. Each point is a latitude, longitude pair for a polygon vertex. | @@ -216,15 +216,15 @@ The object definition for a `CorridorScan` complex mission item is given below. }, ``` -| Key | Description | -| ------------------------------------------------------- | --------------------------------------------------------------------- | +| Key | Description | +| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | | `version` | The version for this `CorridorScan` definition. Current version is 3. | -| `type` | `ComplexItem` (this is a complex item). | -| `complexItemType` | `CorridorScan` | -| `CorridorWidth` | ? | -| `EntryPoint` | ? | -| [`TransectStyleComplexItem`](#TransectStyleComplexItem) | The common base definition for Survey and CorridorScan complex items. | -| `polyline` | ? | +| `type` | `ComplexItem` (this is a complex item). | +| `complexItemType` | `CorridorScan` | +| `CorridorWidth` | ? | +| `EntryPoint` | ? | +| [`TransectStyleComplexItem`](#TransectStyleComplexItem) | The common base definition for Survey and CorridorScan complex items. | +| `polyline` | ? | #### Structure Scan {#structure_scan} @@ -261,17 +261,17 @@ The object definition for a `StructureScan` complex mission item is given below. } ``` -| Key | Description | -| --------------------------- | ---------------------------------------------------------------------- | -| `version` | The version for this `StructureScan` definition. Current version is 2. | -| `type` | `ComplexItem` (this is a complex item). | -| `complexItemType` | `StructureScan` | -| `Altitude` | ? | -| [`CameraCalc`](#CameraCalc) | ? | -| `Layers` | ? | -| `StructureHeight` | ? | -| `altitudeRelative` | `true`: `altitude` is relative to home, `false`: `altitude` is AMSL. | -| `polygon` | ? | +| Key | Description | +| --------------------------- | -------------------------------------------------------------------------------------------------------------------- | +| `version` | The version for this `StructureScan` definition. Current version is 2. | +| `type` | `ComplexItem` (this is a complex item). | +| `complexItemType` | `StructureScan` | +| `Altitude` | ? | +| [`CameraCalc`](#CameraCalc) | ? | +| `Layers` | ? | +| `StructureHeight` | ? | +| `altitudeRelative` | `true`: `altitude` is relative to home, `false`: `altitude` is AMSL. | +| `polygon` | ? | #### `TransectStyleComplexItem` {#TransectStyleComplexItem} @@ -305,17 +305,17 @@ The object definition for a `StructureScan` complex mission item is given below. }, ``` -| Key | Description | -| --------------------------- | --------------------------------------------------------------------------------- | +| Key | Description | +| --------------------------- | ----------------------------------------------------------------------------------------------------------------- | | `version` | The version for this `TransectStyleComplexItem` definition. Current version is 1. | -| [`CameraCalc`](#CameraCalc) | ? | -| `CameraTriggerInTurnAround` | ? (boolean) | -| `FollowTerrain` | ? (boolean) | -| `HoverAndCapture` | ? (boolean) | -| `Items` | ? | -| `Refly90Degrees` | ? (boolean) | -| `TurnAroundDistance` | The distance to fly past the polygon edge prior to turning for the next transect. | -| `VisualTransectPoints` | ? | +| [`CameraCalc`](#CameraCalc) | ? | +| `CameraTriggerInTurnAround` | ? (boolean) | +| `FollowTerrain` | ? (boolean) | +| `HoverAndCapture` | ? (boolean) | +| `Items` | ? | +| `Refly90Degrees` | ? (boolean) | +| `TurnAroundDistance` | The distance to fly past the polygon edge prior to turning for the next transect. | +| `VisualTransectPoints` | ? | ##### CameraCalc {#CameraCalc} @@ -344,26 +344,26 @@ The `CameraCalc` contains camera information used for a survey, corridor or stru }, ``` -| Key | Description | -| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `version` | The version for this `CameraCalc` definition. Current version is 1. | -| `AdjustedFootprintFrontal` | ? | -| `AdjustedFootprintSide` | ? | -| `DistanceToSurface` | ? Units? | -| `DistanceToSurfaceRelative` | ? | +| Key | Description | +| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `version` | The version for this `CameraCalc` definition. Current version is 1. | +| `AdjustedFootprintFrontal` | ? | +| `AdjustedFootprintSide` | ? | +| `DistanceToSurface` | ? Units? | +| `DistanceToSurfaceRelative` | ? | | `CameraName` | Name of camera being used (must correspond to one of the cameras known to _QGroundControl_ or: `Manual (no camera specs)` for manual setup, `Custom Camera` for a custom setup. The keys listed after this point are not specified for a "Manual" camera definition. | -| `FixedOrientation` | ? (boolean) | -| `FocalLength` | Focal length of camera lens in millimeters. | -| `FrontalOverlap` | Percentage of frontal image overlap. | -| `ImageDensity` | ? | -| `ImageHeight` | Image height in px | -| `ImageWidth` | Image width in px | +| `FixedOrientation` | ? (boolean) | +| `FocalLength` | Focal length of camera lens in millimeters. | +| `FrontalOverlap` | Percentage of frontal image overlap. | +| `ImageDensity` | ? | +| `ImageHeight` | Image height in px | +| `ImageWidth` | Image width in px | | `Landscape` | `true`: Camera installed in landscape orientation on vehicle, `false`: Camera installed in portrait orientation on vehicle. | -| `MinTriggerInterval` | ? | -| `SensorHeight` | Sensor height in millimeters. | -| `SensorWidth` | Sensor width in millimeters. | -| `SideOverlap` | Percentage of side image overlap. | -| `ValueSetIsDistance` | ? (boolean) | +| `MinTriggerInterval` | ? | +| `SensorHeight` | Sensor height in millimeters. | +| `SensorWidth` | Sensor width in millimeters. | +| `SideOverlap` | Percentage of side image overlap. | +| `ValueSetIsDistance` | ? (boolean) | ## GeoFence {#geofence} @@ -384,11 +384,11 @@ The minimal definition is shown below. The fields are: -| Key | Description | -| ------------------------------- | ---------------------------------------------------------------------------------- | -| `version` | The version number for the geofence plan format. The documented version is 2. | -| [`circles`](#circle_geofence) | List containing circle geofence definitions (comma separated). | -| [`polygons`](#polygon_geofence) | List containing polygon geofence definitions (comma separated). | +| Key | Description | +| ------------------------------- | ------------------------------------------------------------------------------------------------------------- | +| `version` | The version number for the geofence plan format. The documented version is 2. | +| [`circles`](#circle_geofence) | List containing circle geofence definitions (comma separated). | +| [`polygons`](#polygon_geofence) | List containing polygon geofence definitions (comma separated). | ### Circle Geofence {#circle_geofence} @@ -408,11 +408,11 @@ The items define the centre and radius of the circle, and whether or not the spe The fields are: -| Key | Description | -| ----------- | --------------------------------------------------------------------------------------------------------------------- | +| Key | Description | +| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | `version` | The version number for the geofence "circle" plan format. The documented version is 1. | | `circle` | The definition of the circle. Includes `centre` (latitude, longitude) and `radisu` as shown above. | -| `inclusion` | Whether or not the geofence is enabled (true) or disabled. | +| `inclusion` | Whether or not the geofence is enabled (true) or disabled. | ### Polygon Geofence {#polygon_geofence} @@ -449,11 +449,11 @@ The geofence includes a set of points defined with a clockwise winding (i.e. the The fields are: -| Key | Description | -| ----------- | ------------------------------------------------------------------------------------------------------------------------------ | -| `version` | The version number for the geofence "polygon" plan format. The documented version is 2. | +| Key | Description | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `version` | The version number for the geofence "polygon" plan format. The documented version is 2. | | `polygon` | A list of points for the polygon. Each point contains a latitude and longitude. The points are ordered in a clockwise winding. | -| `inclusion` | Whether or not the geofence is enabled (true) or disabled. | +| `inclusion` | Whether or not the geofence is enabled (true) or disabled. | ## Rally Points {#rally_points} @@ -483,7 +483,7 @@ A definition with two points is shown below. The fields are: -| Key | Description | -| --------- | -------------------------------------------------------------------------------- | +| Key | Description | +| --------- | ---------------------------------------------------------------------------------------------------------------- | | `version` | The version number for the rally point plan format. The documented version is 2. | -| `points` | A list of rally points. | +| `points` | A list of rally points. | diff --git a/docs/ko/qgc-dev-guide/getting_started/container.md b/docs/ko/qgc-dev-guide/getting_started/container.md index 3bdda672439..5baae13faa7 100644 --- a/docs/ko/qgc-dev-guide/getting_started/container.md +++ b/docs/ko/qgc-dev-guide/getting_started/container.md @@ -12,11 +12,21 @@ The main advantage of using the container is the usage of the `CMake` build syst ## Building the Container -Before using the container, you have to build the image. +### Script + +To build the container using the script, run this command in the qgc root directory + +``` +./deploy/docker/run-docker-ubuntu.sh +``` + +### Manual + +if you want to Build using the container manually, then you first have to build the image. You can accomplish this using docker, running the following script from the root of the QGC source code directory. ``` -docker build --file ./deploy/docker/Dockerfile-build-linux -t qgc-linux-docker . +docker build --file ./deploy/docker/Dockerfile-build-ubuntu -t qgc-ubuntu-docker . ``` :::info @@ -28,7 +38,7 @@ Keep in mind this is tagging the image for later reference since you can have mu If building on a Mac computer with an M1 chip you must also specify the build option `--platform linux/x86_64` as shown: ``` -docker build --platform linux/x86_64 --file ./deploy/docker/Dockerfile-build-linux -t qgc-linux-docker . +docker build --platform linux/x86_64 --file ./deploy/docker/Dockerfile-build-ubuntu -t qgc-ubuntu-docker . ``` Otherwise you will get a build error like: @@ -46,15 +56,20 @@ We recommend you create a `build` directory on the source tree and then run the ``` mkdir build -docker run --rm -v ${PWD}:/project/source -v ${PWD}/build:/project/build qgc-linux-docker +docker run --rm -v ${PWD}:/project/source -v ${PWD}/build:/project/build qgc-ubuntu-docker ``` +::: info +For up to date docker command and options reference relevant run-script in `deploy/docker`, for example [run-docker-ubuntu.sh](https://github.com/mavlink/qgroundcontrol/blob/master/deploy/docker/run-docker-ubuntu.sh#L16). + +::: + ::: info If using the script to build the Linux image on a Windows host, you would need to reference the PWD differently. On Windows the docker command is: ``` -docker run --rm -v %cd%:/project/source -v %cd%/build:/project/build qgc-linux-docker +docker run --rm -v %cd%:/project/source -v %cd%/build:/project/build qgc-ubuntu-docker ``` ::: diff --git a/docs/ko/qgc-dev-guide/getting_started/index.md b/docs/ko/qgc-dev-guide/getting_started/index.md index a8df17fe625..a23d2f39bc4 100644 --- a/docs/ko/qgc-dev-guide/getting_started/index.md +++ b/docs/ko/qgc-dev-guide/getting_started/index.md @@ -1,5 +1,5 @@ --- -qt_version: 6.6.1 +qt_version: 6.8.2 --- # Getting Started with Source and Builds @@ -14,7 +14,7 @@ Versions are provided for all platforms. ## Source Code -Source code for _QGroundControl_ is kept on GitHub here: https\://github.com/mavlink/qgroundcontrol. +Source code for _QGroundControl_ is kept on GitHub here: https://github.com/mavlink/qgroundcontrol. It is [dual-licensed under Apache 2.0 and GPLv3](https://github.com/mavlink/qgroundcontrol/blob/master/.github/COPYING.md). To get the source files: @@ -59,10 +59,6 @@ There is a significant risk that other Qt versions will inject bugs that affect For more information see: [Qt 6 supported platform list](https://doc.qt.io/qt-6/supported-platforms.html). -:::info -Native [CentOS Builds](../getting_started/cent_os.md) are also supported, but are documented separately (as the tested environment is different). -::: - #### Install Qt You **must install Qt as described below** instead of using pre-built packages from say, a Linux distribution. @@ -72,83 +68,64 @@ To install Qt: 1. Download and run the [Qt Online Installer](https://www.qt.io/download-qt-installer-oss) - **Ubuntu:** - Set the downloaded file to executable using: `chmod +x`. - - You may also need to install libxcb-cursor. - -2. In the installer _Select Components_ dialog choose: Qt {{ $frontmatter.qt_version }}. - - Then install the following components: - - - Under _Qt _{{ $frontmatter.qt_version }}_ select: - - Depending on the OS you want to build for: - - **Windows**: _MSVC 2019 64 bit_ - - **MacOS**: _macOS_ - - **Linux**: _Desktop gcc 64-bit_ - - **Android**: _Android_ - - _Qt 5 Compatibility Module_ - - _Qt Shader Tools_ - - Under _Additional Libraries_ select: - - _Qt Charts_ - - _Qt Connectivity_ - - _Qt Location (TP)_ - - _Qt Multimedia_ - - _Qt Positioning_ - - _Qt Serial Port_ - - _Qt Speech_ - -3. Install Additional Packages (Platform Specific) - - - **Ubuntu:** `sudo apt-get install speech-dispatcher libudev-dev libsdl2-dev patchelf build-essential` + - You may also need to install libxcb-cursor0 + +2. On the _Installation Folder_ page select "Custom Installation" + +3. On the _Select Components_ page: + + - I you don't see _Qt {{ $frontmatter.qt_version }}_ listed check the _Archive_ checkbox and click _Filter_. + +- Under Qt -> _Qt {{ $frontmatter.qt_version }}_ select: + - **Windows**: MSVC 2022 _arch_ - where _arch_ is the architecture of your machine + - **Mac**: Desktop + - **Linux**: Desktop gcc 64-bit + - **Android**: Android +- Select all _Additional Libraries_ +- Deselect QT Design Studio + +1. Install Additional Packages (Platform Specific) + + - **Ubuntu:** `sudo bash ./qgroundcontrol/tools/setup/install-dependencies-debian.sh` - **Fedora:** `sudo dnf install speech-dispatcher SDL2-devel SDL2 systemd-devel patchelf` - **Arch Linux:** `pacman -Sy speech-dispatcher patchelf` - - **OSX** [Setup](https://doc.qt.io/qt-6/macos.html) - - **Android** [Setup](https://doc.qt.io/qt-6/android-getting-started.html) + - **Mac** `sh qgroundcontrol/tools/setup/macos-dependencies.sh` + - **Android** [Setup](https://doc.qt.io/qt-6/android-getting-started.html). JDK17 is required for the latest updated versions. NDK Version: 25.1.8937393 + You can confirm it is being used by reviewing the project setting: **Projects > Manage Kits > Devices > Android (tab) > Android Settings > _JDK location_**. + Note: Visit here for more detailed configurations [android.yml](.github/workflows/android.yml) -4. Install Optional/OS-Specific Functionality +2. Install Optional/OS-Specific Functionality ::: info Optional features that are dependent on the operating system and user-installed libraries are linked/described below. These features can be forcibly enabled/disabled by specifying additional values to qmake. ::: - - **Video Streaming/Gstreamer:** - see [Video Streaming](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoReceiver/README.md). + - **Video Streaming/Gstreamer:** - see [Video Streaming](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoManager/VideoReceiver/GStreamer/README.md) -#### Building using Qt Creator {#qt-creator} +#### Install Visual Studio (Windows Only) {#vs} -1. Launch _Qt Creator_ and open the **qgroundcontrol.pro** project. +Install [Visual Studio 2022 Community Edition](https://visualstudio.microsoft.com/downloads/). -2. In the **Projects** section, select the appropriate kit for your needs: +When installing, select _Desktop development with C++_ as shown: - - **OSX:** Desktop Qt {{ $frontmatter.qt_version }} clang 64 bit +![Visual Studio 2019 - Select Desktop Environment with C++](../../../assets/dev_getting_started/visual_studio_select_features.png) - ::: info - iOS builds must be built using [XCode](http://doc.qt.io/qt-5/ios-support.html). - ::: +:::info +Visual Studio is ONLY used to get the compiler. Building _QGroundControl_ is done using [Qt Creator](#qt-creator) or [cmake](#cmake) directly as outlined below. +::: - - **Ubuntu:** Desktop Qt {{ $frontmatter.qt_version }} GCC 64bit +#### Building using Qt Creator {#qt-creator} - - **Windows:** Desktop Qt {{ $frontmatter.qt_version }} MSVC2019 **64bit** +1. Launch _Qt Creator_, select Open Project and select the **CMakeLists.txt** file. - - **Android:** Android for armeabi-v7a (GCC 4.9, Qt {{ $frontmatter.qt_version }}) - - JDK11 is required. - You can confirm it is being used by reviewing the project setting: **Projects > Manage Kits > Devices > Android (tab) > Android Settings > _JDK location_**. +2. On the _Configure Project_ page it should default to the version of Qt you just installed using the instruction above. If not select that kit from the list and click _Configure Project_. -3. Build using the "hammer" (or "play") icons: +3. Build using the "hammer" (or "play") icons or the menus: ![QtCreator Build Button](../../../assets/dev_getting_started/qt_creator_build_qgc.png) -#### Install Visual Studio 2019 (Windows Only) {#vs} - -The Windows compiler can be found here: [Visual Studio 2019 compiler](https://visualstudio.microsoft.com/vs/older-downloads/) (64 bit) - -When installing, select _Desktop development with C++_ as shown: - -![Visual Studio 2019 - Select Desktop Environment with C++](../../../assets/dev_getting_started/visual_studio_select_features.png) - -:::info -Visual Studio is ONLY used to get the compiler. Actually building _QGroundControl_ should be done using [Qt Creator](#qt-creator) or [qmake](#qmake) as outlined below. -::: - -#### Build using qmake on CLI {#qmake} +#### Build using CMake on CLI {#cmake} Example commands to build a default QGC and run it afterwards: @@ -158,40 +135,22 @@ Example commands to build a default QGC and run it afterwards: cd qgroundcontrol ``` -2. Create and enter a shadow build directory: - - ```sh - mkdir build - cd build - ``` - -3. Configure the build using the qmake script in the root of the repository: - - ```sh - qmake ../ - ``` - -4. Run make to compile and link. - To accelerate the process things you can use the `-j{number of threads}` parameter. +2. Configure: ```sh - make -j12 + cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Debug ``` - ::: info - You can also specify build time flags here. - For example, you could disable airmap inclusion using the command: +3. Build ```sh - DEFINES+=DISABLE_AIRMAP make build + cmake --build build --config Debug ``` - ::: - -5. Run the QGroundcontrol binary that was just built: +4. Run the QGroundcontrol binary that was just built: ```sh - ./staging/QGroundControl + ./build/Debug/QGroundControl ``` ### Vagrant @@ -212,14 +171,6 @@ Example commands to build a default QGC and run it afterwards: You can additionally create installation file(s) for _QGroundControl_ as part of the normal build process. -:::tip -On Windows you will need to first install [NSIS](https://sourceforge.net/projects/nsis/). -::: - -To add support for installation file creation you need to add `CONFIG+=installer` to your project file, or when you call _qmake_. - -To do this in _Qt Creator_: - -- Open **Projects > Build > Build Steps > qmake > Additional arguments**. -- Enter `CONFIG+=installer` as shown: - ![Installer](../../../assets/dev_getting_started/qt_project_installer.png) +```sh +cmake --install . --config Release +``` diff --git a/docs/ko/qgc-dev-guide/index.md b/docs/ko/qgc-dev-guide/index.md index 9be96cc1f60..51252011bc8 100644 --- a/docs/ko/qgc-dev-guide/index.md +++ b/docs/ko/qgc-dev-guide/index.md @@ -1,6 +1,7 @@ # QGroundControl Dev Guide -[![Releases](https://img.shields.io/github/release/mavlink/QGroundControl.svg)](https://github.com/mavlink/QGroundControl/releases) [![Discuss](https://img.shields.io/badge/discuss-dev-ff69b4.svg)](http://discuss.px4.io/c/qgroundcontrol/qgroundcontrol-developers) +[![Discuss](https://img.shields.io/badge/discuss-dev-ff69b4.svg)](http://discuss.px4.io/c/qgroundcontrol/qgroundcontrol-developers) +[![Discord](https://discordapp.com/api/guilds/1022170275984457759/widget.png?style=shield)](https://discord.com/channels/1022170275984457759/1022185820683255908) This developer guide is the best source for information if you want to build, modify or extend [QGroundControl](http://qgroundcontrol.com) (QGC). It shows how to obtain and build the source code, explains how QGC works, and provides guidelines for contributing code to the project. @@ -11,14 +12,14 @@ This part of the guide is for **developers**! :::warning This is an active work in progress - information should be correct, but may not be complete! -If you find that it is missing helpful information (or errors) please raise an issue. +If you find that it is missing helpful information (or errors) please raise an issue or better yet submit a pull request to the docs with updated information. ::: ## Design Philosophy QGC is designed to provide a single codebase that can run across multiple OS platforms as well as multiple device sizes and styles. -The QGC user interface is implemented using [Qt QML](http://doc.qt.io/qt-5/qtqml-index.html). QML provides for hardware acceleration which is a key feature on lower powered devices such as tablets or phones. QML also provides features which allows us to more easily create a single user interface which can adapt itself to differing screen sizes and resolution. +The QGC user interface is implemented using Qt Qml. Qml provides for hardware acceleration which is a key feature on lower powered devices such as tablets or phones. Qml also provides features which allows us to more easily create a single user interface which can adapt itself to differing screen sizes and resolution. The QGC UI targets itself more towards a tablet+touch style of UI than a desktop mouse-based UI. This make a single UI easier to create since tablet style UI also tends to work fine on desktop/laptops. @@ -35,10 +36,6 @@ We expect all contributors to adhere to the [QGroundControl code of conduct](htt This code aims to foster an open and welcoming environment. ::: -### Coordination Call - -The developer team meets bi-weekly to discuss the highest priority issues, project coordination, and discuss any Issues, PRs, or Questions from the Community. ([Developer Call Details](contribute/dev_call.md)) - ### Translations We use [Crowdin](https://crowdin.com) to make it easier to manage translation for both _QGroundControl_ and the documentation. @@ -61,8 +58,6 @@ For more information see: [Licenses](contribute/licences.md). ## Governance -The QGroundControl mission planner is hosted under the governance of the [Dronecode Project](https://www.dronecode.org/). - -Dronecode Logo Linux Foundation Logo +The QGroundControl ground station is hosted under the governance of the [Dronecode Project](https://www.dronecode.org/).
 
diff --git a/docs/ko/qgc-dev-guide/navigating_source.md b/docs/ko/qgc-dev-guide/navigating_source.md new file mode 100644 index 00000000000..b8a3657e034 --- /dev/null +++ b/docs/ko/qgc-dev-guide/navigating_source.md @@ -0,0 +1,20 @@ +# Navigating QGC Source Code + +QGC is a large code base. With that it can be daunting to find what your are looking for in the source. Below are listed some tips to help you find what you are looking for. + +## Start from the top of the UI + +The top level window Qml UI code is found in `MainRootWindow.qml`. You can start here and work your way down through the UI hierarchy till you find what you are looking for. + +In this qml file you'll find things like: + +- How the toolbar is created +- How the top level views are created: Fly, Plan, ... + +## Global Search + +The best way to find something is to find the UI which is closest to what you are looking for by doing text searches. + +### Example: Find the source for the GPS drop down in the toolbar + +In the dropdown you see the words "Vehicle GPS Status". Do a global search for those words. Make sure you are doing a case sensitive search. Also make sure you are matching whole words. It can also be helpful to exclude the `*.ts` translation files. Since they can lead to multiple results. If you do the search described here it will take you right to `GPSIndicatorPage.qml`. Some times a search may lead to many results in both qml and .cpp files. In this case limit the results to `*.qml` files. diff --git a/docs/ko/qgc-dev-guide/plan/mission_command_tree.md b/docs/ko/qgc-dev-guide/plan/mission_command_tree.md index 55441b4e3fc..80dddd367dd 100644 --- a/docs/ko/qgc-dev-guide/plan/mission_command_tree.md +++ b/docs/ko/qgc-dev-guide/plan/mission_command_tree.md @@ -83,7 +83,7 @@ Let's walk through an example hierarchy for `MAV_CMD_NAV_WAYPOINT`. Root informa ### Root - Vehicle Type Specific leaf node -The next level of the hiearchy is generic mavlink but vehicle specific. Json files are here: [MR](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoMultiRotor.json), [FW](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoFixedWing.json), [ROVER](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoRover.json), [Sub](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoSub.json), [VTOL](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoVTOL.json). And here are the overrides for (Fixed Wings)(https\://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoFixedWing.json#L7): +The next level of the hiearchy is generic mavlink but vehicle specific. Json files are here: [MR](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoMultiRotor.json), [FW](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoFixedWing.json), [ROVER](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoRover.json), [Sub](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoSub.json), [VTOL](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoVTOL.json). And here are the overrides for (Fixed Wings)(https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoFixedWing.json#L7): ``` { diff --git a/docs/ko/qgc-dev-guide/release_branching_process.md b/docs/ko/qgc-dev-guide/release_branching_process.md index da2a0671f6c..0b65a5d4cd8 100644 --- a/docs/ko/qgc-dev-guide/release_branching_process.md +++ b/docs/ko/qgc-dev-guide/release_branching_process.md @@ -74,7 +74,8 @@ A proposed strategy for branching on custom builds can be found [here](custom_bu 2. Create a tag on the HEAD of master name `dX.Y` where the minor version is one greater than the new Stable. For example if you are create a new Stable 4.2 version then the tag would be 'd4.3'. This tag is used to create the version numbers for Android daily builds. Example: `git tag -a d4.3.0 -m "QGroundControl Daily Android Version Base"`. 3. Create an annotated tag on the newly created Stable branch named `vX.Y.0` with the correct major/minor version number. Example: `git tag -a v4.2.0 -m "QGroundControl v4.2.0"`. Pushing this tag to the repo will start a build. 4. Once the build completes verify the builds are pushed up to S3 correctly and sanity check that they at least boot correctly. Location on S3 will be `https://qgroundcontrol.s3.us-west-2.amazonaws.com/latest/...`. -5. Update the `https://qgroundcontrol.s3.us-west-2.amazonaws.com/builds/latest/QGC.version.txt` text file to the latest Stable version. This will notify uses there is a new Stable available the next time they launch QGC. +5. Update the `https://qgroundcontrol.s3.us-west-2.amazonaws.com/latest/QGC.version.txt` text file to the latest Stable version. This will notify users that there is a new Stable available the next time they launch QGC. +6. Note that the cached cloudfront downloads will take up to 24h to refresh. If they need to update earlier, the caches would need to be manually invalidated. ### Patch Version diff --git a/docs/ko/qgc-dev-guide/user_interface_design/controls.md b/docs/ko/qgc-dev-guide/user_interface_design/controls.md index 16bbca6fbed..c7e0840916c 100644 --- a/docs/ko/qgc-dev-guide/user_interface_design/controls.md +++ b/docs/ko/qgc-dev-guide/user_interface_design/controls.md @@ -33,3 +33,4 @@ These custom controls are exclusive to QGC and are used to create standard UI el - QGCViewPanel - The main view contents inside of a QGCView. - RoundButton - A round button control which uses an image as its inner contents. - SetupPage - The base control for all Setup vehicle component pages. Provides a title, description and component page contents area. +- SelectableControl - Allows users to select from a list of controls to display. Right-click on Desktop or Press and Hold on Mobile will show selection UI. Example usage: Allows user to select between multiple Instrument display variants. diff --git a/docs/ko/qgc-dev-guide/views/fly.md b/docs/ko/qgc-dev-guide/views/fly.md index a9f5a8e6c7c..15e0379a69c 100644 --- a/docs/ko/qgc-dev-guide/views/fly.md +++ b/docs/ko/qgc-dev-guide/views/fly.md @@ -1,6 +1,6 @@ # Fly View -- Top level QML code is in **FlightDisplayView\.qml** +- Top level QML code is in **FlightDisplayView.qml** - QML code communicates with `MissionController` (C++) for mission display - Instrument widgets communicate with active Vehicle object - Two main inner views are: diff --git a/docs/ko/qgc-dev-guide/views/setup.md b/docs/ko/qgc-dev-guide/views/setup.md index 0dd51a0b157..2b011fa12d6 100644 --- a/docs/ko/qgc-dev-guide/views/setup.md +++ b/docs/ko/qgc-dev-guide/views/setup.md @@ -1,5 +1,5 @@ # Setup View -- Top level QML code implemented in **SetupView\.qml** +- Top level QML code implemented in **SetupView.qml** - Fixed set of buttons/pages: Summary, Firmware - Remainder of buttons/pages come from AutoPilotPlugin VehicleComponent list diff --git a/docs/ko/qgc-user-guide/custom_actions/custom_actions.md b/docs/ko/qgc-user-guide/custom_actions/custom_actions.md new file mode 100644 index 00000000000..82a56ac8f2c --- /dev/null +++ b/docs/ko/qgc-user-guide/custom_actions/custom_actions.md @@ -0,0 +1,44 @@ +# Custom Mavlink Action + +Both the Fly View and Joysticks support the ability execute arbitrary mavlink commands to the active vehicle. In the Fly View these will show up in the Toolstrip Action list. With Joysticks you can assign then to button presses. + +## Mavlink Actions File + +The actions available are defined in a JSON file. The format of that file is as follows: + +``` +{ + "version": 1, + "fileType": "MavlinkActions", + "actions": [ + { + "label": "First Mavlink Command", + "description": "This is the first command", + "mavCmd": 10, + "compId": 100, + "param1": 1, + "param2": 2, + ... + }, + { + "label": "Second Mavlink Command", + "description": "This is the second command", + "mavCmd": 20, + ... + } + ] +} +``` + +Fields: + +- actions (required) - An array of json objects, one for each command +- label (required) - The user visible short description for the command. This is used as the button text for the Fly View - Actions command list. For Joysticks, this is the command you select from the dropdown. For Joysticks, make sure your name doesn't conflict with the built in names. +- description (required) - This is a longer description of the command used in the Fly View - Action list. This is not used by joysticks. +- mavCmd (required) - The command id of the mavlink command you want to send. +- compId (options) - The component id for where you want to send the command to. If not specified `MAV_COMP_ID_AUTOPILOT1` is used. +- param1 thru param7 (optional) - The parameters for the command. Parameters which are not specified will default to 0.0 + +Mavlink action files should be located in the MavlinkActions directory of the QGC save location. For example on Linux that would be `~/Documents/QGroundControl/MavlinkActions` or `~/Documents/QGroundControl Daily/MavlinkActions`. The Fly View and Joysticks can each have there own custom actions file. + +When you start up QGC it will load these files if they exist and make the commands available for use. diff --git a/docs/ko/qgc-user-guide/fly_view/camera_tools.md b/docs/ko/qgc-user-guide/fly_view/camera_tools.md new file mode 100644 index 00000000000..a1cd5980e3c --- /dev/null +++ b/docs/ko/qgc-user-guide/fly_view/camera_tools.md @@ -0,0 +1,29 @@ +# Camera Tools + +The camera tools are used to capture still images and video, and to configure the camera. + +![Camera Panel](../../../assets/fly/camera_panel/camera_mavlink.png) + +The camera capture and configuration options depend on the connected camera. +The configuration options are selected using the panel gear icon. +The configuration for a simple autopilot-connected camera are shown below. + +![Camera Panel - minimal settings](../../../assets/fly/camera_panel/camera_settings_minimal.png) + +When connected to camera that supports the [MAVLink Camera Protocol](https://mavlink.io/en/services/camera.html) you can additionally configure and use other camera services that it makes available. +For example, if your camera supports video mode you will be able to switch between still image capture and video mode, and start/stop recording. + +![Camera Panel - MAVLink settings](../../../assets/fly/camera_panel/camera_settings_mavlink.png) + +::: info +Most of the settings that are displayed depend on the camera (they are defined in its [MAVLink Camera Definition File](https://mavlink.io/en/services/camera_def.html)). + +> A few common settings at the end are hard-coded: Photo Mode (Single/Time Lapse), Photo Interval (if Time Lapse), Reset Camera Defaults (sends a reset command to the camera), Format (storage) +> ::: + +### Video Stream {#video_instrument_page} + +The video page is used to enable/disable video streaming. +When enabled, you can start/stop the video stream, enable a grid overlay, change how the image fits the screen, and record the video locally with QGC. + +![Instrument Page - Video Stream](../../../assets/fly/instrument_page_video_stream.jpg) diff --git a/docs/ko/qgc-user-guide/fly_view/fly_tools.md b/docs/ko/qgc-user-guide/fly_view/fly_tools.md new file mode 100644 index 00000000000..dff94728e21 --- /dev/null +++ b/docs/ko/qgc-user-guide/fly_view/fly_tools.md @@ -0,0 +1,60 @@ +# Fly Tools + +## Pre Flight Checklist {#preflight_checklist} + +An automated preflight checklist can be used to run through standard checks that the vehicle is configured correctly and it is safe to fly. + +To view the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../settings_view/general.md) and selecting the **Use preflight checklist** checkbox. +The tool will then be added to the _Flight Tools_. +Press it to open the checklist: + +![Pre Flight Checklist](../../../assets/fly/pre_flight_checklist.jpg) + +Once you have performed each test, select it on the UI to mark it as complete. + +## Takeoff {#takeoff} + +:::tip +If you are starting a mission for a multicopter, _QGroundControl_ will automatically perform the takeoff step. +::: + +To takeoff (when landed): + +1. Press the **Takeoff** button in the _Fly Tools_ (this will toggle to a **Land** button after taking off). +2. Optionally set the takeoff altitude in the right-side vertical slider. + +- You can slide up/down to change the altitude +- You can also click on the specified altitude (10 ft in example) and then type in a specific altitude. + +1. Confirm takeoff using the slider. + +![takeoff](../../../assets/fly/takeoff.png) + +## Land {#land} + +You can land at the current position at any time while flying: + +1. Press the **Land** button in the _Fly Tools_ (this will toggle to a **Takeoff** button when landed). +2. Confirm landing using the slider. + +## RTL/Return + +Return to a "safe point" at any time while flying: + +1. Press the **RTL** button in the _Fly Tools_. +2. Confirm RTL using the slider. + +:::info +Vehicles commonly return to the "home" (takeoff) location and land. +This behaviour depends on the vehicle type and configuration. +For example, rally points or mission landings may be used as alternative return targets. +::: + +## Change Altitude {#change_altitude} + +You can change altitude while flying, except when in a mission: + +1. Press the **Actions** button on the _Fly Tools_ +2. Select the _Change Altitude_ button +3. Select the new altitude from the vertical slider +4. Confirm the action diff --git a/docs/ko/qgc-user-guide/fly_view/fly_view.md b/docs/ko/qgc-user-guide/fly_view/fly_view.md index fee14e05745..de8e6826e9d 100644 --- a/docs/ko/qgc-user-guide/fly_view/fly_view.md +++ b/docs/ko/qgc-user-guide/fly_view/fly_view.md @@ -1,294 +1,46 @@ # Fly View -비행 화면은 비행중인 기체에 명령어를 실행하고 그 결과를 모니터링합니다. +The Fly View is used to command and monitor the vehicle. -다음과 같은 목적으로 사용할 수 있습니다: - -- 자동화된 [비행 전 체크리스트](#preflight_checklist)를 제공합니다. -- Arm the vehicle (or check why it won't arm). -- 미션 제어:: [시작](#start_mission), [계속](#continue_mission), [일시중지](#pause) 및 [재개](#resume_mission). -- 기체의 [시동](#arm)/[시동 해제](#disarm)/[비상 정지](#emergency_stop), [이륙](#takeoff)/[착륙](#land), [고도 변경](#change_altitude), 특정 위치로 [이동](#goto) 또는 [궤도](#orbit), [복귀/RTL](#rtl)할 수 있습니다. -- 지도 화면과 동영상 화면간의 전환(사용 가능한 경우) -- 현 기체의 비디오 출력, 미션, 텔레메트리 및 기타 정보를 표시하고 연결된 기체간에 전환합니다. +## Overview ![비행 뷰](../../../assets/fly/fly_view_overview.jpg) -## UI 개요 - -위의 스크린샷은 비행 화면의 주요 요소를 나타냅니다. - -- **지도:** 연결된 모든 기체의 위치와 현재 차량의 임무를 표시합니다. - - 지도를 드래그하여 이동할 수 있습니다(일정 시간이 지나면 지도가 자동으로 중앙에 위치함). +- **[Toolbar](fly_view_toolbar.md):** The toolbar is at the top of the screen. It provides controls to select views, show flight status and mode as well as the status of the main components of the vehicle. +- **[Vehicle Actions](fly_tools.md):** Allows you command the vehicle to take a specific action. +- **[Instrument Panel](instrument_panel.md):** A widget that displays vehicle telemetry. +- **[Attitude/Compass](hud.md):** A widget that provides virtual horizon and heading information. +- **[Camera Tools](camera_tools.md)**: A widget for switching between still and video modes, starting/stopping capture, and controlling camera settings. +- **[Video](video.md):** Display the video from the vehicle. Allows you to toggle between video or map as the main display. +- **Map:** Displays the positions of all connected vehicles and the mission for the current vehicle. + - You can drag the map to move it around (the map automatically re-centres on the vehicle after a certain amount of time). + - You can zoom the map in and out using the zoom buttons, mouse wheel, track pad or pinch on a tablet. - 비행 후에는 지도를 클릭하여 [이동](#goto) 또는 [궤도](#orbit) 위치를 설정할 수 있습니다. -- **비행 툴바:** 센서(GPS, 배터리, RC 제어) 및 차량 상태(비행 모드, 무장/해제 상태)에 대한 주요 상태 정보. - - 더 자세히 보려면 센서 표시기를 선택하십시오. - - 새 모드를 선택하려면 _비행 모드_ 텍스트(예: "Hold")를 누르십시오. - 모든 모드를 사용할 수 있는 것은 아닙니다. - - The text next to the **Q** icon indicates the flight readiness using text: "Not Ready", "Ready to Fly", "Flying", and status using colour: "green" (all good!), amber (a warning), red (serious problem). - Select the text when the background is amber or red to find out the cause of any preflight issues (QGC 4.2.0 and later). - You can also select the text to reach a button to arm/disarm/emergency-stop the vehicle. -- **비행 도구:** 다음과 같은 목적으로 사용할 수 있습니다: - - Toggle between takeoff/land. - - 현재 작업(예: 착륙 또는 미션)을 일시 중지하거나 재시작합니다. - - 안전 복귀(RTL 또는 복귀라고도 함). - - _작업_ 버튼은 현재 상태에 대한 적절한 옵션을 제공합니다(이 옵션은 _확인 슬라이더_와 중첩됨). - 조치에는 고도 변경과 미션 지속을 포함됩니다. - - [실행 전 체크리스트](#preflight_checklist)를 활성화합니다(도구 옵션은 기본적으로 비활성화되어 있음). -- **[Instrument Panel](#instrument_panel):** A widget that displays vehicle telemetry. -- **Attitude/Compass**: A widget that provides virtual horizon and heading information. -- **Camera Tools**: A widget for switching between still and video modes, starting/stopping capture, and controlling camera settings. -- **[동영상/전환기](#video_switcher):** 창에서 비디오 또는 지도를 전환합니다. - - 요소를 눌러 _동영상_ 및 _지도_를 전경으로 전환합니다. - - _QGroundControl_은 UDP 프로토콜을 이용하여 RTP 및 RTSP 비디오를 스트리밍합니다. - 또한, 직접 연결된 UVC 장치를 지원합니다. - QGroundControl 비디오 지원은 [비디오 README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md)을 참고하십시오. - - [텔레메트리 오버레이](../fly_view/video_overlay.md)가 자막 파일로 자동 생성됩니다. -- **확인 슬라이더:** 요청된 작업을 확인하는 슬라이더입니다. - 슬라이드하여 작동을 시작합니다. 취소하려면 **X**를 클릭하십시오. - -기본적으로 표시되지 않거나 특정 조건에서만 표시되는 다른 요소들 많습니다. -예를 들어, 다중 기체 선택기는 여러 대의 기체가 연결된 경우에만 표시되며, 비행 전 체크리스트 도구 버튼은 적절한 설정이 활성화된 경우에만 표시됩니다. - -## 계기판 {#instrument_panel} - -The instrument panel displays telemetry information about the current vehicle. - -![계기 페이지 - 값/원격 측정용](../../../assets/fly/instrument_page_values.jpg) - -기본적으로 고도(홈 위치 기준) 및 지면 속도입니다. - -패널 왼쪽 상단의 작은 톱니바퀴 아이콘을 눌러 표시할 정보를 설정할 수 있습니다. -This toggles the position of the panel between bottom centre and right-centre. - -![Instrument Panel - hover for move/edit tools](../../../assets/fly/instrument_panel/instrument_panel_tools_move_edit.png) - -You configure what information is display by selecting the edit/pencil icon. -The grid will then display "+" and "-" icons that you can use to add or remove rows and columns (and the pencil icon is replaced by a "lock" icon that you can use to save the settings). - -![Instrument Panel - add rows/columns](../../../assets/fly/instrument_panel/instrument_panel_tools_edit_on.png) - -Select a value to launch its "Value Display" editor. -This allows you to change the icon, text, size, units and so on of the current telemetry value. - -![계기 페이지 - 값 설정](../../../assets/fly/instrument_page_values_settings.jpg) - -The selection list on the top left is used to change the source of the telemetry. -By default this is the vehicle, but you can use the selector to choose a particular sensor type. - -![계기 페이지 - 카메라용](../../../assets/fly/instrument_page_camera.jpg) - -The selection list on the top right is used to select a particular telemetry value for the vehicle or sensor. - -비행 중인 기체의 시동을 꺼려면 _비행 도구 모음_에서 **시동**을 선택합니다. - -### 카메라 {#camera_instrument_page} - -The camera panel is used to capture still images and video, and to configure the camera. - -![계기 페이지 - 카메라 MAVLink 설정](../../../assets/fly/instrument_page_camera_mavlink.jpg) - -The camera capture and configuration options depend on the connected camera. -The configuration options are selected using the panel gear icon. -The configuration for a simple autopilot-connected camera are shown below. - -![Camera Panel - minimal settings](../../../assets/fly/camera_panel/camera_settings_minimal.png) - -[MAVLink 카메라 프로토콜](https://mavlink.io/en/services/camera.html)을 지원하는 카메라에 연결하면, 사용 가능한 다른 카메라 서비스를 추가로 설정하고 사용할 수 있습니다. -예를 들어, 카메라가 비디오 모드를 지원하는 경우 정지 이미지 캡처와 비디오 모드 사이를 전환하고 녹화를 시작하고 중지할 수 있습니다. - -![계기 페이지 - 카메라 MAVLink 설정](../../../assets/fly/instrument_page_camera_mavlink_settings.jpg) - -::: info -Most of the settings that are displayed depend on the camera (they are defined in its [MAVLink Camera Definition File](https://mavlink.io/en/services/camera_def.html)). -> 마지막에 몇 가지 일반적인 설정이 하드 코딩되어 있습니다: 사진 모드(단일/인터벌), 사진 간격(인터벌인 경우), 카메라 기본값 재설정(카메라에 재설정 명령 전송), 포맷(저장) - -### 비디오 스트림 {#video_instrument_page} - -비디오 페이지는 비디오 스트리밍을 활성화 하거나 비활성화 합니다. -활성화시에는 비디오 스트림을 시작하고, 그리드 오버레이를 활성화하고, 이미지가 화면에 맞는 방식을 변경하고, QGroundControl을 사용하여 로컬로 비디오를 녹화할 수 있습니다. - -![계기 페이지 - 비디오 스트림](../../../assets/fly/instrument_page_video_stream.jpg) +There are a number of other elements that are not displayed by default and are only displayed in certain conditions or for certain vehicle types. ## 액션/태스크 다음 섹션에서는 비행 화면에서 일반적인 작업 수행 방법을 설명합니다. -::: info -Many of the available options depend on both the vehicle type and its current state. -::: - -### 비행 전 점검 사항 {#preflight_checklist} - -자동 비행 전 점검을 통하여 기체의 설정과 비행 안전 여부를 검사합니다. - -적검 항목을 사용하려면 [애플리케이션 설정 > 일반 > 비행 화면](../settings_view/general.md)로 이동하고 **비행 전 점검 항목 사용**을 선택하여 도구를 활성화합니다. -그러면, _비행 도구_에 도구가 추가됩니다. -점검 항목들을 열려면 클릭합니다. - -![비행 전 점검 리스트](../../../assets/fly/pre_flight_checklist.jpg) - -각 테스트 수행 후 UI에서 해당 테스트를 선택하여 완료로 표시합니다. - -### 시동 {#arm} - -Arming a vehicle starts the motors in preparation for takeoff. -You will only be able to arm the vehicle if it is safe and ready to fly. - -:::tip -Generally, if the vehicle is ready to arm, _QGroundControl_ will arm the vehicle for you if you start a mission or takeoff. -::: - -The vehicle is ready to fly in all modes if the status text says "Ready to Fly" and the background is green. - -![Vehicle state - ready to fly green/ready background](../../../assets/fly/vehicle_states/ready_to_fly_ok.png) - -If the background is amber then it is ready to take off in the current mode, but may not be able to switch to other modes. -If the background is red and the text is "Not Ready" then you will not be able to arm in the current mode. - -![Vehicle state - ready to fly amber/warning background](../../../assets/fly/vehicle_states/ready_to_fly_warning.png) -![Vehicle state - not ready](../../../assets/fly/vehicle_states/not_ready.png) - -From QGC 4.2.0 (at time of writing, a daily build) you can find out the exact cause of the warning or error, and possible solutions, by pushing the status text. - -This launches the preflight arming checks popup with a list of all preflight warnings. -The toggle on the right expands each error with additional information and possible solutions. - -![UI To check arming warnings](../../../assets/fly/vehicle_states/arming_preflight_check_ui.png) - -Once each issue is resolved it will disappear from the UI. -When all issues blocking arming have been removed you can use the arm button to display the arming confirmation slider, and arm the vehicle (or you can just take off - note that the vehicles will (by default) disarm automatically if you do not take off after a few seconds. - -![계기 페이지 - 진동 클립](../../../assets/fly/instrument_page_vibration.jpg) - -::: info -The status text also displays when flying. - -> ![계기 페이지 - 차량 건강](../../../assets/fly/instrument_page_health_good.jpg) ![계기 페이지 - 차량 상태 불량](../../../assets/fly/instrument_page_health_bad.jpg) -> -> The arming checks UI will open even when flying, allowing you to emergency disarm. -> ::: - -### 시동 끄기 {#disarm} - -기체의 시동이 꺼지면, 모터는 정지합니다(기체를 안전한 상태로 변경함). - -Generally you do not need to explicitly disarm as vehicles will disarm automatically after landing, or shortly after arming if you do not take off. - -If needed, you can do so from the Arming Preflight Checks UI. - -![시동](../../../assets/fly/arm.jpg) - -You will then need to use the disarming slider. - -![시동 끄기](../../../assets/fly/disarm.jpg) - -비행 중 기체의 시동을 꺼는 것을 [비상 정지](#emergency_stop)라고 합니다. - -### 비상 정지 {#emergency_stop} - -비상 정지는 비행 중 기체의 시동을 꺼는 것과 동일합니다. -Your vehicle will crash! - -If needed, you can do so from the Arming Preflight Checks UI. - -기체의 시동을 꺼려면 기체가 **착륙**하였을 때 _비행 도구 모음_에서 **시동**을 선택하십시오. - -You will then need to use the emergency disarming slider. - -![비상 정지](../../../assets/fly/emergency_stop.jpg) - -### 이륙 {#takeoff} - -:::tip -멀티콥터의 미션을 시작하면, _QGroundControl_에서 자동으로 이륙 단계를 수행합니다. -::: - -이륙 절차(착륙 후): - -1. _비행 도구_에서 **이륙** 버튼을 클릭합니다(이륙 후 **착륙** 버튼으로 전환됨). -2. 오른쪽 수직 슬라이더에서 이륙 고도를 설정할 수 있습니다. -3. 슬라이더를 사용하여 이륙 실행을 확인합니다. - -![이륙](../../../assets/fly/takeoff.png) - -### 착륙 {#land} - -비행 중에는 언제든 지 현재 위치에 착륙 가능합니다. - -1. _비행 도구_에서 **착륙** 버튼을 클릭합니다(착륙 시 **이륙** 버튼으로 전환됨). -2. 슬라이더를 사용하여 착륙 실행을 확인합니다. - -![착륙](../../../assets/fly/land.jpg) - -### RTL/Return - -비행 중 언제든 지 "안전 지점"으로 복귀할 수 있습니다. - -1. _비행 도구_에서 **RTL** 버튼을 클릭합니다. -2. 슬라이더를 사용하여 착륙지 복귀 실시를 확인합니다. - -![출발지복귀](../../../assets/fly/rtl.jpg) - :::info -기체는 일반적으로 "홈"(이륙) 위치와 착륙 지점으로 복귀합니다. -이 동작은 기체 유형과 설정에 따라 차이가 날 수 있습니다. -예를 들어, 집결지나 임무 착륙을 대체 반환 목표로 사용할 수 있습니다. -::: - -### 고도 변경 {#change_altitude} - -미션 수행중을 제외하고는, 비행 중 고도 변경이 가능합니다. - -1. _비행 도구_에서 **액션** 버튼을 클릭합니다. - -2. 대화상자에서 _고도 변경_ 작업을 선택합니다. - - ![임무 계속/고도 변경 작업](../../../assets/fly/continue_mission_change_altitude_action.jpg) - -3. 수직 슬라이더를 원하는 고도로 이동한 다음 확인 슬라이더를 끌어 작업을 실행합니다. - - ![고도 변경](../../../assets/fly/change_altitude.jpg) - -### 위치 이동 {#goto} - -이륙후 특정 위치 이동을 지정할 수 있습니다. - -1. 지도에서 기체의 이동 지점을 왼쪽 클릭 후, 팝업에서 **위치 이동**을 선택합니다. - -![계속 또는 선회](../../../assets/fly/goto_or_orbit.jpg) - -1. 위치는 확인 슬라이더와 함께 지도에 표시됩니다. - - ![계속 확인](../../../assets/fly/goto.jpg) - -2. 준비가 되면 슬라이더를 끌어 작업을 시작합니다(또는 **X** 아이콘을 눌러 취소). - -:::info -위치 이동 지점은 기체에서 1km 이내로 설정하여야 합니다(QGroundControl에 하드 코딩됨). +Many of the available options depend on both the vehicle type and its current state. ::: -### 선회 비행 {#orbit} - -이륙 후 특정 위치 선회를 지정할 수 있습니다. - -1. 지도(원하는 궤도의 중심 부근)를 마우스 왼쪽 버튼 클릭후, 팝업에서 **위치에서 궤도**를 선택합니다. +### Actions associated with a map position (#map_actions) -![계속 또는 선회](../../../assets/fly/goto_or_orbit.jpg) +There are a number of actions which can be taken which are associated with a specific position on the map. To use these actions: -1. 예정 궤도는 확인 슬라이더와 함께 지도에 표시됩니다. +1. Click on the map at a specific position +2. A popup will display showing you the list of available actions +3. Select the action you want +4. Confirm the action - ![선회 확인](../../../assets/fly/orbit.jpg) - - - 중심 마커를 선택하고 끌어서 궤도 위치를 이동합니다. - - 외부 원의 점을 선택하고 끌어 궤도 반경을 변경합니다. - -2. 준비가 되면 슬라이더를 끌어서 작업을 시작합니다(또는 **X** 아이콘을 눌러 취소). +Examples of map position actions are Go To Location, Orbit and so forth. ### 일시 중지 -이륙, 착륙, RTL, 임무 실행 및 위치 궤도를 포함한 대부분의 작업을 일시 중지할 수 있습니다. -일시 정지 시 기체의 동작은 기체 유형에 따라 달라집니다. 일반적으로 멀티콥터는 호버링을 하고, 고정익은 선회 비행을합니다. +이륙, 착륙, RTL, 임무 실행 및 위치 궤도를 포함한 대부분의 작업을 일시 중지할 수 있습니다. 일시 정지 시 기체의 동작은 기체 유형에 따라 달라집니다. 일반적으로 멀티콥터는 호버링을 하고, 고정익은 선회 비행을합니다. :::info _위치 이동_ 작업은 일시 중지가 불가능 합니다. @@ -300,8 +52,6 @@ _위치 이동_ 작업은 일시 중지가 불가능 합니다. 2. 선택적으로 오른쪽 수직 슬라이더를 사용하여 새 고도를 설정합니다. 3. 슬라이더를 사용하여 일시 중지를 확인합니다. -![일시 중지](../../../assets/fly/pause.jpg) - ### 미션 #### 미션 시작 {#start_mission} diff --git a/docs/ko/qgc-user-guide/fly_view/fly_view_toolbar.md b/docs/ko/qgc-user-guide/fly_view/fly_view_toolbar.md new file mode 100644 index 00000000000..1895c883cfd --- /dev/null +++ b/docs/ko/qgc-user-guide/fly_view/fly_view_toolbar.md @@ -0,0 +1,78 @@ +# Fly View Toolbar + +![Fly View](../../../assets/fly/toolbar/fly_view_toolbar.jpg) + +## Views + +The "Q" icon on the left of the toolbar allows you to select between additional top level views: + +- **[Plan Flight](../plan_view/plan_view.md):** Used to create missions, geo-fences and rally points +- **Analyze Tools:** A set of tools for things like log download, geo-tagging images, or viewing telemetry. +- **Vehicle Configuration:** The various options for the initial configuration of a new vehicle. +- **Application Settings:** Settings for the QGroundControl application itself. + +## Toolbar Indicators + +Next are a multiple toolbar indicators for vehicle status. The dropdowns for each toolbar indicator provide additional detail on status. You can also expand the indicators to show additional application and vehicle settings associated with the indicator. Press the ">" button to expand. + +![Toolbar Indicator - expand button](../../../assets/fly/toolbar_indicator_expand.png) + +### Flight Status + +The Flight Status indicator shows you whether the vehicle is ready to fly or not. It can be in one of the following states: + +- **Ready To Fly** (_green background_) - Vehicle is ready to fly +- **Ready To Fly** (_yellow background_) - Vehicle is ready to fly in the current flight mode. But there are warnings which may cause problems. +- **Not Ready** - Vehicle is not ready to fly and will not takeoff. +- **Armed** - Vehicle is armed and ready to Takeoff. +- **Flying** - Vehicle is in the air and flying. +- **Landing** - Vehicle is in the process of landing. +- **Communication Lost** - QGroundControl has lost communication with the vehicle. + +The Flight Status Indicator dropdown also gives you acess to: + +- **Arm** - Arming a vehicle starts the motors in preparation for takeoff. You will only be able to arm the vehicle if it is safe and ready to fly. Generally you do not need to manually arm the vehicle. You can simply takeoff or start a mission and the vehicle will arm itself. +- **Disarm** - Disarming a vehicle is only availble when the vehicle is on the ground. It will stop the motors. Generally you do not need to explicitly disarm as vehicles will disarm automatically after landing, or shortly after arming if you do not take off. +- **Emergency Stop** - Emergency stop is used to disarm the vehicle while it is flying. For emergency use only, your vehicle will crash! + +In the cases of warnings or not ready state you can click the indicator to display the dropdown which will show the reason(s) why. The toggle on the right expands each error with additional information and possible solutions. + +![UI To check arming warnings](../../../assets/fly/vehicle_states/arming_preflight_check_ui.png) + +Once each issue is resolved it will disappear from the UI. When all issues blocking arming have been removed you should now be ready to fly. + +## Flight Mode + +The Flight Mode indicator shows you the current flight mode. The dropdown allows you to switch between flight modes. The expanded page allows you to: + +- Configure vehicle land settings +- Set global geo-fence settings +- Add/Remove flight modes from the displayed list + +## Vehicle Messages + +The Vehicle Messages indicator dropdown shows you messages which come from the vehicle. The indicator will turn red if there are important messages available. + +## GPS + +The GPS indicator shows you the satellite count and the HDOP in the toolbar icon. The dropdown shows you additional GPS status. The expanded page give you access to RTK settings. + +## Battery + +The Battery indicator shows you a configurable colored battery icon for remaining charge. It can also be configured to show percent remaining, voltage or both. The expanded page allows you to: + +- Set what value(s) you want displayed in the battery icon +- Configure the icon coloring +- Set up the low battery failsafe + +## Remote ID + +## Other Indicators + +There are other indicators which only show in certain situations: + +- Telemetry RSSI +- RC RSSI +- Gimbal +- VTOL transitions +- Select from multiple connected vehicles diff --git a/docs/ko/qgc-user-guide/fly_view/hud.md b/docs/ko/qgc-user-guide/fly_view/hud.md new file mode 100644 index 00000000000..6ec8c28be74 --- /dev/null +++ b/docs/ko/qgc-user-guide/fly_view/hud.md @@ -0,0 +1,429 @@ +# Fly View + +The Fly View is used to command and monitor the vehicle when flying. + +You can use it to: + +- Run an automated [pre-flight checklist](#preflight_checklist). +- Arm the vehicle (or check why it won't arm). +- Control missions: [start](#start_mission), [continue](#continue_mission), [pause](#pause), and [resume](#resume_mission). +- Guide the vehicle to [arm](#arm)/[disarm](#disarm)/[emergency stop](#emergency_stop), [takeoff](#takeoff)/[land](#land), [change altitude](#change_altitude), [go to](#map_actions) or [orbit](#map_actions) a particular location, and [return/RTL](#rtl). +- Switch between a map view and a video view (if available) +- Display video, mission, telemetry, and other information for the current vehicle, and also switch between connected vehicles. + +![Fly View](../../../assets/fly/fly_view_overview.jpg) + +## UI Overview + +The screenshot above shows the main elements of the fly view: + +- **[Fly Toolbar](fly_view_toolbar.md):** Key status information for vehicle components (GPS, battery, RC control), and vehicle state (Flight mode, Armed/Disarmed status). + - Select the [toolbar indicator](#toolbar_indicator) to view more detail. + - Press the _Flight mode_ text (e.g. "Hold") to select a new mode. + Not every mode may be available. + - The text next to the **Q** icon indicates the flight readiness using text: "Not Ready", "Ready to Fly", "Flying", and status using colour: "green" (all good!), amber (a warning), red (serious problem). You can also select the text to reach a button to arm/disarm/emergency-stop the vehicle. +- **[Fly tools](fly_tools.md):** You can use these to: + - Select the [preflight checklist](#preflight_checklist) (tool option disabled by default). + - Toggle between takeoff/land. + - Pause/restart the current operation (e.g. landing, or the mission). + - Safety return (also known as RTL or Return). + - The _Actions_ button offers other appropriate options for the current state. Actions include changing the altitude or continuing a mission. +- **Map:** Displays the positions of all connected vehicles and the mission for the current vehicle. + - You can drag the map to move it around (the map automatically re-centres on the vehicle after a certain amount of time). + - You can zoom the map in and out using the zoom buttons, mouse wheel, track pad or pinch on a tablet. + - Once flying, you can click on the map to set a [Go to](#goto) or [Orbit at](#orbit) location. +- **[Instrument Panel](instrument_panel.md):** A widget that displays vehicle telemetry. +- **[Attitude/Compass](hud.md):** A widget that provides virtual horizon and heading information. +- **Camera Tools**: A widget for switching between still and video modes, starting/stopping capture, and controlling camera settings. +- **[Video/Switcher](#video_switcher):** Toggle between video or map in a window. + - Press the element to switch _Video_ and _Map_ to foreground. + - _QGroundControl_ supports RTP and RTSP video streaming over your vehicles UDP connection. + It also supports directly connected UVC devices. + QGC video support is further discussed in the [Video README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md). + - A [Telemetry Overlay](../fly_view/video_overlay.md) is automatically generated as a subtitle file +- **Confirmation Slider:** Context sensitive slider to confirm requested actions. Slide to confirm operation. You can also hold the spacebar to confirm. Press **X** to cancel. + +There are a number of other elements that are not displayed by default/are only displayed in certain conditions. +For example, the multi-vehicle selector is only displayed if you have multiple vehicles, and the preflight checklist tool button is only displayed if the appropriate setting is enabled. + +## Fly Toolbar {#toolbar} + +### View Selector + +The "Q" icon on the left of the toolbar allows you to select between additional top level views: + +- **[Plan Flight](../plan_view/plan_view.md):** Used to create missions, geo-fences and rally points +- **Analyze Tools:** A set of tools for things like log download, geo-tagging images, or viewing telemetry. +- **Vehicle Configuration:** The various options for the initial configuration of a new vehicle. +- **Application Settings:** Settings for the QGroundControl application itself. + +### Toolbar Indicators {#toolbar_indicators} + +Next are a toolbar indicators for vehicle status. The dropdowns for each toolbar indicator provide additional detail on status. You can also expand the indicators to show additional application and vehicle settings associated with the indicator. Press the ">" button to expand. + +![Toolbar Indicator - expand button](../../../assets/fly/toolbar_indicator_expand.png) + +Here is an example expanded toolbar indicator for flight modes on a vehicle running PX4 firmware. The settings in this indicator provide access to things which may be relevant to change from flight to flight. + +![Toolbar Indicator - expanded](../../../assets/fly/toolbar_indicator_expanded.png) + +They also provide access to the Vehicle Configuration associated with the indicator. In this example: _Flight Modes_ - _Configure_. + +### Ready/Not Ready Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/vehicle_states/ready_to_fly_ok.png) + +Next in the toolbar is the indicator which shows you whether the vehicle is ready to fly or not. + +It can be in one of the following states: + +- **Ready To Fly** (_green background_) - Vehicle is ready to fly +- **Ready To Fly** (_yellow background_) - Vehicle is ready to fly in the current flight mode. But there are warnings which may cause problems. +- **Not Ready** - Vehicle is not ready to fly and will not takeoff. +- **Armed** - Vehicle is armed and ready to Takeoff. +- **Flying** - Vehicle is in the air and flying. +- **Landing** - Vehicle is in the process of landing. +- **Communication Lost** - QGroundControl has lost communication with the vehicle. + +The Ready Indicator dropdown also gives you acess to: + +- **Arming** - Arming a vehicle starts the motors in preparation for takeoff. You will only be able to arm the vehicle if it is safe and ready to fly. Generally you do not need to manually arm the vehicle. You can simply takeoff or start a mission and the vehicle will arm itself. +- **Disarm** - Disarming a vehicle is only availble when the vehicle is on the ground. It will stop the motors. Generally you do not need to explicitly disarm as vehicles will disarm automatically after landing, or shortly after arming if you do not take off. +- **Emergency Stop** - Emergency stop is effectively the same as disarming the vehicle while it is flying. For emergency use only, your vehicle will crash! + +In the cases of warnings or not ready state you can click the indicator to display the dropdown which will show the reason(s) why. The toggle on the right expands each error with additional information and possible solutions. + +![UI To check arming warnings](../../../assets/fly/vehicle_states/arming_preflight_check_ui.png) + +Once each issue is resolved it will disappear from the UI. +When all issues blocking arming have been removed you should now be ready to fly. + +### Flight Mode Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/toolbar/flight_modes_indicator.png) + +The Flight Mode Indicator dropdown allows you to switch between flight modes. The expanded page allows you to: + +- Configure vehicle land settings +- Set global geo-fence settings +- Add/Remove flight modes from the displayed list + +### Vehicle Messages Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/toolbar/messages_indicator.png) + +The Vehicle Messages Indicator dropdown shows you messages which come from the vehicle. The indicator will turn red if there are important messages available. + +### GPS Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/toolbar/gps_indicator.png) + +The GPS Indicator shows you the satellite count and the HDOP in the toolbar icon. The dropdown shows you additional GPS status. The expanded page give you access to RTK settings. + +### Battery Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/toolbar/battery_indicator.png) + +The Battery Indicator shows you a configurable colored battery icon for remaining charge. It can also be configured to show percent remaining, voltage or both. The expanded page allows you to: + +- Set what value(s) you want displayed in the battery icon +- Configure the icon coloring +- Set up the low battery failsafe + +## Fly Tools {#fly_tools} + +### Pre Flight Checklist {#preflight_checklist} + +An automated preflight checklist can be used to run through standard checks that the vehicle is configured correctly and it is safe to fly. + +To view the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../settings_view/general.md) and selecting the **Use preflight checklist** checkbox. +The tool will then be added to the _Flight Tools_. +Press it to open the checklist: + +![Pre Flight Checklist](../../../assets/fly/pre_flight_checklist.jpg) + +Once you have performed each test, select it on the UI to mark it as complete. + +### Takeoff {#takeoff} + +:::tip +If you are starting a mission for a multicopter, _QGroundControl_ will automatically perform the takeoff step. +::: + +To takeoff (when landed): + +1. Press the **Takeoff** button in the _Fly Tools_ (this will toggle to a **Land** button after taking off). +2. Optionally set the takeoff altitude in the right-side vertical slider. + +- You can slide up/down to change the altitude +- You can also click on the specified altitude (10 ft in example) and then type in a specific altitude. + +1. Confirm takeoff using the slider. + +![takeoff](../../../assets/fly/takeoff.png) + +### Land {#land} + +You can land at the current position at any time while flying: + +1. Press the **Land** button in the _Fly Tools_ (this will toggle to a **Takeoff** button when landed). +2. Confirm landing using the slider. + +### RTL/Return + +Return to a "safe point" at any time while flying: + +1. Press the **RTL** button in the _Fly Tools_. +2. Confirm RTL using the slider. + +:::info +Vehicles commonly return to the "home" (takeoff) location and land. +This behaviour depends on the vehicle type and configuration. +For example, rally points or mission landings may be used as alternative return targets. +::: + +### Change Altitude {#change_altitude} + +You can change altitude while flying, except when in a mission: + +1. Press the **Actions** button on the _Fly Tools_ +2. Select the _Change Altitude_ button +3. Select the new altitude from the vertical slider +4. Confirm the action + +## Instrument Panel (Telemetry) {#instrument_panel} + +The instrument panel displays telemetry information about the current vehicle. + +![Instrument Panel - for values/telemetry](../../../assets/fly/instrument_panel/instrument_panel_default_values.png) + +The default values include altitude (relative to the home location), horizontal and vertical speed, total flight time, and distance between vehicle and ground station. + +You can configure where the information is displayed by: + +- Tablets: Press and hold over control +- Desktop: Right click control +- Click to Lock icon to close and save changes + +![Instrument Panel - edit tools](../../../assets/fly/instrument_panel/instrument_panel_tools_edit.png) + +You configure what information is display by selecting the edit/pencil icon. +The grid will then display "+" and "-" icons that you can use to add or remove rows and columns (and the pencil icon is replaced by a "lock" icon that you can use to save the settings). + +Select a value to launch its "Value Display" editor. +This allows you to change the icon, text, size, units and so on of the current telemetry value. + +![Instrument Panel - edit a value](../../../assets/fly/instrument_panel/instrument_panel_tools_edit_value.png) + +The selection list on the top left is used to change the source of the telemetry. +By default this is the vehicle, but you can use the selector to choose a particular sensor type. + +![Instrument Panel - value type](../../../assets/fly/instrument_panel/instrument_panel_edit_value_type.png) + +The selection list on the top right is used to select a particular telemetry value for the vehicle or sensor. + +![Instrument Panel - value options](../../../assets/fly/instrument_panel/instrument_panel_edit_value_options.png) + +## Attitude /Compass {#hud} + +You can select from multiple types of instruments by: + +- Tablets: Press and hold over control +- Desktop: Right click over control +- Click the Lock icon to close and save changes + +![Instrument Panel - hover for move/edit tools](../../../assets/fly/hud_select_variant.png) + +### Camera {#camera_instrument_page} + +The camera panel is used to capture still images and video, and to configure the camera. + +![Camera Panel](../../../assets/fly/camera_panel/camera_mavlink.png) + +The camera capture and configuration options depend on the connected camera. +The configuration options are selected using the panel gear icon. +The configuration for a simple autopilot-connected camera are shown below. + +![Camera Panel - minimal settings](../../../assets/fly/camera_panel/camera_settings_minimal.png) + +When connected to camera that supports the [MAVLink Camera Protocol](https://mavlink.io/en/services/camera.html) you can additionally configure and use other camera services that it makes available. +For example, if your camera supports video mode you will be able to switch between still image capture and video mode, and start/stop recording. + +![Camera Panel - MAVLink settings](../../../assets/fly/camera_panel/camera_settings_mavlink.png) + +:::info +Most of the settings that are displayed depend on the camera (they are defined in its [MAVLink Camera Definition File](https://mavlink.io/en/services/camera_def.html)). + +> A few common settings at the end are hard-coded: Photo Mode (Single/Time Lapse), Photo Interval (if Time Lapse), Reset Camera Defaults (sends a reset command to the camera), Format (storage) +> ::: + +### Video Stream {#video_instrument_page} + +The video page is used to enable/disable video streaming. +When enabled, you can start/stop the video stream, enable a grid overlay, change how the image fits the screen, and record the video locally with QGC. + +![Instrument Page - Video Stream](../../../assets/fly/instrument_page_video_stream.jpg) + +## Actions/Tasks + +The following sections describe how to perform common operations/tasks in the Fly View. + +::: info +Many of the available options depend on both the vehicle type and its current state. +::: + +### Actions associated with a map position (#map_actions) + +There are a number of actions which can be taken which are associated with a specific position on the map. To use these actions: + +1. Click on the map at a specific position +2. A popup will display showing you the list of available actions +3. Select the action you want +4. Confirm the action + +Examples of map position actions are Go To Location, Orbit and so forth. + +### Pause + +You can pause most operations, including taking off, landing, RTL, mission execution, orbit at location. The vehicle behaviour when paused depends on the vehicle type; typically a multicopter will hover, and a fixed wing vehicle will circle. + +:::info +You cannot pause a _Goto location_ operation. +::: + +To pause: + +1. Press the **Pause** button in the _Fly Tools_. +2. Optionally set a new altitude using the right-side vertical slider. +3. Confirm the pause using the slider. + +### Missions + +#### Start Mission {#start_mission} + +You can start a mission when the vehicle is landed (the start mission confirmation slider is often displayed by default). + +To start a mission from landed: + +1. Press the **Action** button on the _Fly Tools_ + +2. Select the _Start Mission_ action from the dialog. + + ![Start mission action](../../../assets/fly/start_mission_action.jpg) + + (to display the confirmation slider) + +3. When the confirmation slider appears, drag it to start the mission. + + ![Start mission](../../../assets/fly/start_mission.jpg) + +#### Continue Mission {#continue_mission} + +You can _continue_ mission from the _next_ waypoint when you're flying (the _Continue Mission_ confirmation slider is often displayed by default after you takeoff). + +:::info +Continue and [Resume mission](#resume_mission) are different! +Continue is used to restart a mission that has been paused, or where you have taken off, so you've already missed a takeoff mission command. +Resume mission is used when you've used a RTL or landed midway through a mission (e.g. for a battery change) and then wish to continue the next mission item (i.e. it takes you to where you were up to in the mission, rather than continuing from your place in the mission). +::: + +You can continue the current mission while (unless already in a mission!): + +1. Press the **Action** button on the _Fly Tools_ + +2. Select the _Continue Mission_ action from the dialog. + + ![Continue Mission/Change Altitude action](../../../assets/fly/continue_mission_change_altitude_action.jpg) + +3. Drag the confirmation slider to continue the mission. + + ![Continue Mission](../../../assets/fly/continue_mission.jpg) + +#### Resume Mission {#resume_mission} + +_Resume Mission_ is used to resume a mission after performing an [RTL/Return](#rtl) or [Land](#land) from within a mission (in order, for example, to perform a battery change). + +:::info +If you are performing a battery change, **do not** disconnect QGC from the vehicle after disconnecting the battery. +After you insert the new battery _QGroundControl_ will detect the vehicle again and automatically restore the connection. +::: + +After landing you will be prompted with a _Flight Plan complete_ dialog, which gives you the option to remove the plan from the vehicle, leave it on the vehicle, or to resume the mission from the last waypoint that was traveled through. + +![Resume Mission](../../../assets/fly/resume_mission.jpg) + +If you select to resume the mission, then _QGroundControl_ will rebuild the mission and upload it to the vehicle. +Then use the _Start Mission_ slider to continue the mission. + +The image below shows the mission that was rebuilt after the Return shown above. + +![Resume Rebuilt Mission](../../../assets/fly/resume_mission_rebuilt.jpg) + +:::info +A mission cannot simply resume from the last mission item that the vehicle executed, because there may be multiple items at the last waypoint that affect the next stage of the mission (e.g. speed commands or camera control commands). +Instead _QGroundControl_ rebuilds the mission, starting from the last mission item flown, and automatically prepending any relevant commands to the front of the mission. +::: + +#### Remove Mission Prompt After Landing {#resume_mission_prompt} + +You will be prompted to remove the mission from the vehicle after the mission completes and the vehicle lands and disarms. +This is meant to prevent issues where stale missions are unknowingly left on a vehicle, potentially resulting in unexpected behavior. + +### Display Video {#video_switcher} + +When video streaming is enabled, _QGroundControl_ will display the video stream for the currently selected vehicle in the "video switcher window" at the bottom left of the map. +You can press the switcher anywhere to toggle _Video_ and _Map_ to foreground (in the image below, the video is shown in the foreground). + +![Video Stream Record](../../../assets/fly/video_record.jpg) + +:::info +Video streaming is configured/enabled in [Application Settings > General tab > Video](../settings_view/general.md#video). +::: + +You can further configure video display using controls on the switcher: + +![Video Pop](../../../assets/fly/video_pop.jpg) + +- Resize the switcher by dragging the icon in the top right corner. +- Hide the switcher by pressing the toggle icon in the lower left. +- Detach the video switcher window by pressing on the icon in its top left corner + (once detached, you can move and resize the window just like any other in your OS). + If you close the detached window the switcher will re-lock to the QGC Fly view. + +### Record Video + +If supported by the camera and vehicle, _QGroundControl_ can start and stop video recording on the camera itself. _QGroundControl_ can also record the video stream and save it locally. + +:::tip +Video stored on the camera may be of much higher quality, but it is likely that your ground station will have a much larger recording capacity. +::: + +#### Record Video Stream (on GCS) + +Video stream recording is controlled on the [video stream instrument page](#video_instrument_page). +Press the red circle to start recording a new video (a new video file is created each time the circle is pressed); the circle will change into a red square while recording is in progress. + +![Video Stream Record](../../../assets/fly/video_record.jpg) + +Video stream recording is configured in the [Application Settings > General tab](../settings_view/general.md): + +- [Video Recording](../settings_view/general.md#video-recording) - specifies the recording file format and storage limits. + + ::: info + Videos are saved in Matroska format (.mkv) by default. + This format is relatively robust against corruption in case of errors. + ::: + +- [Miscellaneous](../settings_view/general.md#miscellaneous) - Streamed video is saved under the **Application Load/Save Path**. + +:::tip +The stored video includes just the video stream itself. +To record video with QGroundControl application elements displayed, you should use separate screen recording software. +::: + +#### Record Video on Camera + +Start/stop video recording _on the camera itself_ using the [camera instrument page](#camera_instrument_page). +First toggle to video mode, then select the red button to start recording. + +![Instrument Page - Camera MAVLink Settings](../../../assets/fly/instrument_page_camera_mavlink.jpg) diff --git a/docs/ko/qgc-user-guide/fly_view/instrument_panel.md b/docs/ko/qgc-user-guide/fly_view/instrument_panel.md new file mode 100644 index 00000000000..5f4deed8d8c --- /dev/null +++ b/docs/ko/qgc-user-guide/fly_view/instrument_panel.md @@ -0,0 +1,32 @@ +# Instrument Panel + +The instrument panel displays telemetry information about the current vehicle. + +![Instrument Panel - for values/telemetry](../../../assets/fly/instrument_panel/instrument_panel_default_values.png) + +The default values include altitude (relative to the home location), horizontal and vertical speed, total flight time, and distance between vehicle and ground station. + +You can configure where the information is displayed by: + +- Tablets: Press and hold over control +- Desktop: Right click control +- Click to Lock icon to close and save changes + +![Instrument Panel - edit tools](../../../assets/fly/instrument_panel/instrument_panel_tools_edit.png) + +You configure what information is display by selecting the edit/pencil icon. +The grid will then display "+" and "-" icons that you can use to add or remove rows and columns (and the pencil icon is replaced by a "lock" icon that you can use to save the settings). + +Select a value to launch its "Value Display" editor. +This allows you to change the icon, text, size, units and so on of the current telemetry value. + +![Instrument Panel - edit a value](../../../assets/fly/instrument_panel/instrument_panel_tools_edit_value.png) + +The selection list on the top left is used to change the source of the telemetry. +By default this is the vehicle, but you can use the selector to choose a particular sensor type. + +![Instrument Panel - value type](../../../assets/fly/instrument_panel/instrument_panel_edit_value_type.png) + +The selection list on the top right is used to select a particular telemetry value for the vehicle or sensor. + +![Instrument Panel - value options](../../../assets/fly/instrument_panel/instrument_panel_edit_value_options.png) diff --git a/docs/ko/qgc-user-guide/fly_view/video.md b/docs/ko/qgc-user-guide/fly_view/video.md new file mode 100644 index 00000000000..432252d5c7e --- /dev/null +++ b/docs/ko/qgc-user-guide/fly_view/video.md @@ -0,0 +1,58 @@ +# Video + +When video streaming is enabled (Application Settings - Video), _QGroundControl_ will display the video stream for the currently selected vehicle in the "video switcher window" at the bottom left of the map. +You can press the switcher anywhere to toggle _Video_ and _Map_ to foreground (in the image below, the video is shown in the foreground). + +![Video Stream Record](../../../assets/fly/video_record.jpg) + +:::info +Video streaming is configured/enabled in [Application Settings > General tab > Video](../settings_view/general.md#video). +::: + +You can further configure video display using controls on the switcher: + +![Video Pop](../../../assets/fly/video_pop.jpg) + +- Resize the switcher by dragging the icon in the top right corner. +- Hide the switcher by pressing the toggle icon in the lower left. +- Detach the video switcher window by pressing on the icon in its top left corner + (once detached, you can move and resize the window just like any other in your OS). + If you close the detached window the switcher will re-lock to the QGC Fly view. + +### Record Video + +If supported by the camera and vehicle, _QGroundControl_ can start and stop video recording on the camera itself. _QGroundControl_ can also record the video stream and save it locally. + +:::tip +Video stored on the camera may be of much higher quality, but it is likely that your ground station will have a much larger recording capacity. +::: + +#### Record Video Stream (on GCS) + +Video stream recording is controlled on the [video stream instrument page](#video_instrument_page). +Press the red circle to start recording a new video (a new video file is created each time the circle is pressed); the circle will change into a red square while recording is in progress. + +![Video Stream Record](../../../assets/fly/video_record.jpg) + +Video stream recording is configured in the [Application Settings > General tab](../settings_view/general.md): + +- [Video Recording](../settings_view/general.md#video-recording) - specifies the recording file format and storage limits. + + ::: info + Videos are saved in Matroska format (.mkv) by default. + This format is relatively robust against corruption in case of errors. + ::: + +- [Miscellaneous](../settings_view/general.md#miscellaneous) - Streamed video is saved under the **Application Load/Save Path**. + +:::tip +The stored video includes just the video stream itself. +To record video with QGroundControl application elements displayed, you should use separate screen recording software. +::: + +#### Record Video on Camera + +Start/stop video recording _on the camera itself_ using the [camera instrument page](#camera_instrument_page). +First toggle to video mode, then select the red button to start recording. + +![Instrument Page - Camera MAVLink Settings](../../../assets/fly/instrument_page_camera_mavlink.jpg) diff --git a/docs/ko/qgc-user-guide/getting_started/download_and_install.md b/docs/ko/qgc-user-guide/getting_started/download_and_install.md index d0127596187..c553ccf1706 100644 --- a/docs/ko/qgc-user-guide/getting_started/download_and_install.md +++ b/docs/ko/qgc-user-guide/getting_started/download_and_install.md @@ -65,8 +65,8 @@ _QGroundControl_을 처음 설치하기 전에: sudo usermod -a -G dialout $USER sudo apt-get remove modemmanager -y sudo apt install gstreamer1.0-plugins-bad gstreamer1.0-libav gstreamer1.0-gl -y - sudo apt install libqt5gui5 -y sudo apt install libfuse2 -y + sudo apt install libxcb-xinerama0 libxkbcommon-x11-0 libxcb-cursor-dev -y ``` 2. 사용자 권한을 변경하려면 로그아웃 후 다시 로그인하여야 합니다. @@ -82,7 +82,8 @@ _QGroundControl_을 처음 설치하기 전에: ./QGroundControl.AppImage (or double click) ``` -듀얼 어댑터가 있는 Ubuntu 18.04 시스템에는 [동영상 스트리밍 문제](../troubleshooting/qgc_setup.md#dual_vga)가 있습니다. +:::info +There are known [video steaming issues](../troubleshooting/qgc_setup.md#dual_vga) on Ubuntu 18.04 systems with dual adaptors. ::: :::info @@ -92,8 +93,6 @@ Ubuntu 16.04에서 이 버전을 실행하려면, [소스에서 비디오 라이 ## 안드로이드 {#android} -Google Play 스토어에서 _QGroundControl_을 일시적으로 사용할 수 없습니다. 아래의 링크들에서 수동으로 설치할 수 있습니다. - - [Android 32 비트 APK](https://qgroundcontrol.s3-us-west-2.amazonaws.com/latest/QGroundControl32.apk) - [Android 64 비트 APK](https://qgroundcontrol.s3-us-west-2.amazonaws.com/latest/QGroundControl64.apk) diff --git a/docs/ko/qgc-user-guide/getting_started/quick_start.md b/docs/ko/qgc-user-guide/getting_started/quick_start.md index 40f6a752a7a..12a6c4dbdad 100644 --- a/docs/ko/qgc-user-guide/getting_started/quick_start.md +++ b/docs/ko/qgc-user-guide/getting_started/quick_start.md @@ -1,16 +1,16 @@ -# QGroundControl Quick Start +# QGroundControl 시작하기 -Getting _QGroundControl_ up and running is quick and easy: +_QGroundControl_를 설치하고 실행하는 방법은 간단합니다. -1. [Download and install](../getting_started/download_and_install.md) the application. -1. Start _QGroundControl_. -1. Attach your vehicle to the ground station device via USB, through a telemetry radio, or over WiFi. _QGroundControl_ should detect your vehicle and connect to it automatically. +1. [Download and install (Daily 5.0)](../releases/daily_builds.md) the application. +2. QGroundControl을 실행합니다. +3. 지상국에서 USB나 텔레메트리 또는 WiFi로 기체를 연결합니다. QGroundControl에서 기체를 자동으로 감지하여 연결합니다. -That's it! If the vehicle is ready to fly, _QGroundControl_ should display [Fly View](../fly_view/fly_view.md) as shown below (otherwise it will open [Setup View](../setup_view/setup_view.md)). +That's it! 비행 준비가 완료되면, _QGroundControl_에는 아래와 같은 [비행화면](../fly_view/fly_view.md)을 표시됩니다. ![](../../../assets/quickstart/fly_view_connected_vehicle.jpg) -A good way to become familiar with _QGroundControl_ is to start experimenting: +QGroundControl에 자주 사용하는 것이 익숙해 질 수 있는 최선의 방법입니다. - Use the View Selector to switch between main views: - Plan Flight @@ -21,6 +21,6 @@ A good way to become familiar with _QGroundControl_ is to start experimenting: While the UI is fairly intuitive, this documentation can also be referenced to find out more. -::: info +:::info Make sure QGC has an internet connection when you connect a new vehicle in order to display map content. ::: diff --git a/docs/ko/qgc-user-guide/index.md b/docs/ko/qgc-user-guide/index.md index cccc6433d66..004821f12e9 100644 --- a/docs/ko/qgc-user-guide/index.md +++ b/docs/ko/qgc-user-guide/index.md @@ -1,6 +1,9 @@ -# QGroundControl 사용자 안내서 +# QGroundControl Guide (Daily Build 5.0) -[![배포](https://img.shields.io/github/release/mavlink/QGroundControl.svg)](https://github.com/mavlink/QGroundControl/releases) [![토론](https://img.shields.io/badge/discuss-px4-ff69b4.svg)](http://discuss.px4.io/c/qgroundcontrol/qgroundcontrol-usage) [![토론](https://img.shields.io/badge/discuss-ardupilot-ff69b4.svg)](http://discuss.ardupilot.org/c/ground-control-software/qgroundcontrol) [![Gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/mavlink/qgroundcontrol?utm_source=badge\&utm_medium=badge\&utm_campaign=pr-badge\&utm_content=badge) [![슬랙](../../assets/site/slack.svg)](https://join.slack.com/t/px4/shared_invite/zt-si4xo5qs-R4baYFmMjlrT4rQK5yUnaA) +[![Discuss](https://img.shields.io/badge/discuss-px4-ff69b4.svg)](http://discuss.px4.io/c/qgroundcontrol/qgroundcontrol-usage) +[![Discuss](https://img.shields.io/badge/discuss-ardupilot-ff69b4.svg)](http://discuss.ardupilot.org/c/ground-control-software/qgroundcontrol) + +_You are viewing the docs for the upcoming 5.0 release of QGroundControl. If you want docs for a Stable build select from the Version dropdown above._ _QGroundControl_을 이용하여 PX4나 ArduPilot 구동 차량을 설정하고 운행할 수 있습니다. 초보자를 위한 쉽고 간편한 기능 뿐만 아니라 숙련자를 위한 고급 기능들도 제공합니다. @@ -11,6 +14,7 @@ _QGroundControl_을 이용하여 PX4나 ArduPilot 구동 차량을 설정하고 - PX4와 ArduPilot(또는 기타 MAVLink 통신 자동조종장치)을 실행하는 기체 비행 방법 - 자율 비행을 위한 미션 계획 - 기체 위치, 비행 트랙, 웨이포인트 및 기체 계기를 표출하는 지도 디스플레이 +- 3D viewer visualizing the 3D map of the environment (.osm file), the 3D model of the vehicle (only multi-rotors for the moment), and the mission 3D trajectory (including the waypoints). - 기기 디스플레이 오버레이를 이용한 비디오 스트리밍 - Support for managing multiple vehicles. - QGroundControl은 Windows, OS X, Linux 플랫폼, iOS 및 Android 장치에서 실행됩니다. diff --git a/docs/ko/qgc-user-guide/plan_view/pattern.md b/docs/ko/qgc-user-guide/plan_view/pattern.md index d367b8f11e5..c5beaa00966 100644 --- a/docs/ko/qgc-user-guide/plan_view/pattern.md +++ b/docs/ko/qgc-user-guide/plan_view/pattern.md @@ -5,9 +5,9 @@ The available pattern tools depend on the vehicle (and support for the vehicle-t ![패턴 도구(계획 도구)](../../../assets/plan/pattern/pattern_tool.jpg) -| 패턴 | 설명 | 차량 | -| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | ---------- | +| 패턴 | 설명 | 차량 | +| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ---------- | | [탐사](../plan_view/pattern_survey.md) | 다각형 영역에 그리드 비행 패턴을 작성합니다. 지오태깅 이미지 생성에 적합한 그리드 및 카메라 설정에 대한 사양과 다각형을 지정할 수 있습니다. | 전체 | | [구조물 스캔](../plan_view/pattern_structure_scan_v2.md) | 수직 표면(다각형 또는 원형) 위의 이미지를 캡처하는 그리드 비행 패턴을 작성합니다. 일반적으로 육안 검사 또는 구조물의 3D 모델을 생성합니다. | 멀티콥터, VTOL | | [복도 스캔](../plan_view/pattern_corridor_scan.md) | 폴리라인을 따르는 비행 패턴을 생성합니다(예: 도로 측량). | 전체 | -| [고정익 착륙](../plan_view/pattern_fixed_wing_landing.md) | 임무에 고정익의 착륙 패턴을 추가합니다. | Fixed Wing | +| [고정익 착륙](../plan_view/pattern_fixed_wing_landing.md) | 임무에 고정익의 착륙 패턴을 추가합니다. | Fixed Wing | diff --git a/docs/ko/qgc-user-guide/plan_view/plan_view.md b/docs/ko/qgc-user-guide/plan_view/plan_view.md index 4dc42810ca2..4d2be1cbd07 100644 --- a/docs/ko/qgc-user-guide/plan_view/plan_view.md +++ b/docs/ko/qgc-user-guide/plan_view/plan_view.md @@ -199,5 +199,5 @@ _차량에 연결_한 상태에서 임무를 계획하고 있다면 차량에 ## 추가 정보 -- [QGC 릴리스 v3.2](../releases/stable_v3.2_long.md#plan_view)의 새로운 플랜 보기 기능 -- [QGC 릴리스 v3.3](../releases/stable_v3.3_long.md#plan_view)의 새로운 플랜 보기 기능 +- New Plan View features for [QGC release v3.2](../qgc-user-guide/releases/release_note_stable_v3.md#plan_view) +- New Plan View features for [QGC release v3.3](../qgc-user-guide/releases/release_note_stable_v3.md#plan-view-1) diff --git a/docs/ko/qgc-user-guide/releases/daily_builds.md b/docs/ko/qgc-user-guide/releases/daily_builds.md index ebdc68187f4..70a7f1013d6 100644 --- a/docs/ko/qgc-user-guide/releases/daily_builds.md +++ b/docs/ko/qgc-user-guide/releases/daily_builds.md @@ -10,23 +10,12 @@ Use at your own risk! 아래 링크에서 다운로드할 수 있습니다([다운로드 및 설치](../getting_started/download_and_install.md)에 설명된 대로 설치). - [윈도우](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl-installer.exe) - - [OS X](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl.dmg) - - ::: info - QGroundControl 미서명 문제로 인하여 Catalina에서 문제가 발생합니다. To open QGC app for the first time: - - - QGroundControl 앱 아이콘을 마우스 오른쪽 버튼으로 클릭하고, 메뉴에서 열기를 선택합니다. 취소 옵션만 제공됩니다. 취소를 선택합니다. - - QGroundControl 앱 아이콘을 마우스 오른쪽 버튼으로 클릭하고 메뉴에서 열기를 선택합니다. 이번에는 열기 옵션이 표시됩니다. - - ::: - -- [리눅스](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl.AppImage) - -- [안드로이드](https://play.google.com/store/apps/details?id=org.mavlink.qgroundcontrolbeta) - Google Play: \*QGroundControl(일일 테스트 빌드)\*로 나열됩니다. - +- [Linux](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl-x86_64.AppImage) - Before running do the following: + - `chmod +x QGroundControl.AppImage` + - On the command prompt enter (one time only): + \- `sudo usermod -a -G dialout $USER` + \- `sudo apt-get remove modemmanager -y` + \- Logout and login again to enable the change to user permissions. +- [Android](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl.apk) - iOS에서는 현재 사용 불가합니다. - -:::info -QGroundControl Continous Delivery 파이프라인에서 Google Play 스토어에 업로드하는 데 문제가 발생할 수 있습니다. [QGroundControl32.apk](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl32.apk) 및 [QGroundControl64.apk](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl64.apk)에서 직접 다운로드할 수 있는 안드로이드 기기용 일일 빌드 APK를 찾을 수 있습니다. -::: diff --git a/docs/ko/qgc-user-guide/releases/privacy_policy.md b/docs/ko/qgc-user-guide/releases/privacy_policy.md index f550f05d41d..45f2339396e 100644 --- a/docs/ko/qgc-user-guide/releases/privacy_policy.md +++ b/docs/ko/qgc-user-guide/releases/privacy_policy.md @@ -1,8 +1,69 @@ # 개인정보 취급 방침 +Dronecode Project, Inc. built the QGroundControl (org.mavlink.qgroundcontrol) app as an Open Source app. This SERVICE is provided by Dronecode Project, Inc. at no cost and is intended for use as is. + +This page is used to inform visitors regarding our policies with the collection, use, and disclosure of Personal Information if anyone decided to use our Service. + +If you choose to use our Service, then you agree to the collection and use of information in relation to this policy. The Personal Information that we collect is used for providing and improving the Service. We will not use or share your information with anyone except as described in this Privacy Policy. + +The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, which are accessible at QGroundControl (org.mavlink.qgroundcontrol) unless otherwise defined in this Privacy Policy. + +**Information Collection and Use** + +For a better experience, while using our Service, we may require you to provide us with certain personally identifiable information, including but not limited to device data. The information that we request will be retained by us and used as described in this privacy policy. + _QGroundControl_은 개인 및/또는 민감한 사용자 데이터에 대한 액세스를 요구할 수 있습니다. 이 데이터는 _QGroundControl_ 외부에서 사용되지 않습니다. 아래 목록은 일부 데이터가 사용되는 방식을 설명합니다. -- 카메라 센서: 비행 원격 측정 데이터로 비디오를 오버레이 용으로 사용합니다. -- 위치: 지도에서 현재 사용자의 위치를 추적합니다. +- Camera sensor: This is used to overlay the video with flight telemetry data. +- Location: This is used for tracking the current user position on the map. + +The app does use third-party services that may collect information used to identify you. + +Link to the privacy policy of third-party service providers used by the app + +- [Google Play Services](https://www.google.com/policies/privacy/) + +**Log Data** + +We want to inform you that whenever you use our Service, in a case of an error in the app we collect data and information (through third-party products) on your phone called Log Data. This Log Data may include information such as your device Internet Protocol (“IP”) address, device name, operating system version, the configuration of the app when utilizing our Service, the time and date of your use of the Service, and other statistics. + +**Cookies** + +Cookies are files with a small amount of data that are commonly used as anonymous unique identifiers. These are sent to your browser from the websites that you visit and are stored on your device's internal memory. + +This Service does not use these “cookies” explicitly. However, the app may use third-party code and libraries that use “cookies” to collect information and improve their services. You have the option to either accept or refuse these cookies and know when a cookie is being sent to your device. If you choose to refuse our cookies, you may not be able to use some portions of this Service. + +**Service Providers** + +We may employ third-party companies and individuals due to the following reasons: + +- To facilitate our Service; +- To provide the Service on our behalf; +- To perform Service-related services; or +- To assist us in analyzing how our Service is used. + +We want to inform users of this Service that these third parties have access to their Personal Information. The reason is to perform the tasks assigned to them on our behalf. However, they are obligated not to disclose or use the information for any other purpose. + +**Security** + +We value your trust in providing us your Personal Information, thus we are striving to use commercially acceptable means of protecting it. But remember that no method of transmission over the internet, or method of electronic storage is 100% secure and reliable, and we cannot guarantee its absolute security. + +**Links to Other Sites** + +This Service may contain links to other sites. If you click on a third-party link, you will be directed to that site. Note that these external sites are not operated by us. Therefore, we strongly advise you to review the Privacy Policy of these websites. We have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services. + +**Children’s Privacy** + +These Services do not address anyone under the age of 13. We do not knowingly collect personally identifiable information from children under 13 years of age. In the case we discover that a child under 13 has provided us with personal information, we immediately delete this from our servers. If you are a parent or guardian and you are aware that your child has provided us with personal information, please contact us so that we will be able to do the necessary actions. + +**Changes to This Privacy Policy** + +We may update our Privacy Policy from time to time. Thus, you are advised to review this page periodically for any changes. We will notify you of any changes by posting the new Privacy Policy on this page. + +This policy is effective as of 2024-03-12 + +**Contact Us** + +If you have any questions or suggestions about our Privacy Policy, do not hesitate to contact us at info@dronecode.org. diff --git a/docs/ko/qgc-user-guide/releases/release_note_stable_v3.md b/docs/ko/qgc-user-guide/releases/release_note_stable_v3.md new file mode 100644 index 00000000000..f20e051fc1a --- /dev/null +++ b/docs/ko/qgc-user-guide/releases/release_note_stable_v3.md @@ -0,0 +1,564 @@ +# QGC v3 Release Notes + +This topic contains the cumulative release notes for _QGroundControl v3.x_. + +## Stable Version 3.5 + +This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.5. + +- **Overall** + - Added Airmap integration to QGC. OSX build only. + - Bumped settings version (now 8). + This will cause all settings to be reset to defaults. + - Added Chinese and Turkish localization and partial German localization. + - Added support for the Taisync 2.4GHz ViUlinx digital HD wireless link. + - Fix loading of parameters from multiple components. + This especially affected WiFi connections. + - **ArduPilot** Support for ChibiOS firmware connect and flash. +- **Settings** + - **RTK** Add support for specifying fixed RTK based station location in Settings/General. + - **GCS Location** + - Added UDP Port option for NMEA GPS Device. + - GCS heading shown if available +- **Plan** + - **Polygons** Support loading polygons from SHP files. + - **Fixed Wing Landing Pattern** Add stop photo/video support. + Defaults to on such that doing an RTL will stop camera. + - **Edit Position dialog** Available on polygon vertices. +- **Fly** + - **Camera Page** Updated support for new MAVLInk camera messages. + Camera select, camera mode, start/stop photo/video, storage mangement... + - **Orbit** Support for changing rotation direction. + - **Instrument Panel** + - Added ESTIMATOR_STATUS values to new estimatorStatus Vehicle FactGroup. + These are now available to display in instrument panel. + - Make Distance to GCS available for display from instrument panel. + - Make Heading to Home available for display from instrument panel. + +## Stable Version 3.4 + +This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.4. Not to mention the large number of bug fixes in each stable release. + +- **Settings** + - **Offline Maps** + - Center Tool allows you to specify a map location in lat/lon or UTM coordinates. Making it easier to get to the location you want to create an offline map for. + - Ability to pre-download terrain heights for offline use. + - **Help** Provides links to QGC user guide and forums. + +- **Setup** + - **Firmware** Ability to flash either PX4 or ArduPilot Flow firmware. + - PX4 Pro Firmware + - **Flight Modes** Specify channels for all available transmitter switches. + - **Tuning: Advanced** Initial implementation of vehicle PID tuning support. Note that this is a work in progress that will improve in 3.5 daily builds. + - ArduPilot Firmware + - **Power/Safety** Support for new multi-battery setup. + - **Trad Heli** New setup page. + +- **Plan** + + - **File Load/Save** New model for Plan file loading which matches a standard File Load/Save/Save As user model. + + - **Load KML** Ability to load a KML file directly from the Sync menu. You will be prompted for what type of Pattern you want to create from the KML if needed. + + - **Survey** Better support for irregular shaped polygons. + + - **[Corridor Scan](../plan_view/pattern_corridor_scan.md)** - Create a flight pattern which follows a poly-line. For example can be used to survey a road. + + - **[Fixed Wing Landing Pattern](../plan_view/pattern_fixed_wing_landing.md)** + - Landing area visually represented in Plan. + - Landing position/heading can be copied from Vehicle position/heading. + + - **Terrain** + + - Height of mission items can be specified as height above terrain. + - Survey and Corridor Scan can generate flight plans which follow terrain. + + ::: info + This feature does not support [ArduPilot terrain following](http://ardupilot.org/copter/docs/common-terrain-following.html). + ::: + + - **Edit Position** Set item position from vehicle position. + +- **Fly** + - **Pre-Flight Checklist** You can turn this on from Settings. It provides a generic checklist to follow prior to flight. Expect more feature to appear for this in 3.5 daily builds. + - **Instrument Panel** + - Many new values available for display. + - New Camera page which provides full camera control. Requires a camera which support new MavLink camera specification. + - **ArduPlane** Much better support for guided commands including QuadPlane support. + - **High Latency Links** Support for high latency links such as satellite connections. + Limits the traffic from QGC up to Vehicle on these links to reduce cost. + Supports HIGH_LATENCY MavLink message. + Supports failover back/forth from high latency to normal link with dual link setup. + +## Stable Version 3.3 (Summary) + +:::tip +More detailed release notes for version 3.3 can be found in the next section. +::: + +This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.3. Not to mention the large number of bug fixes of this release. + +- **Settings** + - Local NMEA GPS device support. + - Video Recording save settings. +- **Setup** + - **Parameter Editor** - Searching updates as you type characters for near immediate response to searches. + - **Joystick** - Android joystick support. +- **Plan** + - **NEW - Structure Scan Pattern** - Create a multi-layered flight pattern that captures images over vertical surfaces (polygonal or circular). Used for 3d model generation or vertical surface inspection. + - **Fixed Wing Landing Pattern** - You can now adjust the distance from the loiter to land point by either distance or glide slope fall rate. + - PX4 GeoFence and Rally Point support. + - Terrain height display in lower Mission Item altitude display +- **Fly** + - Start/Stop video recording. + - Better display of vehicle icons when connected to multiple vehicles. + - Multi-Vehicle View supports commands which apply to all vehicles. + - Displays vehicles reported from ADS-B sensor. +- **Analyze** + - **Mavlink console** - New support for communicating with Mavlink console. + - **Log Download** - Moved from Menu to Analyze view. + +## Stable Version 3.3 (Detailed) + +### Settings View + +#### NMEA GPS Device support + +![NMEA GPS Device support](../../../assets/settings/general/NMEADevice.jpg) + +You can specify a connection to one of these devices on the General page. +The GPS information will then be used for ground station location and in turn follow me support. + +For more information see [Settings > General (AutoConnect to the following devices)](../settings_view/general.md#auto_connect). + +#### Video Recording + +![Video Recording](../../../assets/settings/video_recording.jpg) + +Videos will be saved to the Video directory of your QGC file save path. +You can also specify the maximum amount of space you want video files to consume. +After that size if exceeded the oldest video files will be removed. +Video Recording is turned on/off from the Video widget in the Fly View. + +For more information see [Settings > General (Video / Video Recording)](../settings_view/general.md#video). + +### Plan View + +#### Structure Scan + +A Structure Scan allows you to create a grid flight pattern that captures images over vertical surfaces (polygonal or circular). +These are typically used for the visual inspection or creation of 3d models of structures. + +Details [here](../plan_view/pattern_structure_scan_v2.md). + +#### New MAVLink GeoFence, Rally Point support + +![](../../../assets/plan/geofence_rally.jpg) + +QGC supports the new MAVLink GeoFence and Rally Point specification/protocol. This new system supports multiple polygonal and/or circular fences which can be specified as an exclusion or an inclusion fence. + +The fence which is currently selected by the "Edit" radio button will show the on screen editing controls such as the drag points for polygon editing. + +**Note** Only PX4 Pro firmware supports the new specification. ArduPilot does not yet support the new spec. Support for GeoFence/Rally is temporarily disabled in QGC until QGC ArduPilot code is reworked to the new architecture. + +#### Edit Position Dialog + +![](../../../assets/plan/edit_position_dialog.jpg) + +The Edit Position Dialog allows you to specify a detailed position for an item in either Geographic or UTM coordinate systems. It is available from the Polygon Tools menu as well as the hamburger menu of any mission item which specifies a coordinate: + +![](../../../assets/plan/mission_item_editor_hamburger.jpg) + +#### Polygon Tools + +![](../../../assets/plan/polygon_tools.jpg) + +You can now also click on the polygon center drag handle to bring up a set of polygon manipulation tools. The tools are available anywhere polygon editing is supported: Survey, Structure Scan, GeoFence, ... + +- Circle - Converts the polygon to a circular polygon. +- Polygon - Changes a circular polygon back to a rectangular polygon. +- Set radius - Set radius for circular polygons. +- Edit position - Displays the edit position dialog to specify a detailed position for the circular center. +- Load KML - Set polygon to polygon loaded from KML file. + +Circular polygon example: + + + +### Fly View + +#### Start/Stop Video Recording + +This is now a video record button in the video window. Settings for saved videos are available from General Page of Setup view. + +#### Multi-Vehicle vehicle indicators + +When you are connected to multiple vehicles the vehicle id will be shown below the vehicle icon. The active vehicle will be opaque and the inactive vehicles will be semi-transparent. + +![](../../../assets/fly/multi_vehicle_indicators.jpg) + +#### Multi-Vehicle View supports batch commands + +The multi-vehicle list now supports commands which apply to all vehicles. + +![](../../../assets/fly/multi_vehicle_list.jpg) + +The current list of available commands are Pause and Start Mission but that will be exapanded upon with further development. + +#### ADS-B sensor vehicle display + +Vehicle reported by ADS-B sensor on vehicle are shown on map as smaller blue icons with altitude and callsign below the icon. + +![](../../../assets/fly/adsb_vehicle.jpg) + +## Stable Version 3.2 (Summary) + +:::tip +More detailed release notes for version 3.2 can be found in the next section. +::: + +This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.2. + +- **Settings** + + - **File Save path** - Specify a save path for all files used by QGC. + - **Telemetry log auto-save** - Telemetry logs are now automatically saved without prompting. + - **AutoLoad Plans** - Used to automatically load a Plan onto a vehicle when it first connects. + - **RTK GPS** - Specify the Survey in accuracy and Minimum observation duration. + +- **Setup** + + - ArduPilot only + - **Pre-Flight Barometer and Airspeed calibration** - Now supported + - **Copy RC Trims** - Now supported + +- **Plan View** + + - **Plan files** - Missions are now saved as .plan files which include the mission, geo-fence and rally points. + - **Plan Toolbar** - New toolbar which shows you mission statistics and Upload button. + - **Mission Start** - Allows you to specify values such as flight speed and camera settings to start the mission with. + - **New Waypoint features** - Adjust heading and flight speed for each waypoint as well as camera settings. + - **Visual Gimbal direction** - Gimbal direction is shown on waypoint indicators. + - **Pattern tool** - Allows you to add complex patterns to a mission. + - Fixed Wing Landing (new) + - Survey (many new features) + - **Fixed Wing Landing Pattern** - Adds a landing pattern for fixed wings to your mission. + - **Survey** - New features + - **Take Images in Turnarounds** - Specify whether to take images through entire survey or just within each transect segment. + - **Hover and Capture** - Stop vehicle at each image location and take photo. + - **Refly at 90 degree offset** - Add additional pattern at 90 degree offset to original so get better image coverage. + - **Entry location** - Specify entry point for survey. + - **Polygon editing** - Simple on screen mechanism to drag, resize, add/remove points. Much better touch support. + +- **Fly View** + + - **Arm/Disarm** - Available from toolbar. + - **Guided Actions** - New action toolbar on the left. Supports: + - Takeoff + - Land + - RTL + - Pause + - Start Mission + - Resume Mission - after battery change + - Change Altitude + - Land Abort + - Set Waypoint + - Goto Location + - **Remove mission after vehicle lands** - Prompt to remove mission from vehicle after landing. + - **Flight Time** - Flight time is shown in instrument panel. + - **Multi-Vehicle View** - Better control of multiple vehicles. + +- **Analyze View** - New + + - **Log Download** - Moved to Analyze view from menu + - **Mavlink Console** - NSH shell access + +- **Support for third-party customized QGroundControl** + - Standard QGC supports multiple firmware types and multiple vehicle types. There is now support in QGC which allows a third-party to create their own custom version of QGC which is targeted specifically to their custom vehicle. They can then release their own version of QGC with their vehicle. + +## Stable Version 3.2 (Detailed) + +This is a more detailed high level (but still _non-exhaustive_) list of new features added to _QGroundControl_ in version 3.2. + +### Settings + +#### Telemetry log auto-save + +If you have _Save telemetry log after each flight_ turned on you will no longer be prompted as to where to save the log each time the vehicle disarms. +Logs will automatically be saved to the [Application Load/Save Path](../settings_view/general.md#load_save_path) + +For more information see [Settings > General (Miscellaneous)](../settings_view/general.md#autosave_log). + +#### AutoLoad plans + +If this setting is turned on, _QGroundControl_ will automatically upload a plan to the vehicle when it connects. +The plan file must be named **AutoLoad#.plan** where the `#` is replaced with the vehicle id. +The plan file must be located in the [Application Load/Save Path](../settings_view/general.md#load_save_path). + +For more information see [Settings > General (Miscellaneous)](../settings_view/general.md#autoload_missions). + +#### Application Load/Save Path + +You can now specify a save path which QGC will use as the default location to save files such as Parameters, Telemetry or Mission Plans. + +For more information see [Settings > General (Miscellaneous)](../settings_view/general.md#load_save_path). + +#### RTK GPS + +You can now specify the _Survey in accuracy_ and _Minimum observation duration_ for use with a connected RTK GPS. + +For more information see [Settings > General (RTK GPS)](../settings_view/general.md#rtk_gps). + +### Setup + +#### ArduPilot - Pre-Flight Barometer and Airspeed calibration + +This is now supported from the Sensors page. + +#### ArduPilot - Copy RC Trims + +This is now supported from the Copy Trims button on the Radio setup page. + +### Plan View + +#### Plan Files + +Previous version of _QGroundControl_ saved missions, geo-fences and rally points in separate files (**.mission**, **.fence**, **.rally**). QGC now save all information related to a flight plan into a single file called a _Plan File_ with a file extension of **.plan**. + +Information about the format can be found in [Plan File Format](../../qgc-dev-guide/file_formats/plan.md) (QGC Developer Guide). + +#### Plan Toolbar + +![Plan Toolbar](../../../assets/plan/plan_toolbar.jpg) + +The new _Plan Toolbar_ is displayed at the top of the [PlanView](../plan_view/plan_view.md). +It shows you information related to the currently selected waypoint as well as statistics for the entire mission. + +When connected to a vehicle it also shows an **Upload** button, which can be used to upload the plan to the vehicle. + +#### Mission Settings + +The [Mission Settings](../plan_view/plan_view.md#mission_settings) panel allows you to specify values which apply to the entire mission, or settings you want to control right at the beginning of a mission. +This is the first item in the mission list on the right of the screen. + + + +##### Mission Defaults + +###### Waypoint alt + +This specifies the default altitude for newly added mission items. +If you update this value while you have a mission loaded it will prompt you to update all the the waypoints to this new altitude. + +###### Flight speed + +This allows you to set the flight speed for the mission to be different than the default mission speed. + +###### RTL after mission end + +Check this if you want your vehicle to RTL after the final mission item. + +##### Camera section + + + +The camera section allows you to specify a camera action to take, control the gimbal and set your camera into photo or video mode. + +The camera actions available are: + +- Continue current action +- Take photos (time) +- Take photos (distance) +- Stop taking photos +- Start recording video +- Stop recording video + +##### Vehicle Info section + + + +When planning a mission the firmware being run on the vehicle as well as the vehicle type must be known in order for QGroundControl to show you the mission commands which are appropriate for your vehicle. + +If you are planning a mission while you are connected to your vehicle the Firmware and Vehicle Type will be determined from the vehicle. If you are planning a mission while not connected to a vehicle you will need to specify this information yourself. + +The additional value that can be specified when planning a mission is the vehicle flight speed. By specifying this value, total mission or survey times can be approximated even when not connected to a vehicle. + +##### Planned Home Position + + + +The planned home position allows you to simulate the vehicle's home position while planning a mission. This way you see the waypoint trajectory for your vehicle from takeoff to mission completion. Keep in mind that this is only the "planned" home position and you should place it where you plan to start the vehicle from. It has no actual impact on flying the mission. The actual home position of a vehicle is set by the vehicle itself when arming. + +#### New Waypoint features + + + +- You can now adjust heading and flight speed for each waypoint. +- There is a camera section available for camera changes on each waypoint. Explanation of Camera Section can be read under Mission Settings above. + +#### Visual Gimbal direction + + + +If you specify gimbal yaw changes on waypoints, both the plan and fly views will show you a visual representation of the gimbal direction. + +#### Pattern tool + +There is a new _Pattern tool_. The following patterns are supported: + +- Fixed Wing Landing (new) +- Survey (with new features) + +##### Fixed Wing Landing Pattern + +![Fixed Wing Landing Pattern](../../../assets/plan/pattern/fixed_wing_landing_pattern.jpg) + +This adds a landing pattern for fixed wings to your mission. +The first point of the pattern is the loiter point which commands to vehicle to loiter to a specific altitude. +Once that altitude is reached, the vehicle will begin the landing sequence and fly down to the specified landing spot. + +Both the loiter and land points can be dragged to adjust. +Also all the various values associated with the pattern can be adjusted. + +For more information see [Fixed Wing Landing Pattern](../plan_view/pattern_fixed_wing_landing.md). + +##### Survey (new features) + +- Images are not automatically taken in the turnaround zone outside of the polygonal survey area. +- There is a new _Hover and Capture_ option which can be used to capture the highest quality image at each image location. The vehicle will stop at each image location prior to taking the image such that the vehicle is stable while the image is taken. +- There is a new option to re-fly the survey grid at a 90 degree angle to the previous pass. This allows you to generate much denser coverage for the images. + +![](../../../assets/plan/polygon_edit.jpg) + +Manipulating the survey area polygon is now easier to use on tablets with touch screens: + +- You can drag the entire polygon to a new location by dragging the center point handle. +- Each polygon vertex can be dragged to a new location. +- To remove a polygon vertex, simple click on the drag handle for it. +- Click on the **+** handles to add a new vertex between two existing vertices. + +### Fly View + +#### RTK GPS + +RTK status is now shown in the toolbar. + +#### Arm/Disarm + +There is an armed/disarmed indicator in the toolbar. You can click it to arm/disarm your vehicle. If you click Disarm in the toolbar while your vehicle is flying you will provided the option to Emergency Stop your vehicle. + +#### Guided Actions + +- Takeoff +- Land +- RTL +- Pause +- Actions + - Start Mission + - Resume Mission + - Change Altitude + - Land Abort +- Direct interaction with map + - Set Waypoint + - Goto Location + +##### Resume Mission + +The Resume Mission guided action is used to resume a mission after performing an RTL from within the mission to perform a battery change. +After the vehicle lands from RTL and you have disconnected the battery **do not** disconnect QGC from the Vehicle. +Put in your new battery and QGC will detect the vehicle again and automatically restore the connection. +Once this happens you will be prompted with a Resume Mission confirmation slider. +If you want to resume the mission, confirm this and the mission will be rebuilt from your last waypoint traveled through. +Once the mission is rebuilt you will be presented with another Resume Mission slide which allows you to review the rebuilt mission before starting it again. +Confirm this Resume Mission slider to continue on with the mission. + +\####### How resume mission rebuilding works + +In order to resume a mission you cannot simply continue it from the last mission item the vehicle ran. +The reason is is that may skip over important change speed commands or camera control commands which are prior to that item in the mission. +If you skipped over those the remainder of the mission will not run correctly. +In order to make resume mission work correctly QGC rebuilds the mission looking backwards from the last mission item flown and automatically appends relevant commands to the front of the mission. +By doing this the state of the mission prior to the resume point is restore. +The following mission commands are the ones scanned for: + +- `MAV_CMD_DO_CONTROL_VIDEO` +- `MAV_CMD_DO_SET_ROI` +- `MAV_CMD_DO_DIGICAM_CONFIGURE` +- `MAV_CMD_DO_DIGICAM_CONTROL` +- `MAV_CMD_DO_MOUNT_CONFIGURE` +- `MAV_CMD_DO_MOUNT_CONTROL` +- `MAV_CMD_DO_SET_CAM_TRIGG_DIST` +- `MAV_CMD_DO_FENCE_ENABLE` +- `MAV_CMD_IMAGE_START_CAPTURE` +- `MAV_CMD_IMAGE_STOP_CAPTURE` +- `MAV_CMD_VIDEO_START_CAPTURE` +- `MAV_CMD_VIDEO_STOP_CAPTURE` +- `MAV_CMD_DO_CHANGE_SPEED` +- `MAV_CMD_NAV_TAKEOFF` + +#### Remove mission after vehicle lands + +You will be prompted to remove the mission from the vehicle after the mission completes and the vehicle lands and disarms. +This is meant to prevent issues where stale missions are unknowingly left on a vehicle cause unexpected behavior. + +#### Instrument panel + +##### Camera trigger + +##### Flight Time + +Flight time is now available for display in the instrument panel. +For new users, flight time will be shown by default. +For existing users who have already modified their instrument panel values you will have to add it yourself if you want to use it. + +### [Analyze View](../analyze_view/index.md) + +- [Log Download](../analyze_view/log_download.md) moved to _Analyze View_ from menu. +- New [GeoTag Images](../analyze_view/geotag_images.md) support for PX4 Pro firmware +- New [MAVLink Console](../analyze_view/mavlink_console.md) which provides access the the _nsh shell_ running on the vehicle. + +### Multi-Vehicle View + +There is a new view available when you have multiple vehicles connected to QGC. It will only show up when more than one vehicle is connected. When that happens you will see an additional set of radio button at the top right of the Plan view. + + + +Click the **Multi-Vehicle** radio button to replace the instrument panel with the multi-vehicle list: + + + +The example above shows three vehicles. The numbers are the vehicle id. In the large font is the current flight mode. You can click the flight mode name to change to a different flight mode. To the right are small version of the instruments for each vehicle. You can command the vehicle to do the following actions from the control panel: + +- Arm/Disarm +- Start/Stop a mission +- Return to Launch +- Take Control back of the vehicle by returning to manual control from a mission. + +#### Multi-Vehicle Gotchas - Unique vehicle ids + +Each vehicle connected to QGC must have a unique id. Otherwise QGC will think the vehicles are actually the same vehicle. The symptom of this is the Plan view jerking around as it tries to position itself to one vehicle and then the next. For PX4 Pro firmwares this is the `MAV_SYS_ID` parameter. For ArduPilot firmwares it is the `SYSID_THISMAV` parameter. + +### Support for third-party customized QGroundControl + +Standard QGC supports multiple firmware types and multiple vehicle types. There is now support in QGC which allows a third-party to create their own custom version of QGC which is targeted specifically to their custom vehicle. They can then release their own version of QGC with their vehicle. + +## Stable Version 3.1 + +New Features + +- [Survey](../plan_view/pattern_survey.md) mission support +- [GeoFence](../plan_view/plan_geofence.md) support in Plan View +- [Rally Point](../plan_view/plan_rally_points.md) support in Plan View (ArduPilot only) +- ArduPilot onboard compass calibration +- Parameter editor search will now search as you type for quicker access +- Parameter display now supports unit conversion +- GeoTag images from log files (PX4 only) +- System health in instrument panel +- MAVLink 2.0 support (no signing yet) + +Major Bug Fixes + +- Fixed crash after disconnect from Vehicle +- Fixed android crash when using SiK Radios +- Many multi-vehicle fixes +- Bluetooth fixes diff --git a/docs/ko/qgc-user-guide/releases/release_note_stable_v4.md b/docs/ko/qgc-user-guide/releases/release_note_stable_v4.md new file mode 100644 index 00000000000..873f71f3d98 --- /dev/null +++ b/docs/ko/qgc-user-guide/releases/release_note_stable_v4.md @@ -0,0 +1,58 @@ +# QGC v4 Release Notes + +:::warning +Release notes are now tracked in the [Github release page](https://github.com/mavlink/qgroundcontrol/releases). +See that page for information about changes after v4.0.0. +::: + +## Stable Version 4.0 + +:::info +The format for Settings in QGC had to change in this release. Which means all QGC settings will be reset to defaults. +::: + +- Settings + - Language: Allow selection of language + - Optional [CSV Logging](../settings_view/csv.md) of telemetry data for improved accessibility. + - ArduPilot + - Support configurable mavlink stream rates. Available from Settings/Mavlink page. + ![Stream Rates JPG](../../../assets/daily_build_changes/arducopter_stream_rates.jpg) + - Improved support for flashing ChibiOS firmware + - Improved support for connecting to ChibiOS bootloader boards +- Setup + - Joystick + - New joystick setup ui + - Ability to configure held button to single or repeated action + - ArduPilot + - Motor Test + - ArduSub + - Automatic motor direction detection + - ArduCopter + - PID Tuning support ![PID Tuning JPG](../../../assets/daily_build_changes/arducopter_pid_tuning.jpg) + - Additional Basic Tuning options ![Basic Tuning JPG](../../../assets/daily_build_changes/arducopter_basic_tuning.jpg) + - Copter/Rover - Frame setup ui ![Setup Frame Copter JPG](../../../assets/daily_build_changes/arducopter_setup_frame.jpg) +- Plan + - Create Plan from template with wizard like progression for completing full Plan. + - Survey: Save commonly used settings as a Preset + - Polygon editing + - New editing tools ui + - Support for tracing a polygon from map locations + - ArduPilot + - Support for GeoFence and Rally Points using latest firmwares and mavlink v2 + - [Pattern Presets](../plan_view/pattern_presets.md) + - Allows you to save settings for a Pattern item (Survey, Corridor Scan, ...) into a named preset. You can then use this preset over and over again as you create new Pattern. +- Fly + - Click to ROI support + - Added support for connecting to ADSB SBS server. Adds support for ADSB data from USB SDR Dongle running 'dump1090 --net' for example. + - Ability to turn on Heading to home, COG and Next Waypoint heading indicators in Compass. + - Video + - Add support for h.265 video streams + - Automatically add a [Video Overlay](../fly_view/video_overlay.md) with flight data as a subtitle for locally-recorded videos + - Vehicle type specific pre-flight checklists. Turn on from Settings. +- Analyze + - New Mavlink Inspector which includes charting support. Supported on all builds including Android and iOS. +- General + - Released Windows build are now 64 bit only + - Log Replay: Ability to specify replay speed + - ArduPilot + - Improved support for chibios firmwares and ArduPilot bootloader with respect to flashing and auto-connect. diff --git a/docs/ko/qgc-user-guide/releases/release_notes.md b/docs/ko/qgc-user-guide/releases/release_notes.md index 0b41ac85307..63ba1f4bd9a 100644 --- a/docs/ko/qgc-user-guide/releases/release_notes.md +++ b/docs/ko/qgc-user-guide/releases/release_notes.md @@ -1,254 +1,7 @@ # Release Notes -This topic contains the cumulative release notes for _QGroundControl_. +Releases and their associated release notes can be found in the [Github releases page](https://github.com/mavlink/qgroundcontrol/releases). :::info -안정적인 빌드 메이저 및 마이너 번호는 다음과 같습니다. -_패치_ 배포 번호는 표시되어 있지 않으나, [Github 배포 페이지](https://github.com/mavlink/qgroundcontrol/releases)에서 나와 있습니다. +Release information about QGC v4.0.0 and earlier can be found in the sub pages. ::: - -## 안정 버전 4.0(현재) - -:::info -QGroundControl의 설정 형식은 이번 배포판에서 변경되었습니다. 즉, 모든 QGroundControl의 설정이 기본값으로 재설정됩니다. -::: - -- 설정 - - 언어: 언어 선택 허용 - - 접근성 향상을 위한 원격 측정 데이터의 선택적 [CSV 로깅](../settings_view/csv.md). - - ArduPilot - - Mavlink: 가능한 스트리밍 속도 설정 -- 설정 - - 조이스틱 - - 새로운 조이스틱 설정 UI - - 보류 버튼을 단일 또는 반복 작업으로 설정하는 기능 - - ArduPilot - - 모터 테스트 - - ArduSub - - 자동 모터 방향 감지 -- 계획 - - 전체 계획을 완료 마법사를 사용하여 템플릿에서 계획을 생성. - - 설문조사: 자주 사용하는 설정을 사전 설정으로 저장 - - 다각형 편집 - - 새로운 편집 도구 UI - - 지도 위치에서 폴리곤 추적 지원 - - ArduPilot - - 최신 펌웨어 및 mavlink v2를 사용하여 GeoFence 및 Rally Points 지원 -- 비행 - - 클릭하여 ROI 지원 - - ADSB SBS 서버에 연결하기 위한 지원이 추가되었습니다. 예를 들어 'dump1090 --net'을 실행하는 USB SDR 동글의 ADSB 데이터에 대한 지원을 추가합니다. - - 나침반에서 집으로 향하는 방향, COG 및 다음 웨이포인트 방향 표시기를 켤 수 있는 기능. - - 비디오 - - h.265 비디오 스트림 지원 추가 - - 비행 데이터가 포함된 [동영상 오버레이](../fly_view/video_overlay.md)를 현지에서 녹화된 동영상의 자막으로 자동 추가 - - 차량 유형별 비행 전 체크리스트. 설정에서 켜기 -- 분석 - - 차트 지원을 포함하는 새로운 Mavlink 탐색기. Android 및 iOS를 포함한 모든 빌드에서 지원됩니다. -- 일반 - - 릴리스된 Windows 빌드는 이제 64비트 전용입니다. - - 로그 재생: 재생 속도 지정 기능 - - ArduPilot - - 플래싱 및 자동 연결과 관련하여 chibios 펌웨어 및 ArduPilot 부트로더에 대한 지원이 향상되었습니다. - -일부 기능들에 대한 자세한 내용은 [v4.0](../releases/stable_v4.0_additional.md)을 참고하십시오. - -## 안정 버전 3.5 - -이 섹션에는 버전 3.5에서 _QGroundControl_에 추가된 새 기능의 상위 수준 및 _전체_ 목록이 포함되어 있습니다. - -- **전체** - - QGC에 Airmap 통합을 추가하였습니다. OSX 빌드 전용. - - 범프 설정 버전(현재 8). - 이렇게 하면 모든 설정들이 기본값으로 재설정됩니다. - - 중국어, 터키어 및 부분적인 독일어 번역이 추가되었습니다. - - Taisync 2.4GHz ViUlinx 디지털 HD 무선 네트웍 지원이 추가되었습니다. - - 여러 구성 요소에서 매개변수 로드를 수정합니다. - 이것은 특히 WiFi 연결에 큰 변화가 일어났습니다. - - **ArduPilot** ChibiOS 펌웨어 연결 및 플래시 지원. -- **설정** - - **RTK** 설정/일반에서 고정 RTK 기반 스테이션 위치 지정에 대한 지원을 추가합니다. - - **GCS 위치** - - NMEA GPS 장치용 UDP 포트 옵션이 추가되었습니다. - - 사용 가능한 경우 GCS 방향 표시 -- **계획** - - **폴리곤** SHP 파일에서 폴리곤 불러오기를 지원합니다. - - **고정익 착륙 패턴** 정지 사진 및 동영상 지원이 추가되었습니다. - RTL을 수행하면 카메라가 중지되도록 기본값은 켜짐입니다. - - **위치 편집 대화상자** 폴리곤 정점에서 사용할 수 있습니다. -- **비행** - - **카메라 페이지** 새로운 MAVLink 카메라 메시지에 대한 지원이 업데이트되었습니다. - 카메라 선택, 카메라 모드, 사진/동영상 시작/중지, 스토리지 관리 등등 - - **궤도** 회전 방향 변경 지원. - - **계기판** - - 새로운 estimatorStatus Vehicle FactGroup에 ESTIMATOR_STATUS 값을 추가하였습니다. - 이제 계기판에 표시할 수 있습니다. - - 계기판에서 표시할 수 있도록 GCS까지의 거리를 설정합니다. - - Make Heading to Home available for display from instrument panel. - -## 안정 버전 3.4 - -이 섹션에는 버전 3.4에서 _QGroundControl_에 추가된 새 기능의 상위 수준 및 _전체_ 목록이 포함되어 있습니다. 각 안정적인 릴리스에서 다수의 버그들이 수정되었습니다. - -- **설정** - - **오프라인 지도** - - Center Tool을 사용하면 위도/경도 또는 UTM 좌표로 지도 위치를 지정할 수 있습니다. 생성하는 오프라인 지도 영역을 편리하게 수정할 수 있습니다. - - 오프라인 사용을 위해 지형 높이를 미리 다운로드합니다. - - **Help** QGC 사용자 가이드 및 포럼에 대한 링크를 제공합니다. - -- **설정** - - **펌웨어** PX4 또는 ArduPilot Flow 펌웨어를 플래시하는 기능. - - PX4 프로 펌웨어 - - **비행 모드** 사용 가능한 모든 송신기 스위치에 대한 채널을 지정합니다. - - **튜닝: 고급** 차량 PID 튜닝 지원의 초기 구현. 이것은 3.5 일일 빌드에서 수정중인 개선 사항입니다. - - ArduPilot 펌웨어 - - **전원/안전** 새로운 다중 배터리 설정을 지원합니다. - - **Trad Heli** 새로운 설정 페이지. - -- **계획** - - - **파일 로드/저장** 표준 파일 로드/저장/다른 이름으로 저장 사용자 모델과 일치하는 계획 파일 로드를 위한 새 모델입니다. - - - **KML 로드** 동기화 메뉴에서 직접 KML 파일을 로드하는 기능. 필요한 경우 KML에서 생성하려는 패턴 유형을 묻는 메시지가 표시됩니다. - - - **탐사** 불규칙한 모양의 다각형에 대한 지원이 개선되었습니다. - - - **[복도 스캔](../plan_view/pattern_corridor_scan.md)** - 폴리라인 형태의 비행 패턴을 생성합니다. 예를 들어, 도로 조사에 사용할 수 있습니다. - - - **[고정익 착륙 패턴](../plan_view/pattern_fixed_wing_landing.md)** - - 평면도에 시각적으로 표시되는 착륙 영역. - - 착륙 위치/방향은 차량 위치/방향에서 복사할 수 있습니다. - - - **비행** - - - 미션 아이템의 높이는 지형 위의 높이로 지정할 수 있습니다. - - 측량 및 복도 스캔은 지형을 따라 비행 계획을 생성할 수 있습니다. - - **Note** 이 기능은 [ArduPilot 지형 추적](http://ardupilot.org/copter/docs/common-terrain-following.html) 기능을 지원하지 않습니다. - ::: - - - **위치 편집** 차량 위치에서 항목 위치를 설정합니다. - -- **비행** - - **비행 전 체크리스트** 설정에서 이 기능을 켤 수 있습니다. 비행 전에 따라야 할 일반적인 체크리스트를 제공합니다. 3.5 일일 빌드에서 더 많은 기능이 제공할 예정입니다. - - **계기판** - - 많은 새로운 값을 표시할 수 있습니다. - - New Camera page which provides full camera control. 새로운 MavLink 카메라 사양을 지원하는 카메라가 필요합니다. - - **ArduPlane** QuadPlane 지원을 포함하여 안내 명령에 대한 지원이 향상되었습니다. - - **높은 대기 시간 링크** 위성 연결과 같은 대기 시간이 긴 링크를 지원합니다. - 비용을 줄이기 위하여 이러한 링크에서 QGroundControl에서 기체 트래픽을 제한합니다. - HIGH_LATENCY MavLink 메시지를 지원합니다. - 듀얼 링크 설정으로, 높은 대기 시간에서 일반 링크로의 장애 복구를 지원합니다. - -## 안정 버전 3.3 - -:::tip -버전 3.3에 대한 자세한 출시 정보는 [여기](../releases/stable_v3.3_long.md)에서 확인할 수 있습니다. -::: - -이 섹션에는 버전 3.3에서 _QGroundControl_에 추가된 새 기능의 상위 수준 및 _전체_ 목록이 포함되어 있습니다. Not to mention the large number of bug fixes of this release. - -- **설정** - - 로컬 NMEA GPS 장치 지원. - - 비디오 녹화 설정을 저장합니다. -- **설정** - - **매개변수 편집기** - 검색에 거의 즉각적인 응답을 위해 문자를 입력할 때 검색이 업데이트됩니다. - - **조이스틱** - Android 조이스틱 지원. -- **계획** - - **새로운 기능 - 구조 스캔 패턴** - 수직 표면(다각형 또는 원형) 위의 이미지를 캡처하는 다층 비행 패턴을 생성합니다. 3D 모델 생성 또는 수직 표면 검사에 사용됩니다. - - **고정익 착륙 패턴** - 거리 또는 활공 경사 낙하율로 배회지에서 착륙 지점까지의 거리를 조정할 수 있습니다. - - PX4 GeoFence 및 Rally Point 지원. - - 낮은 임무 항목 고도 표시의 지형 고도 표시 -- **지형** - - 비디오 녹화를 시작/중지합니다. - - 여러 기체에 연결된 경우 기체 아이콘이 더 잘 표시됩니다. - - 다중 기체 보기는 모든 기체에 적용되는 명령을 지원합니다. - - ADS-B 센서에서 보고된 기체를 표시합니다. -- **분석** - - **Mavlink 콘솔** - Mavlink 콘솔과의 통신을 위한 새로운 지원. - - **로그 다운로드** - 메뉴에서 분석 보기로 이동하였습니다. - -## 안정 버전 3.2 - -:::tip -버전 3.2에 대한 자세한 출시 정보는 [여기](../releases/stable_v3.2_long.md)에서 확인할 수 있습니다. -::: - -이 섹션에는 버전 3.2에서 _QGroundControl_에 추가된 새 기능의 상위 수준 및 _전체_ 목록이 포함되어 있습니다. - -- **설정** - - - **파일 저장 경로** - QGroundControl에서 사용하는 모든 파일의 저장 경로를 지정합니다. - - **원격 측정 로그 자동 저장** - 이제 원격 측정 로그를 묻지 않고, 자동으로 저장합니다. - - **계획 자동 로드** - 기체 최조 연실시 미션을 자동으로 로드합니다. - - **RTK GPS** - 정확도와 최소 관찰 기간으로 측량을 지정합니다. - -- **설정** - - - ArduPilot 전용 - - **비행 전 기압계 및 속도 보정** - 이제 지원됨 - - **RC 트림 복사** - 이제 지원됨 - -- **계획 화면** - - - **계획 파일** - 이제 임무가 임무, 지오펜스 및 집결 지점을 포함하는 .plan 파일로 저장됩니다. - - **계획 도구 모음** - 미션 통계와 업로드 버튼을 표시하는 새로운 도구 모음입니다. - - **미션 시작** - 비행 속도 및 카메라 설정과 같은 값을 지정하여 미션을 시작할 수 있습니다. - - **새로운 웨이포인트 기능** - 각 웨이포인트와 카메라 설정에 대한 방향과 비행 속도를 조정합니다. - - **시각적 짐벌 방향** - 짐벌 방향은 웨이포인트 표시기에 표시됩니다. - - **패턴 도구** - 미션에 복잡한 패턴을 추가할 수 있습니다. - - 고정익 착륙 (신규) - - 탐사(많은 신규 기능) - - **고정익 착륙 패턴** - 미션에 고정익 착륙 패턴을 추가합니다. - - **탐사** - 새로운 기능 - - **턴어라운드로 이미지 찍기** - 전체 설문조사를 통해 이미지를 촬영 여부나 각 횡단 세그먼트 내에서만 이미지를 촬영 여부를 지정합니다. - - **마우스 오버 및 캡처** - 각 이미지 위치에서 차량을 멈추고 사진을 찍습니다. - - **90도 오프셋에서 반사** - 원본에 90도 오프셋으로 패턴을 추가하여 이미지 범위를 개선합니다. - - **진입 위치** - 설문조사의 진입점을 지정합니다. - - **폴리곤 편집** - 드래그, 크기 조정, 포인트 추가/제거를 위한 간단한 화면 메커니즘. 터치 기능 개선 및 지원 - -- **비행 화면** - - - **시동/비시동** - 도구 모음에서 사용할 수 있습니다. - - **안내 작업** - 왼쪽에 새로운 작업 도구 모음이 있습니다. 지원: - - 이륙 - - 착륙 - - RTL - - 일시 중지 - - 미션 시작 - - 임무 재개 - 배터리 교체 후 - - 고도 변경 - - Land Abort - - 경로점 설정 - - 위치 이동 - - **차량 착륙 후 임무 제거** - 착륙 후 차량에서 임무를 제거하라는 메시지가 표시됩니다. - - **비행 시간** - 비행 시간은 계기판에 표시됩니다. - - **여러 기체 보기** - 여러 기체들을 제어가 편리합니다. - -- **분석 화면** - 신규 - - - **로그 다운로드** - 메뉴에서 분석 보기로 이동 - - **Mavlink 콘솔** - NSH 셸 액세스 - -- **타사 맞춤형 QGroundControl 지원** - - 표준 QGroundControl는 여러가지 펌웨어 유형과 여러가지 기체 유형을 지원합니다. 이제 QGroundControl에서 지원이 제공되어 타사에서 사용자 지정 차량을 대상으로 하는 자체 사용자 지정 버전의 QGroundControl를 만들 수 있습니다. 그런 다음, 기체와과 함께 자체 버전의 QGroundControl를 출시할 수 있습니다. - -## 안정 버전 3.1 - -새로운 기능 - -- [탐사](../plan_view/pattern_survey.md) 미션 지원 -- 계획 화면에서 [GeoFence](../plan_view/plan_geofence.md) 지원 -- 계획 화면에서 [Rally Point](../plan_view/plan_rally_points.md) 지원(ArduPilot만 해당) -- ArduPilot 온보드 나침반 보정 -- 더 빠른 액세스를 위해 입력 시 매개변수 편집기를 검색합니다. -- 이제 매개변수에서 단위 변환을 지원합니다. -- 로그 파일의 GeoTag 이미지(PX4만 해당) -- System health in instrument panel -- MAVLink 2.0 지원(아직 서명 없음) - -주요 버그 수정 - -- 기체 연결 해제 후 충돌 수정 -- SiK 라디오를 사용할 때 안드로이드 충돌 수정 -- 많은 다중 차량 수정 -- 블루투스 수정 diff --git a/docs/ko/qgc-user-guide/settings_view/console_logging.md b/docs/ko/qgc-user-guide/settings_view/console_logging.md index 470df5dd41a..5fd21b03bce 100644 --- a/docs/ko/qgc-user-guide/settings_view/console_logging.md +++ b/docs/ko/qgc-user-guide/settings_view/console_logging.md @@ -10,15 +10,15 @@ _콘솔_은 _QGroundControl_ 문제를 진단하는 데 유용한 도구입니 The most commmonly used logging options are listed below. -| 옵션 | 설명 | -| ----------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | -| `LinkManagerLog`, `MultiVehicleManagerLog` | 디버그 연결 문제 | +| 옵션 | 설명 | +| ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | +| `LinkManagerLog`, `MultiVehicleManagerLog` | 디버그 연결 문제 | | `LinkManagerVerboseLog` | Debug serial ports not being detected. 디버그 직렬 포트 미감지 사용 가능한 직렬 포트의 매우 시끄러운 연속 출력. | -| `FirmwareUpgradeLog` | 펌웨어 플래시 문제를 디버그 | -| `ParameterManagerLog` | 디버그 매개변수 로드 문제 | -| `ParameterManagerDebugCacheFailureLog` | 디버그 매개변수 캐시 crc가 누락 | -| `PlanManagerLog`, `MissionManagerLog`, `GeoFenceManagerLog`, `RallyPointManagerLog` | 디버그 계획 업로드/다운로드 문제 | -| `RadioComponentControllerLog` | 무선 보정 문제를 디버그 | +| `FirmwareUpgradeLog` | 펌웨어 플래시 문제를 디버그 | +| `ParameterManagerLog` | 디버그 매개변수 로드 문제 | +| `ParameterManagerDebugCacheFailureLog` | 디버그 매개변수 캐시 crc가 누락 | +| `PlanManagerLog`, `MissionManagerLog`, `GeoFenceManagerLog`, `RallyPointManagerLog` | 디버그 계획 업로드/다운로드 문제 | +| `RadioComponentControllerLog` | 무선 보정 문제를 디버그 | ## 명령줄 로깅 diff --git a/docs/ko/qgc-user-guide/setup_view/flight_modes.md b/docs/ko/qgc-user-guide/setup_view/flight_modes.md index fee3b498cb3..2e423701b3f 100644 --- a/docs/ko/qgc-user-guide/setup_view/flight_modes.md +++ b/docs/ko/qgc-user-guide/setup_view/flight_modes.md @@ -56,6 +56,6 @@ That's it! FrSky Taranis에서 이 프로세스는 두 개의 실제 스위치 위치의 각 조합에 "논리적 스위치"를 할당하는 것을 포함합니다. 그런 다음 각 논리적 스위치는 동일한 채널에서 다른 PWM 값에 할당됩니다. -이 비디오는 _FrSky Taranis_ 송신기를 사용한 수행과정을 나타냅니다: https\://youtu.be/TFEjEQZqdVA +이 비디오는 _FrSky Taranis_ 송신기를 사용한 수행과정을 나타냅니다: https://youtu.be/TFEjEQZqdVA diff --git a/docs/ko/qgc-user-guide/setup_view/flight_modes_ardupilot.md b/docs/ko/qgc-user-guide/setup_view/flight_modes_ardupilot.md index 057d3b29bc3..b09e3a2ee65 100644 --- a/docs/ko/qgc-user-guide/setup_view/flight_modes_ardupilot.md +++ b/docs/ko/qgc-user-guide/setup_view/flight_modes_ardupilot.md @@ -42,8 +42,9 @@ ArduPilot에서 최대 6개의 다른 비행 모드를 송신기의 단일 채 모든 값은 변경시에 자동으로 저장됩니다. -위의 ArduCopter 스크린샷은 채널 7 스위치에 RTL의 추가 옵션이 있는 3위치 비행 모드 스위치의 일반적인 설정을 보여줍니다. -또한 2개의 스위치와 송신기의 믹싱을 사용하여 6가지 비행 모드를 설정할 수 있습니다. 방법에 대한 자습서를 보려면 이 [페이지](http://ardupilot.org/copter/docs/common-rc-transmitter-flight-mode-configuration.html#common-rc-transmitter-flight-mode-configuration)의 중앙 섹션으로 스크롤하십시오. +:::info +The ArduCopter screenshot above shows a typical setup for a three position flight mode switch with an additional option of RTL being on a channel 7 switch. +You can also setup 6 flight modes using two switches plus mixing on your transmitter. Scroll down to the center section of this [page](http://ardupilot.org/copter/docs/common-rc-transmitter-flight-mode-configuration.html#common-rc-transmitter-flight-mode-configuration) for tutorials on how to do that. ::: ## See Also diff --git a/docs/ko/qgc-user-guide/setup_view/joystick.md b/docs/ko/qgc-user-guide/setup_view/joystick.md index 10621f8fb40..5f501d669fd 100644 --- a/docs/ko/qgc-user-guide/setup_view/joystick.md +++ b/docs/ko/qgc-user-guide/setup_view/joystick.md @@ -18,8 +18,8 @@ _QGroundControl_은 RC 송신기 대신 조이스틱이나 게임패드로 기 ## PX4 조이스틱 활성화 -PX4에서 조이스틱 지원을 활성화하려면 매개변수 [`COM_RC_IN_MODE`](h[ttp://localhost:8080/px4_user_guide/en](https://docs.px4.io/en/main/advanced_config/parameter_reference.html#COM_RC_IN_MODE)을 `10`이면 _조이스틱_이 설정 옵션으로 제공되지 않습니다. +To enable Joystick support in PX4 you need to set the parameter [`COM_RC_IN_MODE`](https://docs.px4.io/en/main/advanced_config/parameter_reference.html#COM_RC_IN_MODE) to `1` - _Joystick_. +이 매개변수가 `0`이면 _조이스틱_이 설정 옵션으로 제공되지 않습니다. This is enabled by default for PX4 SITL builds (see the [Parameters](../setup_view/parameters.md) topic for information on how to find and set a particular parameter). diff --git a/docs/ko/qgc-user-guide/setup_view/motors.md b/docs/ko/qgc-user-guide/setup_view/motors.md index 52758b5bbc8..a1d4c307b7d 100644 --- a/docs/ko/qgc-user-guide/setup_view/motors.md +++ b/docs/ko/qgc-user-guide/setup_view/motors.md @@ -20,14 +20,19 @@ 2. (_PX4 전용_) 안전 스위치 활성화(장착된 경우) -3. 스위치를 밀어 모터 슬라이더를 활성화합니다(레이블: _프로펠러 제거 - 모터 슬라이더 활성화_). +3. Slide the switch to enable motor slider and buttons (labeled: _Propellers are removed - Enable slider and motors_). -4. 개별 슬라이더를 조정하여 모터를 회전시키고, 올바른 방향으로 회전하는 지 확인합니다. +4. Adjust the slider to select the power for the motors. + +5. Press the button corresponding to the motor and confirm it spin in the correct direction. ::: info - 모터는 슬라이더를 놓은 후에만 회전하며 3초 후에 자동으로 회전을 멈춥니다. + The motors will automatically stop spinning after 3 seconds. + You can also stop the motor by pressing the 'Stop' button. + If no motors turn, raise the “Throttle %” and try again. ::: ## 추가 정보 - [기본 설정 > 모터 설정](http://docs.px4.io/master/en/config/motors.html) (_PX4 사용자 가이드_) - 여기에는 추가 PX4 관련 정보를 설명합니다. +- [ESCS and Motors](https://ardupilot.org/copter/docs/connect-escs-and-motors.html#motor-order-diagrams) - This is the Motor order diagrams for all frames diff --git a/docs/ko/qgc-user-guide/setup_view/parameters.md b/docs/ko/qgc-user-guide/setup_view/parameters.md index 824fef148a4..fbc800a5341 100644 --- a/docs/ko/qgc-user-guide/setup_view/parameters.md +++ b/docs/ko/qgc-user-guide/setup_view/parameters.md @@ -38,6 +38,6 @@ _검색_ 필드에 용어를 입력하여 매개변수를 _검색_합니다. 그 **파일에서 불러오기 / 파일에 저장**
기존 파일에서 매개변수를 불러오거나 현재 매개변수 설정을 파일에 저장합니다. -**RC를 Param으로 지우기**
이것은 RC 송신기 제어와 매개변수간의 연관성을 모두 삭제합니다. 자세한 내용은 [라디오 설정 > 매개변수 튜닝 채널](../setup_view/Radio.md#param-tuning-channels-px4)를 참고하십시오. +**RC를 Param으로 지우기**
이것은 RC 송신기 제어와 매개변수간의 연관성을 모두 삭제합니다. For more information see: [Radio Setup > Param Tuning Channels](../setup_view/radio.md#param-tuning-channels-px4). **기체 재부팅**
기체을 재부팅합니다 (일부 매개변수를 변경후에 요구됩니다). diff --git a/docs/ko/qgc-user-guide/setup_view/tuning_px4.md b/docs/ko/qgc-user-guide/setup_view/tuning_px4.md index 0ae0f3fc5c4..2944c708667 100644 --- a/docs/ko/qgc-user-guide/setup_view/tuning_px4.md +++ b/docs/ko/qgc-user-guide/setup_view/tuning_px4.md @@ -36,7 +36,7 @@ Tuning only needs to be done once, and is recommended unless you're using vehicl 3. _좌회전 오른쪽 롤 중심_ (전체 기동은 약 3초가 소요됩니다). 차량은 2번의 진동 내에서 안정되어야 합니다. 4. 각 시도에서 더 큰 진폭으로 기울이면서 기동을 반복합니다. - 기체가 \~20도에서 2번의 진동 내에서 안정화될 수 있으면 다음 단계로 이동합니다. + 기체가 ~20도에서 2번의 진동 내에서 안정화될 수 있으면 다음 단계로 이동합니다. 5. 피치 축에서 동일한 동작을 반복합니다. 위의 A에서 작은 각도로 시작하여 기체의 틸트를 증가시키기 전에 2개의 진동 내에서 스스로 움직일 수 있는 지 확인하십시오. @@ -47,7 +47,7 @@ Tuning only needs to be done once, and is recommended unless you're using vehicl ### 자동 튜닝 절차 자동 튜닝은 **충분한 공간이 있는 안전한 지역**에서 진행하여야 합니다. -약 40초(19\~68초)가 걸립니다. +약 40초(19~68초)가 걸립니다. 최상의 결과를 얻으려면 날씨가 좋고 바람이 적을 때 테스트 하는 것이 좋습니다. :::info @@ -60,7 +60,7 @@ RC 컨트롤러로 자동 튜닝 프로세스를 중단할 준비를 하십시 2. RC를 사용하여 이륙하고 테스트 준비: - **멀티콥터:** **고도 모드**에서 조종기를 사용하여 이륙합니다. - 안전한 거리와 지상에서 몇 미터(4\~20m)에서 기체를 호버링하십시오. + 안전한 거리와 지상에서 몇 미터(4~20m)에서 기체를 호버링하십시오. - **고정익 모드의 VTOL:** 순항 속도로 비행하면 **홀드 모드**를 활성화합니다. 이렇게 하면 비행기가 일정한 고도와 속도로 원을 그리며 비행합니다. @@ -107,7 +107,7 @@ PID 값을 변경할 때 사용할 스텝 크기의 종류에 대한 자세한 1. RC를 사용하여 이륙하고 테스트 준비: - **멀티콥터:** **고도 모드**에서 조종기를 사용하여 이륙합니다. - 안전한 거리와 지상에서 몇 미터(4\~20m)에서 기체를 호버링하십시오. + 안전한 거리와 지상에서 몇 미터(4~20m)에서 기체를 호버링하십시오. - **고정익:** 순항 속도로 비행하면 **유지 모드**를 활성화합니다. 이렇게 하면 비행기가 일정한 고도와 속도로 원을 그리며 비행합니다. diff --git a/docs/ko/qgc-user-guide/viewer_3d/viewer_3d.md b/docs/ko/qgc-user-guide/viewer_3d/viewer_3d.md new file mode 100644 index 00000000000..f90339efe72 --- /dev/null +++ b/docs/ko/qgc-user-guide/viewer_3d/viewer_3d.md @@ -0,0 +1,53 @@ +# 3D View + +The 3D View is used to visualize and monitor the vehicle, the environment, and the planned mission in 3D. Most of the capabilities available in the [Fly View](../fly_view/fly_view.md) is also available in the 3D View. + +You can use it to: + +- To import and display the 3D map for any region of interest downloaded from the OpenStreetMap website (.osm file). +- Display the vehicle along with its mission in 3D. +- And most of the capabilities of the [Fly View](../fly_view/fly_view.md), including: + - Run an automated [pre-flight checklist](#preflight_checklist). + - Arm the vehicle (or check why it won't arm). + - Control missions: [start](#start_mission), [continue](#continue_mission), [pause](#pause), and [resume](#resume_mission). + - Guide the vehicle to [arm](#arm)/[disarm](#disarm)/[emergency stop](#emergency_stop), [takeoff](#takeoff)/[land](#land), [change altitude](#change_altitude), and [return/RTL](#rtl). + - Switch between a map view and a video view (if available) + - Display video, mission, telemetry, and other information for the current vehicle, and also switch between connected vehicles. + +![3D View](../../../assets/viewer_3d/viewer_3d_overview.jpg) + +# UI Overview + +The screenshot above shows the main elements of the 3D View. + +**Enabling the 3D View:** The 3D View is disabled by default. To enable it, go to **Application Settings** ->**Fly View** tab, and under the **3D View** settings group, toggle the **Enabled** switch as shown below: + +![3D View](../../../assets/viewer_3d/enable_3d_view.jpg) + +To open the 3D View, when you are in the [Fly View](../fly_view/fly_view.md), from the toolbar on the left, select the 3D View icon as illustrated below: + +![3D View](../../../assets/viewer_3d/open_3d_viewer.jpg) + +Once the 3D View is opened, you can navigate through the 3D environment by using either a mouse or a touchscreen as follows: + +- **Mouse:** + - **To move horizontally and vertically**: Press and hold the mouse left-click, then move the cursor. + - **To rotate**: Press and hold the mouse right-click, then move the cursor. + - **To zoom**: Use the mouse wheel\middle button. + +- **Touchscreen:** + - **To move horizontally and vertically**: Use a single finger, then tap and move your finger. + - **To rotate**: Use two fingers, then tap and move your fingers while keeping them together. + - **To zoom**: Use a pinch with two fingers and move them together or apart to zoom in or out. + +To visualize the 3D map of a particular area in the 3D viewer, you have to download the .osm file of that area from the [OpenStreetMap](https://www.openstreetmap.org/#map=16/47.3964/8.5498) website and then import it through the **3D View** settings. More details on the **3D View** settings can be found in the next section. + +# Settings + +You can change the settings of the 3D View from **Application Settings** ->**Fly View** tab under the **3D View** settings group. +The following properties can be modified in the 3D View settings group: + +- **Enabled**: To enable or disable the 3D View. +- **3D Map File**: The path to the .osm file of a region of interest to be visualized in the QGC. The .osm file can be uploaded by clicking on the **Select File** button. To clear the 3D View from the previously loaded .osm file, you can click on the **Clear** button. +- **Average Building Level Height**: This parameter determines the height of each storey of the buildings, as in .osm file sometimes the height of the buildings is specified in terms of the level/storey. +- **Vehicle Altitude Bias**: This refers to the bias in the altitude of vehicles and their missions with respect to the ground level. It is helpful in cases where the estimated altitude of the vehicle by its flight control is biased, as the relative altitude is currently used in the 3D View. diff --git a/docs/tr/SUMMARY.md b/docs/tr/SUMMARY.md index b1ac96f407e..9493285e911 100644 --- a/docs/tr/SUMMARY.md +++ b/docs/tr/SUMMARY.md @@ -2,14 +2,24 @@ - [Overview](qgc-user-guide/index.md) - [Quick Start](qgc-user-guide/getting_started/quick_start.md) - - [Download and Install](qgc-user-guide/getting_started/download_and_install.md) + - [Download and Install (Daily 5.0)](qgc-user-guide/releases/daily_builds.md) - [Support](qgc-user-guide/support/support.md) -- [Fly](qgc-user-guide/fly_view/fly_view.md) +- [Fly View](qgc-user-guide/fly_view/fly_view.md) + - [Toolbar](qgc-user-guide/fly_view/fly_view_toolbar.md) + - [Fly Tools](qgc-user-guide/fly_view/fly_tools.md) + - [Instrument Panel](qgc-user-guide/fly_view/instrument_panel.md) + - [Attitude/Compass](qgc-user-guide/fly_view/hud.md) + - [Camera Tools](qgc-user-guide/fly_view/camera_tools.md) + - [Video](qgc-user-guide/fly_view/video.md) + - [Video Overlay](qgc-user-guide/fly_view/video_overlay.md) - [Replay Flight Data](qgc-user-guide/fly_view/replay_flight_data.md) - - [Video Overlay](qgc-user-guide/fly_view/video_overlay.md) -- [Plan](qgc-user-guide/plan_view/plan_view.md) +- [Mavlink Actions](qgc-user-guide/custom_actions/custom_actions.md) + +- [3D View](qgc-user-guide/viewer_3d/viewer_3d.md) + +- [Plan Flight](qgc-user-guide/plan_view/plan_view.md) - [GeoFence](qgc-user-guide/plan_view/plan_geofence.md) - [Rally Points](qgc-user-guide/plan_view/plan_rally_points.md) - [Pattern](qgc-user-guide/plan_view/pattern.md) @@ -19,7 +29,7 @@ - [Fixed Wing Landing Pattern](qgc-user-guide/plan_view/pattern_fixed_wing_landing.md) - [Pattern Presets](qgc-user-guide/plan_view/pattern_presets.md) -- [Vehicle Setup](qgc-user-guide/setup_view/setup_view.md) +- [Vehicle Configuration](qgc-user-guide/setup_view/setup_view.md) - [Firmware](qgc-user-guide/setup_view/firmware.md) - [Airframe](qgc-user-guide/setup_view/airframe.md) - [Airframe (ArduPilot)](qgc-user-guide/setup_view/airframe_ardupilot.md) @@ -61,15 +71,13 @@ - [Releases](qgc-user-guide/releases/index.md) - [Release Notes](qgc-user-guide/releases/release_notes.md) - - [v4.0 (Additional Notes)](qgc-user-guide/releases/stable_v4.0_additional.md) - - [v3.3 (Detailed)](qgc-user-guide/releases/stable_v3.3_long.md) - - [v3.2 (Detailed)](qgc-user-guide/releases/stable_v3.2_long.md) + - [QGC v4 Release Notes](qgc-user-guide/releases/release_note_stable_v4.md) + - [QGC v3 Release Notes](qgc-user-guide/releases/release_note_stable_v3.md) - [Daily Builds](qgc-user-guide/releases/daily_builds.md) - [Daily Build New Features](qgc-user-guide/releases/daily_build_new_features.md) - [Privacy Policy](qgc-user-guide/releases/privacy_policy.md) - [Troubleshooting](qgc-user-guide/troubleshooting/index.md) - - [Setup Problems](qgc-user-guide/troubleshooting/qgc_setup.md) - [Usage Problems](qgc-user-guide/troubleshooting/qgc_usage.md) - [Connection problems](qgc-user-guide/troubleshooting/vehicle_connection.md) @@ -80,11 +88,11 @@ - [Developer's Guide](qgc-dev-guide/index.md) - [Getting Started with source & builds](qgc-dev-guide/getting_started/index.md) - [Build using Containers](qgc-dev-guide/getting_started/container.md) - - [Using QGC on CentOS](qgc-dev-guide/getting_started/cent_os.md) + - [Navigating the Source Code](qgc-dev-guide/navigating_source.md) + - [Class Hierarchy](qgc-dev-guide/classes/index.md) - [QGC Release/Branching Process](qgc-dev-guide/release_branching_process.md) - [Communication Flow](qgc-dev-guide/communication_flow.md) - [Plugin Architecture](qgc-dev-guide/firmware_plugin.md) - - [Class Hierarchy](qgc-dev-guide/classes/index.md) - [User Interface Design](qgc-dev-guide/user_interface_design/index.md) - [Multi-Device Design Pattern](qgc-dev-guide/user_interface_design/multi_device_pattern.md) - [Font and Colour Palette](qgc-dev-guide/user_interface_design/font_palette.md) @@ -114,7 +122,6 @@ - [Release/Branching Process For Custom Builds](qgc-dev-guide/custom_build/release_branching_process.md) - [MAVLink](qgc-dev-guide/custom_build/mavlink.md) - [Code Submission](qgc-dev-guide/contribute/index.md) - - [Developer Call](qgc-dev-guide/contribute/dev_call.md) - [Coding Style](qgc-dev-guide/contribute/coding_style.md) - [Unit Tests](qgc-dev-guide/contribute/unit_tests.md) - [Pull Requests](qgc-dev-guide/contribute/pull_requests.md) diff --git a/docs/tr/index.md b/docs/tr/index.md index 570138d3ecf..3da41afd4c9 100644 --- a/docs/tr/index.md +++ b/docs/tr/index.md @@ -1,7 +1,7 @@ --- layout: home hero: - name: QGroundControl Guide + name: QGroundControl Guide (Daily Build 5.0) tagline: For beginners, experienced users, and developers actions: - theme: brand diff --git a/docs/tr/qgc-dev-guide/command_line_options.md b/docs/tr/qgc-dev-guide/command_line_options.md index 42e7e20dd94..edfabb64b20 100644 --- a/docs/tr/qgc-dev-guide/command_line_options.md +++ b/docs/tr/qgc-dev-guide/command_line_options.md @@ -30,16 +30,16 @@ Linux Terminal: The options/command line arguments are listed in the table below. -| Option | Description | -| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| `--clear-settings` | Clears the app settings (reverts _QGroundControl_ back to default settings). | -| `--logging:full` | Turns on full logging. See [Console Logging](../../qgc-user-guide/settings_view/console_logging.html#logging-from-the-command-line). | -| `--logging:full,LinkManagerVerboseLog,ParameterLoaderLog` | Turns on full logging and turns off the following listed comma-separated logging options. | -| `--logging:LinkManagerLog,ParameterLoaderLog` | Turns on the specified comma separated logging options | -| `--unittest:name` | (Debug builds only) Runs the specified unit test. Leave off `:name` to run all tests. | -| `--unittest-stress:name` | (Debug builds only) Runs the specified unit test 20 times in a row. Leave off :name to run all tests. | -| `--fake-mobile` | Simulates running on a mobile device. | -| `--test-high-dpi` | Simulates running _QGroundControl_ on a high DPI device. | +| Option | Description | +| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `--clear-settings` | Clears the app settings (reverts _QGroundControl_ back to default settings). | +| `--logging:full` | Turns on full logging. See [Console Logging](../../qgc-user-guide/settings_view/console_logging.html#logging-from-the-command-line). | +| `--logging:full,LinkManagerVerboseLog,ParameterLoaderLog` | Turns on full logging and turns off the following listed comma-separated logging options. | +| `--logging:LinkManagerLog,ParameterLoaderLog` | Turns on the specified comma separated logging options | +| `--unittest:name` | (Debug builds only) Runs the specified unit test. Leave off `:name` to run all tests. | +| `--unittest-stress:name` | (Debug builds only) Runs the specified unit test 20 times in a row. Leave off :name to run all tests. | +| `--fake-mobile` | Simulates running on a mobile device. | +| `--test-high-dpi` | Simulates running _QGroundControl_ on a high DPI device. | Notes: diff --git a/docs/tr/qgc-dev-guide/custom_build/mavlink.md b/docs/tr/qgc-dev-guide/custom_build/mavlink.md index 6423c43a4bb..24883618f8e 100644 --- a/docs/tr/qgc-dev-guide/custom_build/mavlink.md +++ b/docs/tr/qgc-dev-guide/custom_build/mavlink.md @@ -10,6 +10,6 @@ In order to add support for a new set of messages you should add them to [develo To modify the version of MAVLink used by QGC: - Replace the pre-build C library at [/qgroundcontrol/libs/mavlink/include/mavlink](https://github.com/mavlink/qgroundcontrol/tree/master/libs/mavlink/include/mavlink). - - By default this is a submodule importing https\://github.com/mavlink/c_library_v2 + - By default this is a submodule importing https://github.com/mavlink/c_library_v2 - You can change the submodule, or [build your own libraries](https://mavlink.io/en/getting_started/generate_libraries.html) using the MAVLink toolchain. - You can change the whole dialect used by setting it in [`MAVLINK_CONF`](https://github.com/mavlink/qgroundcontrol/blob/master/QGCExternalLibs.pri#L52) when running _qmake_. diff --git a/docs/tr/qgc-dev-guide/custom_build/release_branching_process.md b/docs/tr/qgc-dev-guide/custom_build/release_branching_process.md index 44890d6b03a..9023e149488 100644 --- a/docs/tr/qgc-dev-guide/custom_build/release_branching_process.md +++ b/docs/tr/qgc-dev-guide/custom_build/release_branching_process.md @@ -8,7 +8,7 @@ The best place to start is understanding the mechanism QGC uses to do it's own r ## Custom build/release types -Regular QGC has two main build types: Stable and Daily. The build type for a custom build is more complex. Throughout this discussion we will use the term "upstream" to refer to the main QGC repo (https\://github.com/mavlink/qgroundcontrol). Also when we talk about a "new" upstream stable release, this means a major/minor release, not a patch release. +Regular QGC has two main build types: Stable and Daily. The build type for a custom build is more complex. Throughout this discussion we will use the term "upstream" to refer to the main QGC repo (https://github.com/mavlink/qgroundcontrol). Also when we talk about a "new" upstream stable release, this means a major/minor release, not a patch release. ### Synchronized Stable diff --git a/docs/tr/qgc-dev-guide/custom_build/resource_override.md b/docs/tr/qgc-dev-guide/custom_build/resource_override.md index 2c8fa94eba1..37a3fdd7d01 100644 --- a/docs/tr/qgc-dev-guide/custom_build/resource_override.md +++ b/docs/tr/qgc-dev-guide/custom_build/resource_override.md @@ -1,8 +1,12 @@ # Resource Overrides -A "resource" in QGC source code terminology is anything found in the [qgroundcontrol.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgroundcontrol.qrc) and [qgcresources.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgcresources.qrc) file. By overriding a resource you can replace it with your own version of it. This could be as simple as a single icon, or as complex as replacing an entire Vehicle Setup page of qml ui code. +A "resource" in QGC source code terminology is anything found in Qt resources file: -Be aware that using resource overrides does not isolate you from upstream QGC changes like the plugin architecture does. In a sense you are directly modify the upstream QGC resources used by the main code. +- [qgroundcontrol.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgroundcontrol.qrc) and +- [qgcresources.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgcresources.qrc) file. +- [InstrumentValueIcons.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/resources/InstrumenValueIcons/InstrumentValueIcons.qrc) + +By overriding a resource you can replace it with your own version of it. This could be as simple as a single icon, or as complex as replacing an entire Vehicle Setup page of qml ui code. Be aware that using resource overrides does not isolate you from upstream QGC changes like the plugin architecture does. In a sense you are directly modify the upstream QGC resources used by the main code. ## Exclusion Files @@ -14,7 +18,7 @@ You must include the custom version of the overriden resouce in you custom build ## Generating the new modified versions of standard QGC resource file -This is done using the `updateqrc.py` python script. It will read the upstream `qgroundcontrol.qrc` and `qgcresources.qrc` file and the corresponding exclusion files and output new versions of these files in your custom directory. These new versions will not have the resources you specified to exclude in them. The build system for custom builds uses these generated files (if they exist) to build with instead of the upstream versions. The generated version of these file should be added to your repo. Also whenever you update the upstream portion of QGC in your custom repo you must re-run `python updateqrc.py` to generate new version of the files since the upstream resources may have changed. +This is done using the resource update python scripts:`python updateqrc.py` and `python updateinstrumentqrc.py`. It will read the upstream resouce files and the corresponding exclusion files and output new versions of these files in your custom directory. These new versions will not have the resources you specified to exclude in them. The build system for custom builds uses these generated files (if they exist) to build with instead of the upstream versions. The generated version of these file should be added to your repo. Also whenever you update the upstream portion of QGC in your custom repo you must re-run the scripts to generate new versions of the files since the upstream resources may have changed. ## Custom Build Example diff --git a/docs/tr/qgc-dev-guide/file_formats/plan.md b/docs/tr/qgc-dev-guide/file_formats/plan.md index 20babe1a5c7..41ea7195356 100644 --- a/docs/tr/qgc-dev-guide/file_formats/plan.md +++ b/docs/tr/qgc-dev-guide/file_formats/plan.md @@ -30,11 +30,11 @@ The main fields are: | Key | Description | | ------------------------------ | ------------------------------------------------------------------------------------------------- | -| `version` | The version for this file. Current version is 1. | -| `fileType` | Must be `"Plan"`. | +| `version` | The version for this file. Current version is 1. | +| `fileType` | Must be `"Plan"`. | | `groundStation` | The name of the ground station which created this file (here _QGroundControl_) | -| [`mission`](#mission) | The mission associated with this flight plan. | -| [`geoFence`](#geofence) | (Optional) Geofence information for this plan. | +| [`mission`](#mission) | The mission associated with this flight plan. | +| [`geoFence`](#geofence) | (Optional) Geofence information for this plan. | | [`rallyPoints`](#rally_points) | (Optional) Rally/Safe point information for this plan | ## Mission Object {#mission} @@ -82,15 +82,15 @@ The list may be a mix of both [SimpleItem](#mission_simple_item) and [ComplexIte The following values are required: -| Key | Description | -| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `version` | The version for the mission object. Current version is 2. | -| `firmwareType` | The firmware type for which this mission was created. This is one of the [MAV_AUTOPILOT](https://mavlink.io/en/messages/common.html#MAV_AUTOPILOT) enum values. | -| `globalPlanAltitudeMode` | The global plan-wide altitude mode setting. This is used by plan items that don't specify an `"AltitudeMode"`. | -| `vehicleType` | The vehicle type for which this mission was created. This is one of the [MAV_TYPE](https://mavlink.io/en/messages/common.html#MAV_TYPE) enum values. | +| Key | Description | +| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `version` | The version for the mission object. Current version is 2. | +| `firmwareType` | The firmware type for which this mission was created. This is one of the [MAV_AUTOPILOT](https://mavlink.io/en/messages/common.html#MAV_AUTOPILOT) enum values. | +| `globalPlanAltitudeMode` | The global plan-wide altitude mode setting. This is used by plan items that don't specify an `"AltitudeMode"`. | +| `vehicleType` | The vehicle type for which this mission was created. This is one of the [MAV_TYPE](https://mavlink.io/en/messages/common.html#MAV_TYPE) enum values. | | `cruiseSpeed` | The default forward speed for Fixed wing or VTOL vehicles (i.e. when moving between waypoints). | -| `hoverSpeed` | The default forward speed for multi-rotor vehicles. | -| `items` | The list of mission item objects associated with the mission . The list may contain either/both [SimpleItem](#mission_simple_item) and [ComplexItem](#mission_complex_item) objects. | +| `hoverSpeed` | The default forward speed for multi-rotor vehicles. | +| `items` | The list of mission item objects associated with the mission . The list may contain either/both [SimpleItem](#mission_simple_item) and [ComplexItem](#mission_complex_item) objects. | | `plannedHomePosition` | The planned home position is shown on the map and used for mission planning when no vehicle is connected. The array values shown above are (from top): latitude, longitude and AMSL altitude. | The format of the simple and complex items is given below. @@ -123,16 +123,16 @@ A simple item represents a single MAVLink [MISSION_ITEM](https://mavlink.io/en/m The field mapping is shown below. -| Key | Description | -| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `type` | `SimpleItem` for a simple item | -| `AMSLAltAboveTerrain` | Altitude value shown to the user. | -| `Altitude` | | -| `AltitudeMode` | | -| `autoContinue` | [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).autoContinue | +| Key | Description | +| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type` | `SimpleItem` for a simple item | +| `AMSLAltAboveTerrain` | Altitude value shown to the user. | +| `Altitude` | | +| `AltitudeMode` | | +| `autoContinue` | [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).autoContinue | | `command` | The command ([MAV_CMD](https://mavlink.io/en/messages/common.html#MAV_CMD)) for this mission item - see [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).command. | | `doJumpId` | The target id for the current mission item in DO_JUMP commands. These are auto-numbered from 1. | -| `frame` | [MAV_FRAME](https://mavlink.io/en/messages/common.html#MAV_FRAME) (see [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).frame) | +| `frame` | [MAV_FRAME](https://mavlink.io/en/messages/common.html#MAV_FRAME) (see [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).frame) | | `params` | [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).param1,2,3,4,x,y,z (values depends on the particular [MAV_CMD](https://mavlink.io/en/messages/common.html#MAV_CMD)). | ### Complex Mission Item {#mission_complex_item} @@ -176,14 +176,14 @@ The object definition for a `Survey` complex mission item is given below. Complex items have these values associated with them: -| Key | Description | -| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Key | Description | +| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `version` | The version number for this `survey` definition. Current version is 3. | -| `type` | `ComplexItem` (this is a complex item). | -| `complexItemType` | `survey` | -| [`TransectStyleComplexItem`](#TransectStyleComplexItem) | The common base definition for Survey and CorridorScan complex items. | -| `angle` | The angle for the transect paths (degrees). | -| `entryLocation` | ? | +| `type` | `ComplexItem` (this is a complex item). | +| `complexItemType` | `survey` | +| [`TransectStyleComplexItem`](#TransectStyleComplexItem) | The common base definition for Survey and CorridorScan complex items. | +| `angle` | The angle for the transect paths (degrees). | +| `entryLocation` | ? | | `flyAlternateTransects` | If true, the vehicle will skip every other transect and then come back at the end and fly these alternates. This can be used for fixed wing aircraft when the turnaround would be too acute for the vehicle to make the turn. | | `polygon` | The polygon array which represents the polygonal survey area. Each point is a latitude, longitude pair for a polygon vertex. | @@ -216,15 +216,15 @@ The object definition for a `CorridorScan` complex mission item is given below. }, ``` -| Key | Description | -| ------------------------------------------------------- | --------------------------------------------------------------------- | +| Key | Description | +| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | | `version` | The version for this `CorridorScan` definition. Current version is 3. | -| `type` | `ComplexItem` (this is a complex item). | -| `complexItemType` | `CorridorScan` | -| `CorridorWidth` | ? | -| `EntryPoint` | ? | -| [`TransectStyleComplexItem`](#TransectStyleComplexItem) | The common base definition for Survey and CorridorScan complex items. | -| `polyline` | ? | +| `type` | `ComplexItem` (this is a complex item). | +| `complexItemType` | `CorridorScan` | +| `CorridorWidth` | ? | +| `EntryPoint` | ? | +| [`TransectStyleComplexItem`](#TransectStyleComplexItem) | The common base definition for Survey and CorridorScan complex items. | +| `polyline` | ? | #### Structure Scan {#structure_scan} @@ -261,17 +261,17 @@ The object definition for a `StructureScan` complex mission item is given below. } ``` -| Key | Description | -| --------------------------- | ---------------------------------------------------------------------- | -| `version` | The version for this `StructureScan` definition. Current version is 2. | -| `type` | `ComplexItem` (this is a complex item). | -| `complexItemType` | `StructureScan` | -| `Altitude` | ? | -| [`CameraCalc`](#CameraCalc) | ? | -| `Layers` | ? | -| `StructureHeight` | ? | -| `altitudeRelative` | `true`: `altitude` is relative to home, `false`: `altitude` is AMSL. | -| `polygon` | ? | +| Key | Description | +| --------------------------- | -------------------------------------------------------------------------------------------------------------------- | +| `version` | The version for this `StructureScan` definition. Current version is 2. | +| `type` | `ComplexItem` (this is a complex item). | +| `complexItemType` | `StructureScan` | +| `Altitude` | ? | +| [`CameraCalc`](#CameraCalc) | ? | +| `Layers` | ? | +| `StructureHeight` | ? | +| `altitudeRelative` | `true`: `altitude` is relative to home, `false`: `altitude` is AMSL. | +| `polygon` | ? | #### `TransectStyleComplexItem` {#TransectStyleComplexItem} @@ -305,17 +305,17 @@ The object definition for a `StructureScan` complex mission item is given below. }, ``` -| Key | Description | -| --------------------------- | --------------------------------------------------------------------------------- | +| Key | Description | +| --------------------------- | ----------------------------------------------------------------------------------------------------------------- | | `version` | The version for this `TransectStyleComplexItem` definition. Current version is 1. | -| [`CameraCalc`](#CameraCalc) | ? | -| `CameraTriggerInTurnAround` | ? (boolean) | -| `FollowTerrain` | ? (boolean) | -| `HoverAndCapture` | ? (boolean) | -| `Items` | ? | -| `Refly90Degrees` | ? (boolean) | -| `TurnAroundDistance` | The distance to fly past the polygon edge prior to turning for the next transect. | -| `VisualTransectPoints` | ? | +| [`CameraCalc`](#CameraCalc) | ? | +| `CameraTriggerInTurnAround` | ? (boolean) | +| `FollowTerrain` | ? (boolean) | +| `HoverAndCapture` | ? (boolean) | +| `Items` | ? | +| `Refly90Degrees` | ? (boolean) | +| `TurnAroundDistance` | The distance to fly past the polygon edge prior to turning for the next transect. | +| `VisualTransectPoints` | ? | ##### CameraCalc {#CameraCalc} @@ -344,26 +344,26 @@ The `CameraCalc` contains camera information used for a survey, corridor or stru }, ``` -| Key | Description | -| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `version` | The version for this `CameraCalc` definition. Current version is 1. | -| `AdjustedFootprintFrontal` | ? | -| `AdjustedFootprintSide` | ? | -| `DistanceToSurface` | ? Units? | -| `DistanceToSurfaceRelative` | ? | +| Key | Description | +| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `version` | The version for this `CameraCalc` definition. Current version is 1. | +| `AdjustedFootprintFrontal` | ? | +| `AdjustedFootprintSide` | ? | +| `DistanceToSurface` | ? Units? | +| `DistanceToSurfaceRelative` | ? | | `CameraName` | Name of camera being used (must correspond to one of the cameras known to _QGroundControl_ or: `Manual (no camera specs)` for manual setup, `Custom Camera` for a custom setup. The keys listed after this point are not specified for a "Manual" camera definition. | -| `FixedOrientation` | ? (boolean) | -| `FocalLength` | Focal length of camera lens in millimeters. | -| `FrontalOverlap` | Percentage of frontal image overlap. | -| `ImageDensity` | ? | -| `ImageHeight` | Image height in px | -| `ImageWidth` | Image width in px | +| `FixedOrientation` | ? (boolean) | +| `FocalLength` | Focal length of camera lens in millimeters. | +| `FrontalOverlap` | Percentage of frontal image overlap. | +| `ImageDensity` | ? | +| `ImageHeight` | Image height in px | +| `ImageWidth` | Image width in px | | `Landscape` | `true`: Camera installed in landscape orientation on vehicle, `false`: Camera installed in portrait orientation on vehicle. | -| `MinTriggerInterval` | ? | -| `SensorHeight` | Sensor height in millimeters. | -| `SensorWidth` | Sensor width in millimeters. | -| `SideOverlap` | Percentage of side image overlap. | -| `ValueSetIsDistance` | ? (boolean) | +| `MinTriggerInterval` | ? | +| `SensorHeight` | Sensor height in millimeters. | +| `SensorWidth` | Sensor width in millimeters. | +| `SideOverlap` | Percentage of side image overlap. | +| `ValueSetIsDistance` | ? (boolean) | ## GeoFence {#geofence} @@ -384,11 +384,11 @@ The minimal definition is shown below. The fields are: -| Key | Description | -| ------------------------------- | ---------------------------------------------------------------------------------- | -| `version` | The version number for the geofence plan format. The documented version is 2. | -| [`circles`](#circle_geofence) | List containing circle geofence definitions (comma separated). | -| [`polygons`](#polygon_geofence) | List containing polygon geofence definitions (comma separated). | +| Key | Description | +| ------------------------------- | ------------------------------------------------------------------------------------------------------------- | +| `version` | The version number for the geofence plan format. The documented version is 2. | +| [`circles`](#circle_geofence) | List containing circle geofence definitions (comma separated). | +| [`polygons`](#polygon_geofence) | List containing polygon geofence definitions (comma separated). | ### Circle Geofence {#circle_geofence} @@ -408,11 +408,11 @@ The items define the centre and radius of the circle, and whether or not the spe The fields are: -| Key | Description | -| ----------- | --------------------------------------------------------------------------------------------------------------------- | +| Key | Description | +| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | `version` | The version number for the geofence "circle" plan format. The documented version is 1. | | `circle` | The definition of the circle. Includes `centre` (latitude, longitude) and `radisu` as shown above. | -| `inclusion` | Whether or not the geofence is enabled (true) or disabled. | +| `inclusion` | Whether or not the geofence is enabled (true) or disabled. | ### Polygon Geofence {#polygon_geofence} @@ -449,11 +449,11 @@ The geofence includes a set of points defined with a clockwise winding (i.e. the The fields are: -| Key | Description | -| ----------- | ------------------------------------------------------------------------------------------------------------------------------ | -| `version` | The version number for the geofence "polygon" plan format. The documented version is 2. | +| Key | Description | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `version` | The version number for the geofence "polygon" plan format. The documented version is 2. | | `polygon` | A list of points for the polygon. Each point contains a latitude and longitude. The points are ordered in a clockwise winding. | -| `inclusion` | Whether or not the geofence is enabled (true) or disabled. | +| `inclusion` | Whether or not the geofence is enabled (true) or disabled. | ## Rally Points {#rally_points} @@ -483,7 +483,7 @@ A definition with two points is shown below. The fields are: -| Key | Description | -| --------- | -------------------------------------------------------------------------------- | +| Key | Description | +| --------- | ---------------------------------------------------------------------------------------------------------------- | | `version` | The version number for the rally point plan format. The documented version is 2. | -| `points` | A list of rally points. | +| `points` | A list of rally points. | diff --git a/docs/tr/qgc-dev-guide/getting_started/container.md b/docs/tr/qgc-dev-guide/getting_started/container.md index 3bdda672439..5baae13faa7 100644 --- a/docs/tr/qgc-dev-guide/getting_started/container.md +++ b/docs/tr/qgc-dev-guide/getting_started/container.md @@ -12,11 +12,21 @@ The main advantage of using the container is the usage of the `CMake` build syst ## Building the Container -Before using the container, you have to build the image. +### Script + +To build the container using the script, run this command in the qgc root directory + +``` +./deploy/docker/run-docker-ubuntu.sh +``` + +### Manual + +if you want to Build using the container manually, then you first have to build the image. You can accomplish this using docker, running the following script from the root of the QGC source code directory. ``` -docker build --file ./deploy/docker/Dockerfile-build-linux -t qgc-linux-docker . +docker build --file ./deploy/docker/Dockerfile-build-ubuntu -t qgc-ubuntu-docker . ``` :::info @@ -28,7 +38,7 @@ Keep in mind this is tagging the image for later reference since you can have mu If building on a Mac computer with an M1 chip you must also specify the build option `--platform linux/x86_64` as shown: ``` -docker build --platform linux/x86_64 --file ./deploy/docker/Dockerfile-build-linux -t qgc-linux-docker . +docker build --platform linux/x86_64 --file ./deploy/docker/Dockerfile-build-ubuntu -t qgc-ubuntu-docker . ``` Otherwise you will get a build error like: @@ -46,15 +56,20 @@ We recommend you create a `build` directory on the source tree and then run the ``` mkdir build -docker run --rm -v ${PWD}:/project/source -v ${PWD}/build:/project/build qgc-linux-docker +docker run --rm -v ${PWD}:/project/source -v ${PWD}/build:/project/build qgc-ubuntu-docker ``` +::: info +For up to date docker command and options reference relevant run-script in `deploy/docker`, for example [run-docker-ubuntu.sh](https://github.com/mavlink/qgroundcontrol/blob/master/deploy/docker/run-docker-ubuntu.sh#L16). + +::: + ::: info If using the script to build the Linux image on a Windows host, you would need to reference the PWD differently. On Windows the docker command is: ``` -docker run --rm -v %cd%:/project/source -v %cd%/build:/project/build qgc-linux-docker +docker run --rm -v %cd%:/project/source -v %cd%/build:/project/build qgc-ubuntu-docker ``` ::: diff --git a/docs/tr/qgc-dev-guide/getting_started/index.md b/docs/tr/qgc-dev-guide/getting_started/index.md index a8df17fe625..a23d2f39bc4 100644 --- a/docs/tr/qgc-dev-guide/getting_started/index.md +++ b/docs/tr/qgc-dev-guide/getting_started/index.md @@ -1,5 +1,5 @@ --- -qt_version: 6.6.1 +qt_version: 6.8.2 --- # Getting Started with Source and Builds @@ -14,7 +14,7 @@ Versions are provided for all platforms. ## Source Code -Source code for _QGroundControl_ is kept on GitHub here: https\://github.com/mavlink/qgroundcontrol. +Source code for _QGroundControl_ is kept on GitHub here: https://github.com/mavlink/qgroundcontrol. It is [dual-licensed under Apache 2.0 and GPLv3](https://github.com/mavlink/qgroundcontrol/blob/master/.github/COPYING.md). To get the source files: @@ -59,10 +59,6 @@ There is a significant risk that other Qt versions will inject bugs that affect For more information see: [Qt 6 supported platform list](https://doc.qt.io/qt-6/supported-platforms.html). -:::info -Native [CentOS Builds](../getting_started/cent_os.md) are also supported, but are documented separately (as the tested environment is different). -::: - #### Install Qt You **must install Qt as described below** instead of using pre-built packages from say, a Linux distribution. @@ -72,83 +68,64 @@ To install Qt: 1. Download and run the [Qt Online Installer](https://www.qt.io/download-qt-installer-oss) - **Ubuntu:** - Set the downloaded file to executable using: `chmod +x`. - - You may also need to install libxcb-cursor. - -2. In the installer _Select Components_ dialog choose: Qt {{ $frontmatter.qt_version }}. - - Then install the following components: - - - Under _Qt _{{ $frontmatter.qt_version }}_ select: - - Depending on the OS you want to build for: - - **Windows**: _MSVC 2019 64 bit_ - - **MacOS**: _macOS_ - - **Linux**: _Desktop gcc 64-bit_ - - **Android**: _Android_ - - _Qt 5 Compatibility Module_ - - _Qt Shader Tools_ - - Under _Additional Libraries_ select: - - _Qt Charts_ - - _Qt Connectivity_ - - _Qt Location (TP)_ - - _Qt Multimedia_ - - _Qt Positioning_ - - _Qt Serial Port_ - - _Qt Speech_ - -3. Install Additional Packages (Platform Specific) - - - **Ubuntu:** `sudo apt-get install speech-dispatcher libudev-dev libsdl2-dev patchelf build-essential` + - You may also need to install libxcb-cursor0 + +2. On the _Installation Folder_ page select "Custom Installation" + +3. On the _Select Components_ page: + + - I you don't see _Qt {{ $frontmatter.qt_version }}_ listed check the _Archive_ checkbox and click _Filter_. + +- Under Qt -> _Qt {{ $frontmatter.qt_version }}_ select: + - **Windows**: MSVC 2022 _arch_ - where _arch_ is the architecture of your machine + - **Mac**: Desktop + - **Linux**: Desktop gcc 64-bit + - **Android**: Android +- Select all _Additional Libraries_ +- Deselect QT Design Studio + +1. Install Additional Packages (Platform Specific) + + - **Ubuntu:** `sudo bash ./qgroundcontrol/tools/setup/install-dependencies-debian.sh` - **Fedora:** `sudo dnf install speech-dispatcher SDL2-devel SDL2 systemd-devel patchelf` - **Arch Linux:** `pacman -Sy speech-dispatcher patchelf` - - **OSX** [Setup](https://doc.qt.io/qt-6/macos.html) - - **Android** [Setup](https://doc.qt.io/qt-6/android-getting-started.html) + - **Mac** `sh qgroundcontrol/tools/setup/macos-dependencies.sh` + - **Android** [Setup](https://doc.qt.io/qt-6/android-getting-started.html). JDK17 is required for the latest updated versions. NDK Version: 25.1.8937393 + You can confirm it is being used by reviewing the project setting: **Projects > Manage Kits > Devices > Android (tab) > Android Settings > _JDK location_**. + Note: Visit here for more detailed configurations [android.yml](.github/workflows/android.yml) -4. Install Optional/OS-Specific Functionality +2. Install Optional/OS-Specific Functionality ::: info Optional features that are dependent on the operating system and user-installed libraries are linked/described below. These features can be forcibly enabled/disabled by specifying additional values to qmake. ::: - - **Video Streaming/Gstreamer:** - see [Video Streaming](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoReceiver/README.md). + - **Video Streaming/Gstreamer:** - see [Video Streaming](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoManager/VideoReceiver/GStreamer/README.md) -#### Building using Qt Creator {#qt-creator} +#### Install Visual Studio (Windows Only) {#vs} -1. Launch _Qt Creator_ and open the **qgroundcontrol.pro** project. +Install [Visual Studio 2022 Community Edition](https://visualstudio.microsoft.com/downloads/). -2. In the **Projects** section, select the appropriate kit for your needs: +When installing, select _Desktop development with C++_ as shown: - - **OSX:** Desktop Qt {{ $frontmatter.qt_version }} clang 64 bit +![Visual Studio 2019 - Select Desktop Environment with C++](../../../assets/dev_getting_started/visual_studio_select_features.png) - ::: info - iOS builds must be built using [XCode](http://doc.qt.io/qt-5/ios-support.html). - ::: +:::info +Visual Studio is ONLY used to get the compiler. Building _QGroundControl_ is done using [Qt Creator](#qt-creator) or [cmake](#cmake) directly as outlined below. +::: - - **Ubuntu:** Desktop Qt {{ $frontmatter.qt_version }} GCC 64bit +#### Building using Qt Creator {#qt-creator} - - **Windows:** Desktop Qt {{ $frontmatter.qt_version }} MSVC2019 **64bit** +1. Launch _Qt Creator_, select Open Project and select the **CMakeLists.txt** file. - - **Android:** Android for armeabi-v7a (GCC 4.9, Qt {{ $frontmatter.qt_version }}) - - JDK11 is required. - You can confirm it is being used by reviewing the project setting: **Projects > Manage Kits > Devices > Android (tab) > Android Settings > _JDK location_**. +2. On the _Configure Project_ page it should default to the version of Qt you just installed using the instruction above. If not select that kit from the list and click _Configure Project_. -3. Build using the "hammer" (or "play") icons: +3. Build using the "hammer" (or "play") icons or the menus: ![QtCreator Build Button](../../../assets/dev_getting_started/qt_creator_build_qgc.png) -#### Install Visual Studio 2019 (Windows Only) {#vs} - -The Windows compiler can be found here: [Visual Studio 2019 compiler](https://visualstudio.microsoft.com/vs/older-downloads/) (64 bit) - -When installing, select _Desktop development with C++_ as shown: - -![Visual Studio 2019 - Select Desktop Environment with C++](../../../assets/dev_getting_started/visual_studio_select_features.png) - -:::info -Visual Studio is ONLY used to get the compiler. Actually building _QGroundControl_ should be done using [Qt Creator](#qt-creator) or [qmake](#qmake) as outlined below. -::: - -#### Build using qmake on CLI {#qmake} +#### Build using CMake on CLI {#cmake} Example commands to build a default QGC and run it afterwards: @@ -158,40 +135,22 @@ Example commands to build a default QGC and run it afterwards: cd qgroundcontrol ``` -2. Create and enter a shadow build directory: - - ```sh - mkdir build - cd build - ``` - -3. Configure the build using the qmake script in the root of the repository: - - ```sh - qmake ../ - ``` - -4. Run make to compile and link. - To accelerate the process things you can use the `-j{number of threads}` parameter. +2. Configure: ```sh - make -j12 + cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Debug ``` - ::: info - You can also specify build time flags here. - For example, you could disable airmap inclusion using the command: +3. Build ```sh - DEFINES+=DISABLE_AIRMAP make build + cmake --build build --config Debug ``` - ::: - -5. Run the QGroundcontrol binary that was just built: +4. Run the QGroundcontrol binary that was just built: ```sh - ./staging/QGroundControl + ./build/Debug/QGroundControl ``` ### Vagrant @@ -212,14 +171,6 @@ Example commands to build a default QGC and run it afterwards: You can additionally create installation file(s) for _QGroundControl_ as part of the normal build process. -:::tip -On Windows you will need to first install [NSIS](https://sourceforge.net/projects/nsis/). -::: - -To add support for installation file creation you need to add `CONFIG+=installer` to your project file, or when you call _qmake_. - -To do this in _Qt Creator_: - -- Open **Projects > Build > Build Steps > qmake > Additional arguments**. -- Enter `CONFIG+=installer` as shown: - ![Installer](../../../assets/dev_getting_started/qt_project_installer.png) +```sh +cmake --install . --config Release +``` diff --git a/docs/tr/qgc-dev-guide/index.md b/docs/tr/qgc-dev-guide/index.md index 9be96cc1f60..51252011bc8 100644 --- a/docs/tr/qgc-dev-guide/index.md +++ b/docs/tr/qgc-dev-guide/index.md @@ -1,6 +1,7 @@ # QGroundControl Dev Guide -[![Releases](https://img.shields.io/github/release/mavlink/QGroundControl.svg)](https://github.com/mavlink/QGroundControl/releases) [![Discuss](https://img.shields.io/badge/discuss-dev-ff69b4.svg)](http://discuss.px4.io/c/qgroundcontrol/qgroundcontrol-developers) +[![Discuss](https://img.shields.io/badge/discuss-dev-ff69b4.svg)](http://discuss.px4.io/c/qgroundcontrol/qgroundcontrol-developers) +[![Discord](https://discordapp.com/api/guilds/1022170275984457759/widget.png?style=shield)](https://discord.com/channels/1022170275984457759/1022185820683255908) This developer guide is the best source for information if you want to build, modify or extend [QGroundControl](http://qgroundcontrol.com) (QGC). It shows how to obtain and build the source code, explains how QGC works, and provides guidelines for contributing code to the project. @@ -11,14 +12,14 @@ This part of the guide is for **developers**! :::warning This is an active work in progress - information should be correct, but may not be complete! -If you find that it is missing helpful information (or errors) please raise an issue. +If you find that it is missing helpful information (or errors) please raise an issue or better yet submit a pull request to the docs with updated information. ::: ## Design Philosophy QGC is designed to provide a single codebase that can run across multiple OS platforms as well as multiple device sizes and styles. -The QGC user interface is implemented using [Qt QML](http://doc.qt.io/qt-5/qtqml-index.html). QML provides for hardware acceleration which is a key feature on lower powered devices such as tablets or phones. QML also provides features which allows us to more easily create a single user interface which can adapt itself to differing screen sizes and resolution. +The QGC user interface is implemented using Qt Qml. Qml provides for hardware acceleration which is a key feature on lower powered devices such as tablets or phones. Qml also provides features which allows us to more easily create a single user interface which can adapt itself to differing screen sizes and resolution. The QGC UI targets itself more towards a tablet+touch style of UI than a desktop mouse-based UI. This make a single UI easier to create since tablet style UI also tends to work fine on desktop/laptops. @@ -35,10 +36,6 @@ We expect all contributors to adhere to the [QGroundControl code of conduct](htt This code aims to foster an open and welcoming environment. ::: -### Coordination Call - -The developer team meets bi-weekly to discuss the highest priority issues, project coordination, and discuss any Issues, PRs, or Questions from the Community. ([Developer Call Details](contribute/dev_call.md)) - ### Translations We use [Crowdin](https://crowdin.com) to make it easier to manage translation for both _QGroundControl_ and the documentation. @@ -61,8 +58,6 @@ For more information see: [Licenses](contribute/licences.md). ## Governance -The QGroundControl mission planner is hosted under the governance of the [Dronecode Project](https://www.dronecode.org/). - -Dronecode Logo Linux Foundation Logo +The QGroundControl ground station is hosted under the governance of the [Dronecode Project](https://www.dronecode.org/).
 
diff --git a/docs/tr/qgc-dev-guide/navigating_source.md b/docs/tr/qgc-dev-guide/navigating_source.md new file mode 100644 index 00000000000..b8a3657e034 --- /dev/null +++ b/docs/tr/qgc-dev-guide/navigating_source.md @@ -0,0 +1,20 @@ +# Navigating QGC Source Code + +QGC is a large code base. With that it can be daunting to find what your are looking for in the source. Below are listed some tips to help you find what you are looking for. + +## Start from the top of the UI + +The top level window Qml UI code is found in `MainRootWindow.qml`. You can start here and work your way down through the UI hierarchy till you find what you are looking for. + +In this qml file you'll find things like: + +- How the toolbar is created +- How the top level views are created: Fly, Plan, ... + +## Global Search + +The best way to find something is to find the UI which is closest to what you are looking for by doing text searches. + +### Example: Find the source for the GPS drop down in the toolbar + +In the dropdown you see the words "Vehicle GPS Status". Do a global search for those words. Make sure you are doing a case sensitive search. Also make sure you are matching whole words. It can also be helpful to exclude the `*.ts` translation files. Since they can lead to multiple results. If you do the search described here it will take you right to `GPSIndicatorPage.qml`. Some times a search may lead to many results in both qml and .cpp files. In this case limit the results to `*.qml` files. diff --git a/docs/tr/qgc-dev-guide/plan/mission_command_tree.md b/docs/tr/qgc-dev-guide/plan/mission_command_tree.md index 55441b4e3fc..80dddd367dd 100644 --- a/docs/tr/qgc-dev-guide/plan/mission_command_tree.md +++ b/docs/tr/qgc-dev-guide/plan/mission_command_tree.md @@ -83,7 +83,7 @@ Let's walk through an example hierarchy for `MAV_CMD_NAV_WAYPOINT`. Root informa ### Root - Vehicle Type Specific leaf node -The next level of the hiearchy is generic mavlink but vehicle specific. Json files are here: [MR](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoMultiRotor.json), [FW](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoFixedWing.json), [ROVER](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoRover.json), [Sub](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoSub.json), [VTOL](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoVTOL.json). And here are the overrides for (Fixed Wings)(https\://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoFixedWing.json#L7): +The next level of the hiearchy is generic mavlink but vehicle specific. Json files are here: [MR](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoMultiRotor.json), [FW](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoFixedWing.json), [ROVER](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoRover.json), [Sub](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoSub.json), [VTOL](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoVTOL.json). And here are the overrides for (Fixed Wings)(https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoFixedWing.json#L7): ``` { diff --git a/docs/tr/qgc-dev-guide/release_branching_process.md b/docs/tr/qgc-dev-guide/release_branching_process.md index da2a0671f6c..0b65a5d4cd8 100644 --- a/docs/tr/qgc-dev-guide/release_branching_process.md +++ b/docs/tr/qgc-dev-guide/release_branching_process.md @@ -74,7 +74,8 @@ A proposed strategy for branching on custom builds can be found [here](custom_bu 2. Create a tag on the HEAD of master name `dX.Y` where the minor version is one greater than the new Stable. For example if you are create a new Stable 4.2 version then the tag would be 'd4.3'. This tag is used to create the version numbers for Android daily builds. Example: `git tag -a d4.3.0 -m "QGroundControl Daily Android Version Base"`. 3. Create an annotated tag on the newly created Stable branch named `vX.Y.0` with the correct major/minor version number. Example: `git tag -a v4.2.0 -m "QGroundControl v4.2.0"`. Pushing this tag to the repo will start a build. 4. Once the build completes verify the builds are pushed up to S3 correctly and sanity check that they at least boot correctly. Location on S3 will be `https://qgroundcontrol.s3.us-west-2.amazonaws.com/latest/...`. -5. Update the `https://qgroundcontrol.s3.us-west-2.amazonaws.com/builds/latest/QGC.version.txt` text file to the latest Stable version. This will notify uses there is a new Stable available the next time they launch QGC. +5. Update the `https://qgroundcontrol.s3.us-west-2.amazonaws.com/latest/QGC.version.txt` text file to the latest Stable version. This will notify users that there is a new Stable available the next time they launch QGC. +6. Note that the cached cloudfront downloads will take up to 24h to refresh. If they need to update earlier, the caches would need to be manually invalidated. ### Patch Version diff --git a/docs/tr/qgc-dev-guide/user_interface_design/controls.md b/docs/tr/qgc-dev-guide/user_interface_design/controls.md index 16bbca6fbed..c7e0840916c 100644 --- a/docs/tr/qgc-dev-guide/user_interface_design/controls.md +++ b/docs/tr/qgc-dev-guide/user_interface_design/controls.md @@ -33,3 +33,4 @@ These custom controls are exclusive to QGC and are used to create standard UI el - QGCViewPanel - The main view contents inside of a QGCView. - RoundButton - A round button control which uses an image as its inner contents. - SetupPage - The base control for all Setup vehicle component pages. Provides a title, description and component page contents area. +- SelectableControl - Allows users to select from a list of controls to display. Right-click on Desktop or Press and Hold on Mobile will show selection UI. Example usage: Allows user to select between multiple Instrument display variants. diff --git a/docs/tr/qgc-dev-guide/views/fly.md b/docs/tr/qgc-dev-guide/views/fly.md index a9f5a8e6c7c..15e0379a69c 100644 --- a/docs/tr/qgc-dev-guide/views/fly.md +++ b/docs/tr/qgc-dev-guide/views/fly.md @@ -1,6 +1,6 @@ # Fly View -- Top level QML code is in **FlightDisplayView\.qml** +- Top level QML code is in **FlightDisplayView.qml** - QML code communicates with `MissionController` (C++) for mission display - Instrument widgets communicate with active Vehicle object - Two main inner views are: diff --git a/docs/tr/qgc-dev-guide/views/setup.md b/docs/tr/qgc-dev-guide/views/setup.md index 0dd51a0b157..2b011fa12d6 100644 --- a/docs/tr/qgc-dev-guide/views/setup.md +++ b/docs/tr/qgc-dev-guide/views/setup.md @@ -1,5 +1,5 @@ # Setup View -- Top level QML code implemented in **SetupView\.qml** +- Top level QML code implemented in **SetupView.qml** - Fixed set of buttons/pages: Summary, Firmware - Remainder of buttons/pages come from AutoPilotPlugin VehicleComponent list diff --git a/docs/tr/qgc-user-guide/custom_actions/custom_actions.md b/docs/tr/qgc-user-guide/custom_actions/custom_actions.md new file mode 100644 index 00000000000..82a56ac8f2c --- /dev/null +++ b/docs/tr/qgc-user-guide/custom_actions/custom_actions.md @@ -0,0 +1,44 @@ +# Custom Mavlink Action + +Both the Fly View and Joysticks support the ability execute arbitrary mavlink commands to the active vehicle. In the Fly View these will show up in the Toolstrip Action list. With Joysticks you can assign then to button presses. + +## Mavlink Actions File + +The actions available are defined in a JSON file. The format of that file is as follows: + +``` +{ + "version": 1, + "fileType": "MavlinkActions", + "actions": [ + { + "label": "First Mavlink Command", + "description": "This is the first command", + "mavCmd": 10, + "compId": 100, + "param1": 1, + "param2": 2, + ... + }, + { + "label": "Second Mavlink Command", + "description": "This is the second command", + "mavCmd": 20, + ... + } + ] +} +``` + +Fields: + +- actions (required) - An array of json objects, one for each command +- label (required) - The user visible short description for the command. This is used as the button text for the Fly View - Actions command list. For Joysticks, this is the command you select from the dropdown. For Joysticks, make sure your name doesn't conflict with the built in names. +- description (required) - This is a longer description of the command used in the Fly View - Action list. This is not used by joysticks. +- mavCmd (required) - The command id of the mavlink command you want to send. +- compId (options) - The component id for where you want to send the command to. If not specified `MAV_COMP_ID_AUTOPILOT1` is used. +- param1 thru param7 (optional) - The parameters for the command. Parameters which are not specified will default to 0.0 + +Mavlink action files should be located in the MavlinkActions directory of the QGC save location. For example on Linux that would be `~/Documents/QGroundControl/MavlinkActions` or `~/Documents/QGroundControl Daily/MavlinkActions`. The Fly View and Joysticks can each have there own custom actions file. + +When you start up QGC it will load these files if they exist and make the commands available for use. diff --git a/docs/tr/qgc-user-guide/fly_view/camera_tools.md b/docs/tr/qgc-user-guide/fly_view/camera_tools.md new file mode 100644 index 00000000000..a1cd5980e3c --- /dev/null +++ b/docs/tr/qgc-user-guide/fly_view/camera_tools.md @@ -0,0 +1,29 @@ +# Camera Tools + +The camera tools are used to capture still images and video, and to configure the camera. + +![Camera Panel](../../../assets/fly/camera_panel/camera_mavlink.png) + +The camera capture and configuration options depend on the connected camera. +The configuration options are selected using the panel gear icon. +The configuration for a simple autopilot-connected camera are shown below. + +![Camera Panel - minimal settings](../../../assets/fly/camera_panel/camera_settings_minimal.png) + +When connected to camera that supports the [MAVLink Camera Protocol](https://mavlink.io/en/services/camera.html) you can additionally configure and use other camera services that it makes available. +For example, if your camera supports video mode you will be able to switch between still image capture and video mode, and start/stop recording. + +![Camera Panel - MAVLink settings](../../../assets/fly/camera_panel/camera_settings_mavlink.png) + +::: info +Most of the settings that are displayed depend on the camera (they are defined in its [MAVLink Camera Definition File](https://mavlink.io/en/services/camera_def.html)). + +> A few common settings at the end are hard-coded: Photo Mode (Single/Time Lapse), Photo Interval (if Time Lapse), Reset Camera Defaults (sends a reset command to the camera), Format (storage) +> ::: + +### Video Stream {#video_instrument_page} + +The video page is used to enable/disable video streaming. +When enabled, you can start/stop the video stream, enable a grid overlay, change how the image fits the screen, and record the video locally with QGC. + +![Instrument Page - Video Stream](../../../assets/fly/instrument_page_video_stream.jpg) diff --git a/docs/tr/qgc-user-guide/fly_view/fly_tools.md b/docs/tr/qgc-user-guide/fly_view/fly_tools.md new file mode 100644 index 00000000000..dff94728e21 --- /dev/null +++ b/docs/tr/qgc-user-guide/fly_view/fly_tools.md @@ -0,0 +1,60 @@ +# Fly Tools + +## Pre Flight Checklist {#preflight_checklist} + +An automated preflight checklist can be used to run through standard checks that the vehicle is configured correctly and it is safe to fly. + +To view the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../settings_view/general.md) and selecting the **Use preflight checklist** checkbox. +The tool will then be added to the _Flight Tools_. +Press it to open the checklist: + +![Pre Flight Checklist](../../../assets/fly/pre_flight_checklist.jpg) + +Once you have performed each test, select it on the UI to mark it as complete. + +## Takeoff {#takeoff} + +:::tip +If you are starting a mission for a multicopter, _QGroundControl_ will automatically perform the takeoff step. +::: + +To takeoff (when landed): + +1. Press the **Takeoff** button in the _Fly Tools_ (this will toggle to a **Land** button after taking off). +2. Optionally set the takeoff altitude in the right-side vertical slider. + +- You can slide up/down to change the altitude +- You can also click on the specified altitude (10 ft in example) and then type in a specific altitude. + +1. Confirm takeoff using the slider. + +![takeoff](../../../assets/fly/takeoff.png) + +## Land {#land} + +You can land at the current position at any time while flying: + +1. Press the **Land** button in the _Fly Tools_ (this will toggle to a **Takeoff** button when landed). +2. Confirm landing using the slider. + +## RTL/Return + +Return to a "safe point" at any time while flying: + +1. Press the **RTL** button in the _Fly Tools_. +2. Confirm RTL using the slider. + +:::info +Vehicles commonly return to the "home" (takeoff) location and land. +This behaviour depends on the vehicle type and configuration. +For example, rally points or mission landings may be used as alternative return targets. +::: + +## Change Altitude {#change_altitude} + +You can change altitude while flying, except when in a mission: + +1. Press the **Actions** button on the _Fly Tools_ +2. Select the _Change Altitude_ button +3. Select the new altitude from the vertical slider +4. Confirm the action diff --git a/docs/tr/qgc-user-guide/fly_view/fly_view.md b/docs/tr/qgc-user-guide/fly_view/fly_view.md index 018a1075b8d..474c4f9fa42 100644 --- a/docs/tr/qgc-user-guide/fly_view/fly_view.md +++ b/docs/tr/qgc-user-guide/fly_view/fly_view.md @@ -1,293 +1,46 @@ # Fly View -Uçuş Ekranı, aracı uçarken izlemek ve araca komut vermek için kullanılır. +The Fly View is used to command and monitor the vehicle. -Şunları yapmak için kullanabilirsiniz: - -- Otomatik şekilde [pre-flight checklist](#preflight_checklist) çalıştırın. -- Arm the vehicle (or check why it won't arm). -- Görevleri kontrol edin: [start](#start_mission), [continue](#continue_mission), [pause](#pause), ve [resume](#resume_mission). -- Aracı [arm](#arm)/[disarm](#disarm)/[emergency stop](#emergency_stop), [takeoff](#takeoff)/[land](#land), [change altitude](#change_altitude), belirli bir konuma [go to](#goto) veya [orbit](#orbit), ve [return/RTL](#rtl) için yönlendirin. -- Harita görünümü ile video görünümü (eğer varsa) arasında geçiş yapın -- Mevcut araç için video, görev, telemetri ve diğer bilgileri görüntüleyin ve ayrıca bağlı araçlar arasında geçiş yapın. +## Overview ![Uçuş Ekranı](../../../assets/fly/fly_view_overview.jpg) -## UI Overview - -Yukarıdaki ekran görüntüsü, uçuş ekranının ana öğelerini gösterir: - -- **Harita:** Bağlı tüm araçların pozisyonlarını ve mevcut aracın görevini gösterir. - - Haritada gezinmek için haritayı sürükleyebilirsiniz (harita belirli bir süre sonra otomatik olarak yeniden ortalanır). +- **[Toolbar](fly_view_toolbar.md):** The toolbar is at the top of the screen. It provides controls to select views, show flight status and mode as well as the status of the main components of the vehicle. +- **[Vehicle Actions](fly_tools.md):** Allows you command the vehicle to take a specific action. +- **[Instrument Panel](instrument_panel.md):** A widget that displays vehicle telemetry. +- **[Attitude/Compass](hud.md):** A widget that provides virtual horizon and heading information. +- **[Camera Tools](camera_tools.md)**: A widget for switching between still and video modes, starting/stopping capture, and controlling camera settings. +- **[Video](video.md):** Display the video from the vehicle. Allows you to toggle between video or map as the main display. +- **Map:** Displays the positions of all connected vehicles and the mission for the current vehicle. + - You can drag the map to move it around (the map automatically re-centres on the vehicle after a certain amount of time). + - You can zoom the map in and out using the zoom buttons, mouse wheel, track pad or pinch on a tablet. - Kalkıştan sonra, haritaya tıklayarak bir konuma [Go to](#goto) veya [Orbit at](#orbit) ayarlayabilirsiniz. -- **Uçuş Araç Çubuğu:** Sensörler (GPS, pil, RC kontrolü) ve araç durumu (Uçuş modu, Etkin (armed) / Devre Dışı (disarmed) durumu) hakkında anahtar bilgiler. - - Daha fazla ayrıntı görmek için sensör göstergelerini seçin. - - Yeni bir mod seçmek için _ Flight mode _ metnine (ör. "Hold") tıklayın. - Tüm modlar mevcut olmayabilir. - - The text next to the **Q** icon indicates the flight readiness using text: "Not Ready", "Ready to Fly", "Flying", and status using colour: "green" (all good!), amber (a warning), red (serious problem). - Select the text when the background is amber or red to find out the cause of any preflight issues (QGC 4.2.0 and later). - You can also select the text to reach a button to arm/disarm/emergency-stop the vehicle. -- **Uçuş araçları:** Şunları yapmak için kullanabilirsiniz: - - Kalkış/iniş arasında geçiş yapın. - - Mevcut işlemi durdur/tekrar başlat (ör. iniş, ya da görev). - - Güvenli geri dönüş (RTL ya da Return olarakta bilinir). - - _Action_ butonu mevcut durum için diğer uygun seçenekleri sunar (bunlar _Confirmation Slider_'ın üstünde gözükür). - İşlemler, yüksekliği değiştirmeyi veya bir göreve devam etmeyi içerir. - - [preflight checklist](#preflight_checklist)'i etkinleştirin (varsayılan olarak devre dışıdır). -- **[Instrument Panel](#instrument_panel):** A widget that displays vehicle telemetry. -- **Attitude/Compass**: A widget that provides virtual horizon and heading information. -- **Camera Tools**: A widget for switching between still and video modes, starting/stopping capture, and controlling camera settings. -- **[Video/Harita](#video_switcher):** Bir pencerede video ile harita arasında geçiş yapın. - - _Video_ ya da _Map_'i ön plana almak için öne almak istediğinize tıklayın. - - _QGroundControl_, aracınızın UDP bağlantısı üzerinden RTP ve RTSP video yayını yapmanızı destekler. - It also supports directly connected UVC devices. - QGC'nin video desteği hakkında daha ayrıntılı bilgiyi [Video README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md)'de bulabilirsiniz. - - Bir [Telemetry Overlay](../fly_view/video_overlay.md) dosyası otomatik olarak oluşturulacaktır -- **Kaydırmalı Onay Butonu:** İstenen işlemi gerçekleştirmek için onay butonu. - Operasyonu başlatmak için kaydırın. İptal etmek için **X** 'e basın. - -Ayrıca varsayılan olarak görüntülenmeyen/ belirli koşullarda görüntülenebilen bazı öğelerde var. -Mesela, çoklu-araç seçici sadece birden çok aracınız varsa veya uçuş öncesi kontrol listesi eğer etkinleştirilmişse görüntülenir. - -## Bilgi Paneli {#instrument_panel} - -The instrument panel displays telemetry information about the current vehicle. - -![Bilgi Paneli - değerler ve telemetri için](../../../assets/fly/instrument_page_values.jpg) - -The default values include altitude (relative to the home location), horizontal and vertical speed, total flight time, and distance between vehicle and ground station. - -You can configure where the information is displayed by hovering over the panel and selecting the left-side square tool. -This toggles the position of the panel between bottom centre and right-centre. - -![Bilgi Paneli - Titreşim Klipsleri](../../../assets/fly/instrument_page_vibration.jpg) - -You configure what information is display by selecting the edit/pencil icon. -The grid will then display "+" and "-" icons that you can use to add or remove rows and columns (and the pencil icon is replaced by a "lock" icon that you can use to save the settings). - -**[Bilgi Paneli](#instrument_panel):** Telemetri, kamera, video, sistem durumu ve titreşim dahil olmak üzere araç bilgilerini görüntüleyebileceğiniz çok sekmeli widget. - -Select a value to launch its "Value Display" editor. -This allows you to change the icon, text, size, units and so on of the current telemetry value. - -![Bilgi Paneli - değerlerin ayarları](../../../assets/fly/instrument_page_values_settings.jpg) - -The selection list on the top left is used to change the source of the telemetry. -By default this is the vehicle, but you can use the selector to choose a particular sensor type. - -![Bilgi Paneli - Cihazın Durumu İyi](../../../assets/fly/instrument_page_health_good.jpg) ![Bilgi Paneli - Cihazın Durumu Kötü](../../../assets/fly/instrument_page_health_bad.jpg) - -The selection list on the top right is used to select a particular telemetry value for the vehicle or sensor. - -Aracı devre dışı bırakmak için araç **landed** halindeyken _Fly Toolbar_ 'dan **Armed**'ı seçin. - -### Kamera {#camera_instrument_page} - -Kamera sayfası, kamerayı ayarlamak ve kontrol etmek için kullanılır. - -![Bilgi Paneli - Kamera için](../../../assets/fly/instrument_page_camera.jpg) - -The camera capture and configuration options depend on the connected camera. -The configuration options are selected using the panel gear icon. -The configuration for a simple autopilot-connected camera are shown below. - -![Bilgi Paneli - Kameranın MAVLink ayarları](../../../assets/fly/instrument_page_camera_mavlink.jpg) - -[MAVLink Camera Protocol](https://mavlink.io/en/services/camera.html)'ü destekleyen bir kameraya bağlandığınızda ek olarak geçerli hale gelen diğer kamera özelliklerini ayarlayıp kullanabilirsiniz. -Örnek olarak, eğer kameranız video modunu destekliyorsa, fotoğraf ve video modları arasında geçiş yapabilir, kaydı başlatıp/durdurabilirsiniz. - -![Bilgi Paneli - Kameranın MAVLink ayarları](../../../assets/fly/instrument_page_camera_mavlink.jpg) - -::: info -Most of the settings that are displayed depend on the camera (they are defined in its [MAVLink Camera Definition File](https://mavlink.io/en/services/camera_def.html)). - -> Sondaki bir kaç ortak ayar sabit olarak kodlanmıştır: Fotoğraf Modu (Tekli/Photolapse), Fotoğraf Aralığı (Timelapse için), Kamera Ayarlarını Varsayılana Sıfırla (kameraya bir sıfırlama komutu gönderir), Format (depolama) -### Video Akışı {#video_instrument_page} - -Video sayfası video akışını etkinleştirmek ve devre dışı bırakmak için kullanılır. -Etkinleştirildiğinde, video akışını durdurup başlatabilir, ızgara çizgilerini açabilir, görüntünün ekrana nasıl sığacağını değiştirebilir ve videoyu yerel olarak QGC ile kaydedebilirsiniz. - -![Bilgi Paneli - Video Akışı](../../../assets/fly/instrument_page_video_stream.jpg) +There are a number of other elements that are not displayed by default and are only displayed in certain conditions or for certain vehicle types. ## İşlemler/Görevler Aşağıdaki bölümler, Uçuş Ekranı'nda genel işlemlerin / görevlerin nasıl gerçekleştirileceğini açıklamaktadır. -Mevcut seçeneklerin çoğu, hem aracın türüne hem de mevcut durumuna bağlıdır. -::: - -### Uçuş Öncesi Kontrol Listesi {#preflight_checklist} - -Aracın doğru ayarlandığını ve uçmak için güvenli olduğu gösteren standart kontrollerin yapılması için otomatik bir uçuş öncesi kontrol listesi kullanılabilir. - -To view the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../settings_view/general.md) and selecting the **Use preflight checklist** checkbox. -Liste _Flight Tools_'a eklenecektir. -Kontrol listesini oradan açabilirsiniz: - -![Uçuş Öncesi Kontrol Listesi](../../../assets/fly/pre_flight_checklist.jpg) - -Once you have performed each test, select it on the UI to mark it as complete. - -### Arming and Preflight Checks {#arm} - -Bir aracı devreye almak, kalkışa hazırlık için motorları çalıştırır. -You will only be able to arm the vehicle if it is safe and ready to fly. - -:::tip -Genel olarak _ QGroundControl _ aracı manuel olarak devreye almanızı gerektirmez; Bir göreve veya kalkışa başlarsanız bu sizin için yapılır. -::: - -The vehicle is ready to fly in all modes if the status text says "Ready to Fly" and the background is green. - -![Vehicle state - ready to fly green/ready background](../../../assets/fly/vehicle_states/ready_to_fly_ok.png) - -If the background is amber then it is ready to take off in the current mode, but may not be able to switch to other modes. -If the background is red and the text is "Not Ready" then you will not be able to arm in the current mode. - -![Vehicle state - ready to fly amber/warning background](../../../assets/fly/vehicle_states/ready_to_fly_warning.png) -![Vehicle state - not ready](../../../assets/fly/vehicle_states/not_ready.png) - -From QGC 4.2.0 (at time of writing, a daily build) you can find out the exact cause of the warning or error, and possible solutions, by pushing the status text. - -This launches the preflight arming checks popup with a list of all preflight warnings. -The toggle on the right expands each error with additional information and possible solutions. - -![UI To check arming warnings](../../../assets/fly/vehicle_states/arming_preflight_check_ui.png) - -Once each issue is resolved it will disappear from the UI. -When all issues blocking arming have been removed you can use the arm button to display the arming confirmation slider, and arm the vehicle (or you can just take off - note that the vehicles will (by default) disarm automatically if you do not take off after a few seconds. - -![Aracı Devreye Alma](../../../assets/fly/arm.jpg) - -::: info -The status text also displays when flying. - -> ![Vehicle state - armed](../../../assets/fly/vehicle_states/armed.png) > ![Vehicle state - flying](../../../assets/fly/vehicle_states/flying.png) -> -> The arming checks UI will open even when flying, allowing you to emergency disarm. -> ::: - -### Aracı Devre Dışı Bırakma {#disarm} - -Aracı devre dışı bırakmak motorları durdurur (aracı güvenli hale getirir). - -Generally you do not need to explicitly disarm as vehicles will disarm automatically after landing, or shortly after arming if you do not take off. - -If needed, you can do so from the Arming Preflight Checks UI. - -Aracın uçuşa hazır olma durumunu değiştirmek için _Armed/Disarmed_ metnine tıklayın. - -You will then need to use the disarming slider. - -![Aracı Devre Dışı Bırakma](../../../assets/fly/disarm.jpg) - -Aracı uçarken devre dışı bırakmak [Emergency Stop](#emergency_stop) olarak adlandırılır - -### Acil Durdurma {#emergency_stop} - -Emergency stop is effectively the same as disarming the vehicle while it is flying. -Aracınız çarpacaktır/çakılacaktır! - -If needed, you can do so from the Arming Preflight Checks UI. - -Aracı devre dışı bırakmak için uçuş sırasında _Fly Toolbar_'dan **Armed**'ı seçin. - -You will then need to use the emergency disarming slider. - -![Acil Durdurma](../../../assets/fly/emergency_stop.jpg) - -### Kalkış {#takeoff} - -:::tip -If you are starting a mission for a multicopter, _QGroundControl_ will automatically perform the takeoff step. -::: - -Kalkmak için (iniş yapıldığında): - -1. _Fly Tools_'dan **Land** butonuna basın (kalkıştan sonra bu buton **Takeoff** butonu olarak değişecektir). -2. İsterseniz kalkış yüksekliğini sağda bulunan dikey kaydırıcıyla ayarlayabilirsiniz. -3. Confirm takeoff using the slider. - -![kalkış](../../../assets/fly/takeoff.png) - -### İniş {#land} - -Uçuş sırasında istediğiniz zaman mevcut konuma inebilirsiniz: - -1. _Fly Tools_'dan **Takeoff** butonuna basın (kalkıştan sonra bu buton **Land** butonu olarak değişecektir). -2. Confirm landing using the slider. - -![iniş](../../../assets/fly/land.jpg) - -### RTL/Geri Dönüş - -Return to a "safe point" at any time while flying: - -1. _Fly Tools_'dan **RTL** butonuna basın. -2. Confirm RTL using the slider. - -![rtl](../../../assets/fly/rtl.jpg) - -:::info -Vehicles commonly return to the "home" (takeoff) location and land. -This behaviour depends on the vehicle type and configuration. -For example, rally points or mission landings may be used as alternative return targets. -::: - -### Yükleklik Değiştirme {#change_altitude} - -Uçuş esnasında eğer bir görevde değilse aracın yükseliği değiştirilebilir: - -1. _Fly Tools_'dan **Action** butonuna basın - -2. İletişim kutusundan _Change Altitude_'ı seçin. - - ![Göreve Devam Etme/Yüksekliği Değiştirme ](../../../assets/fly/continue_mission_change_altitude_action.jpg) - -3. Dikey kaydırıcıyla istenilen yüksekliği ayarlayın, ardından kaydırmalı onay butonu ile onaylayın. - - ![Yüksekliği Değiştirme](../../../assets/fly/change_altitude.jpg) - -### Goto Location {#goto} - -Kalkıştan sonra belirli bir konuma uçmayı ayarlayabilirsiniz. - -1. Left click/Press on the map where you want the vehicle to move and select **Go to location** on the popup. - -![Hedefe gitme veya yörünge](../../../assets/fly/goto_or_orbit.jpg) - -1. Konum harita üzerinde kaydırmalı onay butonuyla birlikte gözükecektir. - - ![Hedefe gitme onayı](../../../assets/fly/goto.jpg) - -2. Hazır olduğunuzda kaydırarak onay verin (ya da **X**'e basarak iptal edin). - :::info -Hedef konum aracın 1 km çevresinde seçilmelidir (QGC'de sabit olarak ayarlanmıştır). +Many of the available options depend on both the vehicle type and its current state. ::: -### Yörünge Konumu {#orbit} +### Actions associated with a map position (#map_actions) -Kalkıştan sonra belirli bir konumun çevresinde yörüngede dolaşmasını ayarlayabilirsiniz. +There are a number of actions which can be taken which are associated with a specific position on the map. To use these actions: -1. Left click/Press on the map (near the centre of your desired orbit) and select **Orbit at location** on the popup. +1. Click on the map at a specific position +2. A popup will display showing you the list of available actions +3. Select the action you want +4. Confirm the action -![Hedefe gitme veya yörünge](../../../assets/fly/goto_or_orbit.jpg) - -1. Önerile yörünge kaydırmalı onay butonu ile harita üzerinde belirecektir. - - ![Yörünge Onayı](../../../assets/fly/orbit.jpg) - - - Yörüngenin konumunu değiştirmek için merkezini seçin ve kaydırın. - - Yörüngenin yarıçapını, çemberin dışındaki noktayı seçip sürükleyerek ayarlayabilirsiniz. - -2. Hazır olduğunuzda kaydırarak onay verin (ya da **X**'e basarak iptal edin). +Examples of map position actions are Go To Location, Orbit and so forth. ### Pause -You can pause most operations, including taking off, landing, RTL, mission execution, orbit at location. -Duraklatıldığında aracın davranışı aracın tipine bağlıdır, genellikle multikopterler havada asılı kalırken sabit kanatlar çember çizer. +You can pause most operations, including taking off, landing, RTL, mission execution, orbit at location. Duraklatıldığında aracın davranışı aracın tipine bağlıdır, genellikle multikopterler havada asılı kalırken sabit kanatlar çember çizer. :::info Bir _Goto location_ operasyonunu durduramazsınız. @@ -299,8 +52,6 @@ Durdurmak için: 2. İsterseniz yeni bir yüksekliği sağda bulunan dikey kaydırıcıyla ayarlayabilirsiniz. 3. Confirm the pause using the slider. -![duraklatma](../../../assets/fly/pause.jpg) - ### Görevler #### Görevi Başlatma {#start_mission} @@ -337,7 +88,7 @@ Görevinize aşağıdakileri yaparak devam edebilirsiniz (hali hazırda bir gör 2. İletişim kutusundan _Continue Mission_'ı seçin. - ![Göreve Devam Etme/Yüksekliği Değiştirme](../../../assets/fly/continue_mission_change_altitude_action.jpg) + ![Göreve Devam Etme/Yüksekliği Değiştirme ](../../../assets/fly/continue_mission_change_altitude_action.jpg) 3. Kaydırmalı onay butonunu kaydırarak göreve devam edin. diff --git a/docs/tr/qgc-user-guide/fly_view/fly_view_toolbar.md b/docs/tr/qgc-user-guide/fly_view/fly_view_toolbar.md new file mode 100644 index 00000000000..1895c883cfd --- /dev/null +++ b/docs/tr/qgc-user-guide/fly_view/fly_view_toolbar.md @@ -0,0 +1,78 @@ +# Fly View Toolbar + +![Fly View](../../../assets/fly/toolbar/fly_view_toolbar.jpg) + +## Views + +The "Q" icon on the left of the toolbar allows you to select between additional top level views: + +- **[Plan Flight](../plan_view/plan_view.md):** Used to create missions, geo-fences and rally points +- **Analyze Tools:** A set of tools for things like log download, geo-tagging images, or viewing telemetry. +- **Vehicle Configuration:** The various options for the initial configuration of a new vehicle. +- **Application Settings:** Settings for the QGroundControl application itself. + +## Toolbar Indicators + +Next are a multiple toolbar indicators for vehicle status. The dropdowns for each toolbar indicator provide additional detail on status. You can also expand the indicators to show additional application and vehicle settings associated with the indicator. Press the ">" button to expand. + +![Toolbar Indicator - expand button](../../../assets/fly/toolbar_indicator_expand.png) + +### Flight Status + +The Flight Status indicator shows you whether the vehicle is ready to fly or not. It can be in one of the following states: + +- **Ready To Fly** (_green background_) - Vehicle is ready to fly +- **Ready To Fly** (_yellow background_) - Vehicle is ready to fly in the current flight mode. But there are warnings which may cause problems. +- **Not Ready** - Vehicle is not ready to fly and will not takeoff. +- **Armed** - Vehicle is armed and ready to Takeoff. +- **Flying** - Vehicle is in the air and flying. +- **Landing** - Vehicle is in the process of landing. +- **Communication Lost** - QGroundControl has lost communication with the vehicle. + +The Flight Status Indicator dropdown also gives you acess to: + +- **Arm** - Arming a vehicle starts the motors in preparation for takeoff. You will only be able to arm the vehicle if it is safe and ready to fly. Generally you do not need to manually arm the vehicle. You can simply takeoff or start a mission and the vehicle will arm itself. +- **Disarm** - Disarming a vehicle is only availble when the vehicle is on the ground. It will stop the motors. Generally you do not need to explicitly disarm as vehicles will disarm automatically after landing, or shortly after arming if you do not take off. +- **Emergency Stop** - Emergency stop is used to disarm the vehicle while it is flying. For emergency use only, your vehicle will crash! + +In the cases of warnings or not ready state you can click the indicator to display the dropdown which will show the reason(s) why. The toggle on the right expands each error with additional information and possible solutions. + +![UI To check arming warnings](../../../assets/fly/vehicle_states/arming_preflight_check_ui.png) + +Once each issue is resolved it will disappear from the UI. When all issues blocking arming have been removed you should now be ready to fly. + +## Flight Mode + +The Flight Mode indicator shows you the current flight mode. The dropdown allows you to switch between flight modes. The expanded page allows you to: + +- Configure vehicle land settings +- Set global geo-fence settings +- Add/Remove flight modes from the displayed list + +## Vehicle Messages + +The Vehicle Messages indicator dropdown shows you messages which come from the vehicle. The indicator will turn red if there are important messages available. + +## GPS + +The GPS indicator shows you the satellite count and the HDOP in the toolbar icon. The dropdown shows you additional GPS status. The expanded page give you access to RTK settings. + +## Battery + +The Battery indicator shows you a configurable colored battery icon for remaining charge. It can also be configured to show percent remaining, voltage or both. The expanded page allows you to: + +- Set what value(s) you want displayed in the battery icon +- Configure the icon coloring +- Set up the low battery failsafe + +## Remote ID + +## Other Indicators + +There are other indicators which only show in certain situations: + +- Telemetry RSSI +- RC RSSI +- Gimbal +- VTOL transitions +- Select from multiple connected vehicles diff --git a/docs/tr/qgc-user-guide/fly_view/hud.md b/docs/tr/qgc-user-guide/fly_view/hud.md new file mode 100644 index 00000000000..6ec8c28be74 --- /dev/null +++ b/docs/tr/qgc-user-guide/fly_view/hud.md @@ -0,0 +1,429 @@ +# Fly View + +The Fly View is used to command and monitor the vehicle when flying. + +You can use it to: + +- Run an automated [pre-flight checklist](#preflight_checklist). +- Arm the vehicle (or check why it won't arm). +- Control missions: [start](#start_mission), [continue](#continue_mission), [pause](#pause), and [resume](#resume_mission). +- Guide the vehicle to [arm](#arm)/[disarm](#disarm)/[emergency stop](#emergency_stop), [takeoff](#takeoff)/[land](#land), [change altitude](#change_altitude), [go to](#map_actions) or [orbit](#map_actions) a particular location, and [return/RTL](#rtl). +- Switch between a map view and a video view (if available) +- Display video, mission, telemetry, and other information for the current vehicle, and also switch between connected vehicles. + +![Fly View](../../../assets/fly/fly_view_overview.jpg) + +## UI Overview + +The screenshot above shows the main elements of the fly view: + +- **[Fly Toolbar](fly_view_toolbar.md):** Key status information for vehicle components (GPS, battery, RC control), and vehicle state (Flight mode, Armed/Disarmed status). + - Select the [toolbar indicator](#toolbar_indicator) to view more detail. + - Press the _Flight mode_ text (e.g. "Hold") to select a new mode. + Not every mode may be available. + - The text next to the **Q** icon indicates the flight readiness using text: "Not Ready", "Ready to Fly", "Flying", and status using colour: "green" (all good!), amber (a warning), red (serious problem). You can also select the text to reach a button to arm/disarm/emergency-stop the vehicle. +- **[Fly tools](fly_tools.md):** You can use these to: + - Select the [preflight checklist](#preflight_checklist) (tool option disabled by default). + - Toggle between takeoff/land. + - Pause/restart the current operation (e.g. landing, or the mission). + - Safety return (also known as RTL or Return). + - The _Actions_ button offers other appropriate options for the current state. Actions include changing the altitude or continuing a mission. +- **Map:** Displays the positions of all connected vehicles and the mission for the current vehicle. + - You can drag the map to move it around (the map automatically re-centres on the vehicle after a certain amount of time). + - You can zoom the map in and out using the zoom buttons, mouse wheel, track pad or pinch on a tablet. + - Once flying, you can click on the map to set a [Go to](#goto) or [Orbit at](#orbit) location. +- **[Instrument Panel](instrument_panel.md):** A widget that displays vehicle telemetry. +- **[Attitude/Compass](hud.md):** A widget that provides virtual horizon and heading information. +- **Camera Tools**: A widget for switching between still and video modes, starting/stopping capture, and controlling camera settings. +- **[Video/Switcher](#video_switcher):** Toggle between video or map in a window. + - Press the element to switch _Video_ and _Map_ to foreground. + - _QGroundControl_ supports RTP and RTSP video streaming over your vehicles UDP connection. + It also supports directly connected UVC devices. + QGC video support is further discussed in the [Video README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md). + - A [Telemetry Overlay](../fly_view/video_overlay.md) is automatically generated as a subtitle file +- **Confirmation Slider:** Context sensitive slider to confirm requested actions. Slide to confirm operation. You can also hold the spacebar to confirm. Press **X** to cancel. + +There are a number of other elements that are not displayed by default/are only displayed in certain conditions. +For example, the multi-vehicle selector is only displayed if you have multiple vehicles, and the preflight checklist tool button is only displayed if the appropriate setting is enabled. + +## Fly Toolbar {#toolbar} + +### View Selector + +The "Q" icon on the left of the toolbar allows you to select between additional top level views: + +- **[Plan Flight](../plan_view/plan_view.md):** Used to create missions, geo-fences and rally points +- **Analyze Tools:** A set of tools for things like log download, geo-tagging images, or viewing telemetry. +- **Vehicle Configuration:** The various options for the initial configuration of a new vehicle. +- **Application Settings:** Settings for the QGroundControl application itself. + +### Toolbar Indicators {#toolbar_indicators} + +Next are a toolbar indicators for vehicle status. The dropdowns for each toolbar indicator provide additional detail on status. You can also expand the indicators to show additional application and vehicle settings associated with the indicator. Press the ">" button to expand. + +![Toolbar Indicator - expand button](../../../assets/fly/toolbar_indicator_expand.png) + +Here is an example expanded toolbar indicator for flight modes on a vehicle running PX4 firmware. The settings in this indicator provide access to things which may be relevant to change from flight to flight. + +![Toolbar Indicator - expanded](../../../assets/fly/toolbar_indicator_expanded.png) + +They also provide access to the Vehicle Configuration associated with the indicator. In this example: _Flight Modes_ - _Configure_. + +### Ready/Not Ready Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/vehicle_states/ready_to_fly_ok.png) + +Next in the toolbar is the indicator which shows you whether the vehicle is ready to fly or not. + +It can be in one of the following states: + +- **Ready To Fly** (_green background_) - Vehicle is ready to fly +- **Ready To Fly** (_yellow background_) - Vehicle is ready to fly in the current flight mode. But there are warnings which may cause problems. +- **Not Ready** - Vehicle is not ready to fly and will not takeoff. +- **Armed** - Vehicle is armed and ready to Takeoff. +- **Flying** - Vehicle is in the air and flying. +- **Landing** - Vehicle is in the process of landing. +- **Communication Lost** - QGroundControl has lost communication with the vehicle. + +The Ready Indicator dropdown also gives you acess to: + +- **Arming** - Arming a vehicle starts the motors in preparation for takeoff. You will only be able to arm the vehicle if it is safe and ready to fly. Generally you do not need to manually arm the vehicle. You can simply takeoff or start a mission and the vehicle will arm itself. +- **Disarm** - Disarming a vehicle is only availble when the vehicle is on the ground. It will stop the motors. Generally you do not need to explicitly disarm as vehicles will disarm automatically after landing, or shortly after arming if you do not take off. +- **Emergency Stop** - Emergency stop is effectively the same as disarming the vehicle while it is flying. For emergency use only, your vehicle will crash! + +In the cases of warnings or not ready state you can click the indicator to display the dropdown which will show the reason(s) why. The toggle on the right expands each error with additional information and possible solutions. + +![UI To check arming warnings](../../../assets/fly/vehicle_states/arming_preflight_check_ui.png) + +Once each issue is resolved it will disappear from the UI. +When all issues blocking arming have been removed you should now be ready to fly. + +### Flight Mode Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/toolbar/flight_modes_indicator.png) + +The Flight Mode Indicator dropdown allows you to switch between flight modes. The expanded page allows you to: + +- Configure vehicle land settings +- Set global geo-fence settings +- Add/Remove flight modes from the displayed list + +### Vehicle Messages Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/toolbar/messages_indicator.png) + +The Vehicle Messages Indicator dropdown shows you messages which come from the vehicle. The indicator will turn red if there are important messages available. + +### GPS Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/toolbar/gps_indicator.png) + +The GPS Indicator shows you the satellite count and the HDOP in the toolbar icon. The dropdown shows you additional GPS status. The expanded page give you access to RTK settings. + +### Battery Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/toolbar/battery_indicator.png) + +The Battery Indicator shows you a configurable colored battery icon for remaining charge. It can also be configured to show percent remaining, voltage or both. The expanded page allows you to: + +- Set what value(s) you want displayed in the battery icon +- Configure the icon coloring +- Set up the low battery failsafe + +## Fly Tools {#fly_tools} + +### Pre Flight Checklist {#preflight_checklist} + +An automated preflight checklist can be used to run through standard checks that the vehicle is configured correctly and it is safe to fly. + +To view the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../settings_view/general.md) and selecting the **Use preflight checklist** checkbox. +The tool will then be added to the _Flight Tools_. +Press it to open the checklist: + +![Pre Flight Checklist](../../../assets/fly/pre_flight_checklist.jpg) + +Once you have performed each test, select it on the UI to mark it as complete. + +### Takeoff {#takeoff} + +:::tip +If you are starting a mission for a multicopter, _QGroundControl_ will automatically perform the takeoff step. +::: + +To takeoff (when landed): + +1. Press the **Takeoff** button in the _Fly Tools_ (this will toggle to a **Land** button after taking off). +2. Optionally set the takeoff altitude in the right-side vertical slider. + +- You can slide up/down to change the altitude +- You can also click on the specified altitude (10 ft in example) and then type in a specific altitude. + +1. Confirm takeoff using the slider. + +![takeoff](../../../assets/fly/takeoff.png) + +### Land {#land} + +You can land at the current position at any time while flying: + +1. Press the **Land** button in the _Fly Tools_ (this will toggle to a **Takeoff** button when landed). +2. Confirm landing using the slider. + +### RTL/Return + +Return to a "safe point" at any time while flying: + +1. Press the **RTL** button in the _Fly Tools_. +2. Confirm RTL using the slider. + +:::info +Vehicles commonly return to the "home" (takeoff) location and land. +This behaviour depends on the vehicle type and configuration. +For example, rally points or mission landings may be used as alternative return targets. +::: + +### Change Altitude {#change_altitude} + +You can change altitude while flying, except when in a mission: + +1. Press the **Actions** button on the _Fly Tools_ +2. Select the _Change Altitude_ button +3. Select the new altitude from the vertical slider +4. Confirm the action + +## Instrument Panel (Telemetry) {#instrument_panel} + +The instrument panel displays telemetry information about the current vehicle. + +![Instrument Panel - for values/telemetry](../../../assets/fly/instrument_panel/instrument_panel_default_values.png) + +The default values include altitude (relative to the home location), horizontal and vertical speed, total flight time, and distance between vehicle and ground station. + +You can configure where the information is displayed by: + +- Tablets: Press and hold over control +- Desktop: Right click control +- Click to Lock icon to close and save changes + +![Instrument Panel - edit tools](../../../assets/fly/instrument_panel/instrument_panel_tools_edit.png) + +You configure what information is display by selecting the edit/pencil icon. +The grid will then display "+" and "-" icons that you can use to add or remove rows and columns (and the pencil icon is replaced by a "lock" icon that you can use to save the settings). + +Select a value to launch its "Value Display" editor. +This allows you to change the icon, text, size, units and so on of the current telemetry value. + +![Instrument Panel - edit a value](../../../assets/fly/instrument_panel/instrument_panel_tools_edit_value.png) + +The selection list on the top left is used to change the source of the telemetry. +By default this is the vehicle, but you can use the selector to choose a particular sensor type. + +![Instrument Panel - value type](../../../assets/fly/instrument_panel/instrument_panel_edit_value_type.png) + +The selection list on the top right is used to select a particular telemetry value for the vehicle or sensor. + +![Instrument Panel - value options](../../../assets/fly/instrument_panel/instrument_panel_edit_value_options.png) + +## Attitude /Compass {#hud} + +You can select from multiple types of instruments by: + +- Tablets: Press and hold over control +- Desktop: Right click over control +- Click the Lock icon to close and save changes + +![Instrument Panel - hover for move/edit tools](../../../assets/fly/hud_select_variant.png) + +### Camera {#camera_instrument_page} + +The camera panel is used to capture still images and video, and to configure the camera. + +![Camera Panel](../../../assets/fly/camera_panel/camera_mavlink.png) + +The camera capture and configuration options depend on the connected camera. +The configuration options are selected using the panel gear icon. +The configuration for a simple autopilot-connected camera are shown below. + +![Camera Panel - minimal settings](../../../assets/fly/camera_panel/camera_settings_minimal.png) + +When connected to camera that supports the [MAVLink Camera Protocol](https://mavlink.io/en/services/camera.html) you can additionally configure and use other camera services that it makes available. +For example, if your camera supports video mode you will be able to switch between still image capture and video mode, and start/stop recording. + +![Camera Panel - MAVLink settings](../../../assets/fly/camera_panel/camera_settings_mavlink.png) + +:::info +Most of the settings that are displayed depend on the camera (they are defined in its [MAVLink Camera Definition File](https://mavlink.io/en/services/camera_def.html)). + +> A few common settings at the end are hard-coded: Photo Mode (Single/Time Lapse), Photo Interval (if Time Lapse), Reset Camera Defaults (sends a reset command to the camera), Format (storage) +> ::: + +### Video Stream {#video_instrument_page} + +The video page is used to enable/disable video streaming. +When enabled, you can start/stop the video stream, enable a grid overlay, change how the image fits the screen, and record the video locally with QGC. + +![Instrument Page - Video Stream](../../../assets/fly/instrument_page_video_stream.jpg) + +## Actions/Tasks + +The following sections describe how to perform common operations/tasks in the Fly View. + +::: info +Many of the available options depend on both the vehicle type and its current state. +::: + +### Actions associated with a map position (#map_actions) + +There are a number of actions which can be taken which are associated with a specific position on the map. To use these actions: + +1. Click on the map at a specific position +2. A popup will display showing you the list of available actions +3. Select the action you want +4. Confirm the action + +Examples of map position actions are Go To Location, Orbit and so forth. + +### Pause + +You can pause most operations, including taking off, landing, RTL, mission execution, orbit at location. The vehicle behaviour when paused depends on the vehicle type; typically a multicopter will hover, and a fixed wing vehicle will circle. + +:::info +You cannot pause a _Goto location_ operation. +::: + +To pause: + +1. Press the **Pause** button in the _Fly Tools_. +2. Optionally set a new altitude using the right-side vertical slider. +3. Confirm the pause using the slider. + +### Missions + +#### Start Mission {#start_mission} + +You can start a mission when the vehicle is landed (the start mission confirmation slider is often displayed by default). + +To start a mission from landed: + +1. Press the **Action** button on the _Fly Tools_ + +2. Select the _Start Mission_ action from the dialog. + + ![Start mission action](../../../assets/fly/start_mission_action.jpg) + + (to display the confirmation slider) + +3. When the confirmation slider appears, drag it to start the mission. + + ![Start mission](../../../assets/fly/start_mission.jpg) + +#### Continue Mission {#continue_mission} + +You can _continue_ mission from the _next_ waypoint when you're flying (the _Continue Mission_ confirmation slider is often displayed by default after you takeoff). + +:::info +Continue and [Resume mission](#resume_mission) are different! +Continue is used to restart a mission that has been paused, or where you have taken off, so you've already missed a takeoff mission command. +Resume mission is used when you've used a RTL or landed midway through a mission (e.g. for a battery change) and then wish to continue the next mission item (i.e. it takes you to where you were up to in the mission, rather than continuing from your place in the mission). +::: + +You can continue the current mission while (unless already in a mission!): + +1. Press the **Action** button on the _Fly Tools_ + +2. Select the _Continue Mission_ action from the dialog. + + ![Continue Mission/Change Altitude action](../../../assets/fly/continue_mission_change_altitude_action.jpg) + +3. Drag the confirmation slider to continue the mission. + + ![Continue Mission](../../../assets/fly/continue_mission.jpg) + +#### Resume Mission {#resume_mission} + +_Resume Mission_ is used to resume a mission after performing an [RTL/Return](#rtl) or [Land](#land) from within a mission (in order, for example, to perform a battery change). + +:::info +If you are performing a battery change, **do not** disconnect QGC from the vehicle after disconnecting the battery. +After you insert the new battery _QGroundControl_ will detect the vehicle again and automatically restore the connection. +::: + +After landing you will be prompted with a _Flight Plan complete_ dialog, which gives you the option to remove the plan from the vehicle, leave it on the vehicle, or to resume the mission from the last waypoint that was traveled through. + +![Resume Mission](../../../assets/fly/resume_mission.jpg) + +If you select to resume the mission, then _QGroundControl_ will rebuild the mission and upload it to the vehicle. +Then use the _Start Mission_ slider to continue the mission. + +The image below shows the mission that was rebuilt after the Return shown above. + +![Resume Rebuilt Mission](../../../assets/fly/resume_mission_rebuilt.jpg) + +:::info +A mission cannot simply resume from the last mission item that the vehicle executed, because there may be multiple items at the last waypoint that affect the next stage of the mission (e.g. speed commands or camera control commands). +Instead _QGroundControl_ rebuilds the mission, starting from the last mission item flown, and automatically prepending any relevant commands to the front of the mission. +::: + +#### Remove Mission Prompt After Landing {#resume_mission_prompt} + +You will be prompted to remove the mission from the vehicle after the mission completes and the vehicle lands and disarms. +This is meant to prevent issues where stale missions are unknowingly left on a vehicle, potentially resulting in unexpected behavior. + +### Display Video {#video_switcher} + +When video streaming is enabled, _QGroundControl_ will display the video stream for the currently selected vehicle in the "video switcher window" at the bottom left of the map. +You can press the switcher anywhere to toggle _Video_ and _Map_ to foreground (in the image below, the video is shown in the foreground). + +![Video Stream Record](../../../assets/fly/video_record.jpg) + +:::info +Video streaming is configured/enabled in [Application Settings > General tab > Video](../settings_view/general.md#video). +::: + +You can further configure video display using controls on the switcher: + +![Video Pop](../../../assets/fly/video_pop.jpg) + +- Resize the switcher by dragging the icon in the top right corner. +- Hide the switcher by pressing the toggle icon in the lower left. +- Detach the video switcher window by pressing on the icon in its top left corner + (once detached, you can move and resize the window just like any other in your OS). + If you close the detached window the switcher will re-lock to the QGC Fly view. + +### Record Video + +If supported by the camera and vehicle, _QGroundControl_ can start and stop video recording on the camera itself. _QGroundControl_ can also record the video stream and save it locally. + +:::tip +Video stored on the camera may be of much higher quality, but it is likely that your ground station will have a much larger recording capacity. +::: + +#### Record Video Stream (on GCS) + +Video stream recording is controlled on the [video stream instrument page](#video_instrument_page). +Press the red circle to start recording a new video (a new video file is created each time the circle is pressed); the circle will change into a red square while recording is in progress. + +![Video Stream Record](../../../assets/fly/video_record.jpg) + +Video stream recording is configured in the [Application Settings > General tab](../settings_view/general.md): + +- [Video Recording](../settings_view/general.md#video-recording) - specifies the recording file format and storage limits. + + ::: info + Videos are saved in Matroska format (.mkv) by default. + This format is relatively robust against corruption in case of errors. + ::: + +- [Miscellaneous](../settings_view/general.md#miscellaneous) - Streamed video is saved under the **Application Load/Save Path**. + +:::tip +The stored video includes just the video stream itself. +To record video with QGroundControl application elements displayed, you should use separate screen recording software. +::: + +#### Record Video on Camera + +Start/stop video recording _on the camera itself_ using the [camera instrument page](#camera_instrument_page). +First toggle to video mode, then select the red button to start recording. + +![Instrument Page - Camera MAVLink Settings](../../../assets/fly/instrument_page_camera_mavlink.jpg) diff --git a/docs/tr/qgc-user-guide/fly_view/instrument_panel.md b/docs/tr/qgc-user-guide/fly_view/instrument_panel.md new file mode 100644 index 00000000000..5f4deed8d8c --- /dev/null +++ b/docs/tr/qgc-user-guide/fly_view/instrument_panel.md @@ -0,0 +1,32 @@ +# Instrument Panel + +The instrument panel displays telemetry information about the current vehicle. + +![Instrument Panel - for values/telemetry](../../../assets/fly/instrument_panel/instrument_panel_default_values.png) + +The default values include altitude (relative to the home location), horizontal and vertical speed, total flight time, and distance between vehicle and ground station. + +You can configure where the information is displayed by: + +- Tablets: Press and hold over control +- Desktop: Right click control +- Click to Lock icon to close and save changes + +![Instrument Panel - edit tools](../../../assets/fly/instrument_panel/instrument_panel_tools_edit.png) + +You configure what information is display by selecting the edit/pencil icon. +The grid will then display "+" and "-" icons that you can use to add or remove rows and columns (and the pencil icon is replaced by a "lock" icon that you can use to save the settings). + +Select a value to launch its "Value Display" editor. +This allows you to change the icon, text, size, units and so on of the current telemetry value. + +![Instrument Panel - edit a value](../../../assets/fly/instrument_panel/instrument_panel_tools_edit_value.png) + +The selection list on the top left is used to change the source of the telemetry. +By default this is the vehicle, but you can use the selector to choose a particular sensor type. + +![Instrument Panel - value type](../../../assets/fly/instrument_panel/instrument_panel_edit_value_type.png) + +The selection list on the top right is used to select a particular telemetry value for the vehicle or sensor. + +![Instrument Panel - value options](../../../assets/fly/instrument_panel/instrument_panel_edit_value_options.png) diff --git a/docs/tr/qgc-user-guide/fly_view/video.md b/docs/tr/qgc-user-guide/fly_view/video.md new file mode 100644 index 00000000000..432252d5c7e --- /dev/null +++ b/docs/tr/qgc-user-guide/fly_view/video.md @@ -0,0 +1,58 @@ +# Video + +When video streaming is enabled (Application Settings - Video), _QGroundControl_ will display the video stream for the currently selected vehicle in the "video switcher window" at the bottom left of the map. +You can press the switcher anywhere to toggle _Video_ and _Map_ to foreground (in the image below, the video is shown in the foreground). + +![Video Stream Record](../../../assets/fly/video_record.jpg) + +:::info +Video streaming is configured/enabled in [Application Settings > General tab > Video](../settings_view/general.md#video). +::: + +You can further configure video display using controls on the switcher: + +![Video Pop](../../../assets/fly/video_pop.jpg) + +- Resize the switcher by dragging the icon in the top right corner. +- Hide the switcher by pressing the toggle icon in the lower left. +- Detach the video switcher window by pressing on the icon in its top left corner + (once detached, you can move and resize the window just like any other in your OS). + If you close the detached window the switcher will re-lock to the QGC Fly view. + +### Record Video + +If supported by the camera and vehicle, _QGroundControl_ can start and stop video recording on the camera itself. _QGroundControl_ can also record the video stream and save it locally. + +:::tip +Video stored on the camera may be of much higher quality, but it is likely that your ground station will have a much larger recording capacity. +::: + +#### Record Video Stream (on GCS) + +Video stream recording is controlled on the [video stream instrument page](#video_instrument_page). +Press the red circle to start recording a new video (a new video file is created each time the circle is pressed); the circle will change into a red square while recording is in progress. + +![Video Stream Record](../../../assets/fly/video_record.jpg) + +Video stream recording is configured in the [Application Settings > General tab](../settings_view/general.md): + +- [Video Recording](../settings_view/general.md#video-recording) - specifies the recording file format and storage limits. + + ::: info + Videos are saved in Matroska format (.mkv) by default. + This format is relatively robust against corruption in case of errors. + ::: + +- [Miscellaneous](../settings_view/general.md#miscellaneous) - Streamed video is saved under the **Application Load/Save Path**. + +:::tip +The stored video includes just the video stream itself. +To record video with QGroundControl application elements displayed, you should use separate screen recording software. +::: + +#### Record Video on Camera + +Start/stop video recording _on the camera itself_ using the [camera instrument page](#camera_instrument_page). +First toggle to video mode, then select the red button to start recording. + +![Instrument Page - Camera MAVLink Settings](../../../assets/fly/instrument_page_camera_mavlink.jpg) diff --git a/docs/tr/qgc-user-guide/getting_started/download_and_install.md b/docs/tr/qgc-user-guide/getting_started/download_and_install.md index cd1e40f5794..13551917918 100644 --- a/docs/tr/qgc-user-guide/getting_started/download_and_install.md +++ b/docs/tr/qgc-user-guide/getting_started/download_and_install.md @@ -65,8 +65,8 @@ QGroundControl \* 'ı ilk kez kurmadan önce: sudo usermod -a -G dialout $USER sudo apt-get remove modemmanager -y sudo apt install gstreamer1.0-plugins-bad gstreamer1.0-libav gstreamer1.0-gl -y - sudo apt install libqt5gui5 -y sudo apt install libfuse2 -y + sudo apt install libxcb-xinerama0 libxkbcommon-x11-0 libxcb-cursor-dev -y ``` 2. Logout and login again to enable the change to user permissions. @@ -82,6 +82,7 @@ QGroundControl \* 'ı ilk kez kurmadan önce: ./QGroundControl.AppImage (or double click) ``` +:::info There are known [video steaming issues](../troubleshooting/qgc_setup.md#dual_vga) on Ubuntu 18.04 systems with dual adaptors. ::: @@ -92,8 +93,6 @@ Bu versiyonları Ubuntu 16.04'te çalıştırabilmek için [build QGroundControl ## Android {#android} -_QGroundControl_ is temporily unavailable from the Google Play Store. You can install manually from here: - - [Android 32 bit APK](https://qgroundcontrol.s3-us-west-2.amazonaws.com/latest/QGroundControl32.apk) - [Android 64 bit APK](https://qgroundcontrol.s3-us-west-2.amazonaws.com/latest/QGroundControl64.apk) diff --git a/docs/tr/qgc-user-guide/getting_started/quick_start.md b/docs/tr/qgc-user-guide/getting_started/quick_start.md index 40f6a752a7a..0bb23b57480 100644 --- a/docs/tr/qgc-user-guide/getting_started/quick_start.md +++ b/docs/tr/qgc-user-guide/getting_started/quick_start.md @@ -1,16 +1,16 @@ -# QGroundControl Quick Start +# QGroundControl için Hızlı Başlangıç -Getting _QGroundControl_ up and running is quick and easy: +_QGroundControl_'ü kurmak ve çalıştırmak, hızlı ve kolaydır: -1. [Download and install](../getting_started/download_and_install.md) the application. -1. Start _QGroundControl_. -1. Attach your vehicle to the ground station device via USB, through a telemetry radio, or over WiFi. _QGroundControl_ should detect your vehicle and connect to it automatically. +1. [Download and install (Daily 5.0)](../releases/daily_builds.md) the application. +2. _QGroundControl_'ü başlatın. +3. Aracınızı yer istasyonu cihazına USB, telemetri veya WIFI ile bağlayın. _QGroundControl_ aracınızı otomatik olarak tespit edip bağlanacaktır. -That's it! If the vehicle is ready to fly, _QGroundControl_ should display [Fly View](../fly_view/fly_view.md) as shown below (otherwise it will open [Setup View](../setup_view/setup_view.md)). +İşte bu kadar! Eğer aracınız uçuşa hazırsa, aşağıda görebileceğiniz üzere _QGroundControl_ [Fly View](../fly_view/fly_view.md) 'i görüntüleyecektir (aksi halde [Setup View](../setup_view/setup_view.md)'i açacaktır). ![](../../../assets/quickstart/fly_view_connected_vehicle.jpg) -A good way to become familiar with _QGroundControl_ is to start experimenting: +_QGroundControl_'e alışmanın iyi bir yolu denemeye başlamaktır: - Use the View Selector to switch between main views: - Plan Flight @@ -19,8 +19,8 @@ A good way to become familiar with _QGroundControl_ is to start experimenting: - Application Settings - Click the _Status Indicators_ on the toolbar to find out the status of the connected vehicle. -While the UI is fairly intuitive, this documentation can also be referenced to find out more. +Kullanıcı arayüzü gayet açık olsa da, daha fazlasını öğrenmek için bu dokümantasyona başvurulabilir. -::: info +:::info Make sure QGC has an internet connection when you connect a new vehicle in order to display map content. ::: diff --git a/docs/tr/qgc-user-guide/index.md b/docs/tr/qgc-user-guide/index.md index 7634f460373..7b6532e987e 100644 --- a/docs/tr/qgc-user-guide/index.md +++ b/docs/tr/qgc-user-guide/index.md @@ -1,6 +1,9 @@ -# QGroundControl User Guide +# QGroundControl Guide (Daily Build 5.0) -[![Releases](https://img.shields.io/github/release/mavlink/QGroundControl.svg)](https://github.com/mavlink/QGroundControl/releases) [![Discuss](https://img.shields.io/badge/discuss-px4-ff69b4.svg)](http://discuss.px4.io/c/qgroundcontrol/qgroundcontrol-usage) [![Discuss](https://img.shields.io/badge/discuss-ardupilot-ff69b4.svg)](http://discuss.ardupilot.org/c/ground-control-software/qgroundcontrol) [![Gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/mavlink/qgroundcontrol?utm_source=badge\&utm_medium=badge\&utm_campaign=pr-badge\&utm_content=badge) [![Slack](../../assets/site/slack.svg)](https://join.slack.com/t/px4/shared_invite/zt-si4xo5qs-R4baYFmMjlrT4rQK5yUnaA) +[![Discuss](https://img.shields.io/badge/discuss-px4-ff69b4.svg)](http://discuss.px4.io/c/qgroundcontrol/qgroundcontrol-usage) +[![Discuss](https://img.shields.io/badge/discuss-ardupilot-ff69b4.svg)](http://discuss.ardupilot.org/c/ground-control-software/qgroundcontrol) + +_You are viewing the docs for the upcoming 5.0 release of QGroundControl. If you want docs for a Stable build select from the Version dropdown above._ _QGroundControl_ provides full flight control and vehicle setup for PX4 or ArduPilot powered vehicles. It provides easy and straightforward usage for beginners, while still delivering high end feature support for experienced users. @@ -11,6 +14,7 @@ It provides easy and straightforward usage for beginners, while still delivering - Flight support for vehicles running PX4 and ArduPilot (or any other autopilot that communicates using the MAVLink protocol). - Mission planning for autonomous flight. - Flight map display showing vehicle position, flight track, waypoints and vehicle instruments. +- 3D viewer visualizing the 3D map of the environment (.osm file), the 3D model of the vehicle (only multi-rotors for the moment), and the mission 3D trajectory (including the waypoints). - Video streaming with instrument display overlays. - Support for managing multiple vehicles. - QGC runs on Windows, OS X, Linux platforms, iOS and Android devices. diff --git a/docs/tr/qgc-user-guide/plan_view/pattern.md b/docs/tr/qgc-user-guide/plan_view/pattern.md index db356c2a577..d96c97ed82f 100644 --- a/docs/tr/qgc-user-guide/plan_view/pattern.md +++ b/docs/tr/qgc-user-guide/plan_view/pattern.md @@ -5,9 +5,9 @@ Uygun şablon araçları, araca (ve uçuş dizinindeki araç tipinin desteğine) ![Şablon Aracı (Plan Araçları)](../../../assets/plan/pattern/pattern_tool.jpg) -| Şablon | Tanım | Araçlar | -| --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | +| Şablon | Tanım | Araçlar | +| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | | [Yüzey](../plan_view/pattern_survey.md) | Çok köşeli bir alan üstünde ızgara şeklinde bir uçuş şablonu oluşturun. Alanı ve coğrafi etiketli görüntüler oluşturmak için uygun ızgara ve kamera ayarlarını belirleyebilirsiniz. | Tüm | | [Yapı Taraması](../plan_view/pattern_structure_scan_v2.md) | Dikey yüzeyler üzerinde (çok köşeli ya da dairesel) görüntüler yakalayabilmek için ızgara şeklinde bir uçuş şablonu oluşturun. These are typically used for the visual inspection or creation of 3D models of structures. | MultiCopter, VTOL | -| [Koridor Taraması](../plan_view/pattern_corridor_scan.md) | Çoklu çizgileri takip eden bir uçuş planı oluşturun (mesela, bir yolu gözlemlemek için). | Tüm | -| [Sabit Kanat İnişi](../plan_view/pattern_fixed_wing_landing.md) | Bir göreve sabit kanatlı araçlar için iniş yolu ekleyin. | Fixed Wing | +| [Koridor Taraması](../plan_view/pattern_corridor_scan.md) | Çoklu çizgileri takip eden bir uçuş planı oluşturun (mesela, bir yolu gözlemlemek için). | Tüm | +| [Sabit Kanat İnişi](../plan_view/pattern_fixed_wing_landing.md) | Bir göreve sabit kanatlı araçlar için iniş yolu ekleyin. | Fixed Wing | diff --git a/docs/tr/qgc-user-guide/plan_view/plan_view.md b/docs/tr/qgc-user-guide/plan_view/plan_view.md index 437a1ed0fda..05ae35d0bb8 100644 --- a/docs/tr/qgc-user-guide/plan_view/plan_view.md +++ b/docs/tr/qgc-user-guide/plan_view/plan_view.md @@ -199,5 +199,5 @@ Bu olasılığı analiz etmek için, Plan yükleme/indirme için [ Console Loggi ## Daha Fazla Bilgi -- [QGC v3.2 sürümü](../releases/stable_v3.2_long.md#plan_view) için yeni plan ekranı özellikleri -- [QGC v3.3 sürümü](../releases/stable_v3.3_long.md#plan_view) için yeni plan ekranı özellikleri +- New Plan View features for [QGC release v3.2](../qgc-user-guide/releases/release_note_stable_v3.md#plan_view) +- New Plan View features for [QGC release v3.3](../qgc-user-guide/releases/release_note_stable_v3.md#plan-view-1) diff --git a/docs/tr/qgc-user-guide/releases/daily_builds.md b/docs/tr/qgc-user-guide/releases/daily_builds.md index 0550549176e..d821dea7b8d 100644 --- a/docs/tr/qgc-user-guide/releases/daily_builds.md +++ b/docs/tr/qgc-user-guide/releases/daily_builds.md @@ -10,23 +10,12 @@ Use at your own risk! These can be downloaded from the links below (install as described in [Download and Install](../getting_started/download_and_install.md)): - [Windows](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl-installer.exe) - - [OS X](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl.dmg) - - ::: info - QGroundControl continues to not be signed which causes problem on Catalina. To open QGC app for the first time: - - - Right-click the QGC app icon, select Open from the menu. You will only be presented with an option to Cancel. Select Cancel. - - Right-click the QGC app icon again, Open from the menu. This time you will be presented with the option to Open. - - ::: - -- [Linux](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl.AppImage) - -- [Android](https://play.google.com/store/apps/details?id=org.mavlink.qgroundcontrolbeta) - Google Play: Listed as _QGroundControl (Daily Test Build)_. - +- [Linux](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl-x86_64.AppImage) - Before running do the following: + - `chmod +x QGroundControl.AppImage` + - On the command prompt enter (one time only): + \- `sudo usermod -a -G dialout $USER` + \- `sudo apt-get remove modemmanager -y` + \- Logout and login again to enable the change to user permissions. +- [Android](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl.apk) - iOS currently unavailable - -:::info -The QGroundControl Continous Delivery pipeline from time to time might experience issues uploading to the Google Play store. You can find the daily build APK for Android devices for direct download here: [QGroundControl32.apk](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl32.apk), and [QGroundControl64.apk](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl64.apk) -::: diff --git a/docs/tr/qgc-user-guide/releases/privacy_policy.md b/docs/tr/qgc-user-guide/releases/privacy_policy.md index 44718df6e95..e9b88a034ec 100644 --- a/docs/tr/qgc-user-guide/releases/privacy_policy.md +++ b/docs/tr/qgc-user-guide/releases/privacy_policy.md @@ -1,8 +1,69 @@ # Privacy Policy +Dronecode Project, Inc. built the QGroundControl (org.mavlink.qgroundcontrol) app as an Open Source app. This SERVICE is provided by Dronecode Project, Inc. at no cost and is intended for use as is. + +This page is used to inform visitors regarding our policies with the collection, use, and disclosure of Personal Information if anyone decided to use our Service. + +If you choose to use our Service, then you agree to the collection and use of information in relation to this policy. The Personal Information that we collect is used for providing and improving the Service. We will not use or share your information with anyone except as described in this Privacy Policy. + +The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, which are accessible at QGroundControl (org.mavlink.qgroundcontrol) unless otherwise defined in this Privacy Policy. + +**Information Collection and Use** + +For a better experience, while using our Service, we may require you to provide us with certain personally identifiable information, including but not limited to device data. The information that we request will be retained by us and used as described in this privacy policy. + _QGroundControl_ may require access to personal and/or sensitive user data. None of this data is used outside of _QGroundControl_. The list below explains how some of the data is used: -- Camera sensor: This is used for the purpose of overlaying the video with flight telemetry data. -- Location: This is used for tracking current user position on the map. +- Camera sensor: This is used to overlay the video with flight telemetry data. +- Location: This is used for tracking the current user position on the map. + +The app does use third-party services that may collect information used to identify you. + +Link to the privacy policy of third-party service providers used by the app + +- [Google Play Services](https://www.google.com/policies/privacy/) + +**Log Data** + +We want to inform you that whenever you use our Service, in a case of an error in the app we collect data and information (through third-party products) on your phone called Log Data. This Log Data may include information such as your device Internet Protocol (“IP”) address, device name, operating system version, the configuration of the app when utilizing our Service, the time and date of your use of the Service, and other statistics. + +**Cookies** + +Cookies are files with a small amount of data that are commonly used as anonymous unique identifiers. These are sent to your browser from the websites that you visit and are stored on your device's internal memory. + +This Service does not use these “cookies” explicitly. However, the app may use third-party code and libraries that use “cookies” to collect information and improve their services. You have the option to either accept or refuse these cookies and know when a cookie is being sent to your device. If you choose to refuse our cookies, you may not be able to use some portions of this Service. + +**Service Providers** + +We may employ third-party companies and individuals due to the following reasons: + +- To facilitate our Service; +- To provide the Service on our behalf; +- To perform Service-related services; or +- To assist us in analyzing how our Service is used. + +We want to inform users of this Service that these third parties have access to their Personal Information. The reason is to perform the tasks assigned to them on our behalf. However, they are obligated not to disclose or use the information for any other purpose. + +**Security** + +We value your trust in providing us your Personal Information, thus we are striving to use commercially acceptable means of protecting it. But remember that no method of transmission over the internet, or method of electronic storage is 100% secure and reliable, and we cannot guarantee its absolute security. + +**Links to Other Sites** + +This Service may contain links to other sites. If you click on a third-party link, you will be directed to that site. Note that these external sites are not operated by us. Therefore, we strongly advise you to review the Privacy Policy of these websites. We have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services. + +**Children’s Privacy** + +These Services do not address anyone under the age of 13. We do not knowingly collect personally identifiable information from children under 13 years of age. In the case we discover that a child under 13 has provided us with personal information, we immediately delete this from our servers. If you are a parent or guardian and you are aware that your child has provided us with personal information, please contact us so that we will be able to do the necessary actions. + +**Changes to This Privacy Policy** + +We may update our Privacy Policy from time to time. Thus, you are advised to review this page periodically for any changes. We will notify you of any changes by posting the new Privacy Policy on this page. + +This policy is effective as of 2024-03-12 + +**Contact Us** + +If you have any questions or suggestions about our Privacy Policy, do not hesitate to contact us at info@dronecode.org. diff --git a/docs/tr/qgc-user-guide/releases/release_note_stable_v3.md b/docs/tr/qgc-user-guide/releases/release_note_stable_v3.md new file mode 100644 index 00000000000..f20e051fc1a --- /dev/null +++ b/docs/tr/qgc-user-guide/releases/release_note_stable_v3.md @@ -0,0 +1,564 @@ +# QGC v3 Release Notes + +This topic contains the cumulative release notes for _QGroundControl v3.x_. + +## Stable Version 3.5 + +This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.5. + +- **Overall** + - Added Airmap integration to QGC. OSX build only. + - Bumped settings version (now 8). + This will cause all settings to be reset to defaults. + - Added Chinese and Turkish localization and partial German localization. + - Added support for the Taisync 2.4GHz ViUlinx digital HD wireless link. + - Fix loading of parameters from multiple components. + This especially affected WiFi connections. + - **ArduPilot** Support for ChibiOS firmware connect and flash. +- **Settings** + - **RTK** Add support for specifying fixed RTK based station location in Settings/General. + - **GCS Location** + - Added UDP Port option for NMEA GPS Device. + - GCS heading shown if available +- **Plan** + - **Polygons** Support loading polygons from SHP files. + - **Fixed Wing Landing Pattern** Add stop photo/video support. + Defaults to on such that doing an RTL will stop camera. + - **Edit Position dialog** Available on polygon vertices. +- **Fly** + - **Camera Page** Updated support for new MAVLInk camera messages. + Camera select, camera mode, start/stop photo/video, storage mangement... + - **Orbit** Support for changing rotation direction. + - **Instrument Panel** + - Added ESTIMATOR_STATUS values to new estimatorStatus Vehicle FactGroup. + These are now available to display in instrument panel. + - Make Distance to GCS available for display from instrument panel. + - Make Heading to Home available for display from instrument panel. + +## Stable Version 3.4 + +This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.4. Not to mention the large number of bug fixes in each stable release. + +- **Settings** + - **Offline Maps** + - Center Tool allows you to specify a map location in lat/lon or UTM coordinates. Making it easier to get to the location you want to create an offline map for. + - Ability to pre-download terrain heights for offline use. + - **Help** Provides links to QGC user guide and forums. + +- **Setup** + - **Firmware** Ability to flash either PX4 or ArduPilot Flow firmware. + - PX4 Pro Firmware + - **Flight Modes** Specify channels for all available transmitter switches. + - **Tuning: Advanced** Initial implementation of vehicle PID tuning support. Note that this is a work in progress that will improve in 3.5 daily builds. + - ArduPilot Firmware + - **Power/Safety** Support for new multi-battery setup. + - **Trad Heli** New setup page. + +- **Plan** + + - **File Load/Save** New model for Plan file loading which matches a standard File Load/Save/Save As user model. + + - **Load KML** Ability to load a KML file directly from the Sync menu. You will be prompted for what type of Pattern you want to create from the KML if needed. + + - **Survey** Better support for irregular shaped polygons. + + - **[Corridor Scan](../plan_view/pattern_corridor_scan.md)** - Create a flight pattern which follows a poly-line. For example can be used to survey a road. + + - **[Fixed Wing Landing Pattern](../plan_view/pattern_fixed_wing_landing.md)** + - Landing area visually represented in Plan. + - Landing position/heading can be copied from Vehicle position/heading. + + - **Terrain** + + - Height of mission items can be specified as height above terrain. + - Survey and Corridor Scan can generate flight plans which follow terrain. + + ::: info + This feature does not support [ArduPilot terrain following](http://ardupilot.org/copter/docs/common-terrain-following.html). + ::: + + - **Edit Position** Set item position from vehicle position. + +- **Fly** + - **Pre-Flight Checklist** You can turn this on from Settings. It provides a generic checklist to follow prior to flight. Expect more feature to appear for this in 3.5 daily builds. + - **Instrument Panel** + - Many new values available for display. + - New Camera page which provides full camera control. Requires a camera which support new MavLink camera specification. + - **ArduPlane** Much better support for guided commands including QuadPlane support. + - **High Latency Links** Support for high latency links such as satellite connections. + Limits the traffic from QGC up to Vehicle on these links to reduce cost. + Supports HIGH_LATENCY MavLink message. + Supports failover back/forth from high latency to normal link with dual link setup. + +## Stable Version 3.3 (Summary) + +:::tip +More detailed release notes for version 3.3 can be found in the next section. +::: + +This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.3. Not to mention the large number of bug fixes of this release. + +- **Settings** + - Local NMEA GPS device support. + - Video Recording save settings. +- **Setup** + - **Parameter Editor** - Searching updates as you type characters for near immediate response to searches. + - **Joystick** - Android joystick support. +- **Plan** + - **NEW - Structure Scan Pattern** - Create a multi-layered flight pattern that captures images over vertical surfaces (polygonal or circular). Used for 3d model generation or vertical surface inspection. + - **Fixed Wing Landing Pattern** - You can now adjust the distance from the loiter to land point by either distance or glide slope fall rate. + - PX4 GeoFence and Rally Point support. + - Terrain height display in lower Mission Item altitude display +- **Fly** + - Start/Stop video recording. + - Better display of vehicle icons when connected to multiple vehicles. + - Multi-Vehicle View supports commands which apply to all vehicles. + - Displays vehicles reported from ADS-B sensor. +- **Analyze** + - **Mavlink console** - New support for communicating with Mavlink console. + - **Log Download** - Moved from Menu to Analyze view. + +## Stable Version 3.3 (Detailed) + +### Settings View + +#### NMEA GPS Device support + +![NMEA GPS Device support](../../../assets/settings/general/NMEADevice.jpg) + +You can specify a connection to one of these devices on the General page. +The GPS information will then be used for ground station location and in turn follow me support. + +For more information see [Settings > General (AutoConnect to the following devices)](../settings_view/general.md#auto_connect). + +#### Video Recording + +![Video Recording](../../../assets/settings/video_recording.jpg) + +Videos will be saved to the Video directory of your QGC file save path. +You can also specify the maximum amount of space you want video files to consume. +After that size if exceeded the oldest video files will be removed. +Video Recording is turned on/off from the Video widget in the Fly View. + +For more information see [Settings > General (Video / Video Recording)](../settings_view/general.md#video). + +### Plan View + +#### Structure Scan + +A Structure Scan allows you to create a grid flight pattern that captures images over vertical surfaces (polygonal or circular). +These are typically used for the visual inspection or creation of 3d models of structures. + +Details [here](../plan_view/pattern_structure_scan_v2.md). + +#### New MAVLink GeoFence, Rally Point support + +![](../../../assets/plan/geofence_rally.jpg) + +QGC supports the new MAVLink GeoFence and Rally Point specification/protocol. This new system supports multiple polygonal and/or circular fences which can be specified as an exclusion or an inclusion fence. + +The fence which is currently selected by the "Edit" radio button will show the on screen editing controls such as the drag points for polygon editing. + +**Note** Only PX4 Pro firmware supports the new specification. ArduPilot does not yet support the new spec. Support for GeoFence/Rally is temporarily disabled in QGC until QGC ArduPilot code is reworked to the new architecture. + +#### Edit Position Dialog + +![](../../../assets/plan/edit_position_dialog.jpg) + +The Edit Position Dialog allows you to specify a detailed position for an item in either Geographic or UTM coordinate systems. It is available from the Polygon Tools menu as well as the hamburger menu of any mission item which specifies a coordinate: + +![](../../../assets/plan/mission_item_editor_hamburger.jpg) + +#### Polygon Tools + +![](../../../assets/plan/polygon_tools.jpg) + +You can now also click on the polygon center drag handle to bring up a set of polygon manipulation tools. The tools are available anywhere polygon editing is supported: Survey, Structure Scan, GeoFence, ... + +- Circle - Converts the polygon to a circular polygon. +- Polygon - Changes a circular polygon back to a rectangular polygon. +- Set radius - Set radius for circular polygons. +- Edit position - Displays the edit position dialog to specify a detailed position for the circular center. +- Load KML - Set polygon to polygon loaded from KML file. + +Circular polygon example: + + + +### Fly View + +#### Start/Stop Video Recording + +This is now a video record button in the video window. Settings for saved videos are available from General Page of Setup view. + +#### Multi-Vehicle vehicle indicators + +When you are connected to multiple vehicles the vehicle id will be shown below the vehicle icon. The active vehicle will be opaque and the inactive vehicles will be semi-transparent. + +![](../../../assets/fly/multi_vehicle_indicators.jpg) + +#### Multi-Vehicle View supports batch commands + +The multi-vehicle list now supports commands which apply to all vehicles. + +![](../../../assets/fly/multi_vehicle_list.jpg) + +The current list of available commands are Pause and Start Mission but that will be exapanded upon with further development. + +#### ADS-B sensor vehicle display + +Vehicle reported by ADS-B sensor on vehicle are shown on map as smaller blue icons with altitude and callsign below the icon. + +![](../../../assets/fly/adsb_vehicle.jpg) + +## Stable Version 3.2 (Summary) + +:::tip +More detailed release notes for version 3.2 can be found in the next section. +::: + +This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.2. + +- **Settings** + + - **File Save path** - Specify a save path for all files used by QGC. + - **Telemetry log auto-save** - Telemetry logs are now automatically saved without prompting. + - **AutoLoad Plans** - Used to automatically load a Plan onto a vehicle when it first connects. + - **RTK GPS** - Specify the Survey in accuracy and Minimum observation duration. + +- **Setup** + + - ArduPilot only + - **Pre-Flight Barometer and Airspeed calibration** - Now supported + - **Copy RC Trims** - Now supported + +- **Plan View** + + - **Plan files** - Missions are now saved as .plan files which include the mission, geo-fence and rally points. + - **Plan Toolbar** - New toolbar which shows you mission statistics and Upload button. + - **Mission Start** - Allows you to specify values such as flight speed and camera settings to start the mission with. + - **New Waypoint features** - Adjust heading and flight speed for each waypoint as well as camera settings. + - **Visual Gimbal direction** - Gimbal direction is shown on waypoint indicators. + - **Pattern tool** - Allows you to add complex patterns to a mission. + - Fixed Wing Landing (new) + - Survey (many new features) + - **Fixed Wing Landing Pattern** - Adds a landing pattern for fixed wings to your mission. + - **Survey** - New features + - **Take Images in Turnarounds** - Specify whether to take images through entire survey or just within each transect segment. + - **Hover and Capture** - Stop vehicle at each image location and take photo. + - **Refly at 90 degree offset** - Add additional pattern at 90 degree offset to original so get better image coverage. + - **Entry location** - Specify entry point for survey. + - **Polygon editing** - Simple on screen mechanism to drag, resize, add/remove points. Much better touch support. + +- **Fly View** + + - **Arm/Disarm** - Available from toolbar. + - **Guided Actions** - New action toolbar on the left. Supports: + - Takeoff + - Land + - RTL + - Pause + - Start Mission + - Resume Mission - after battery change + - Change Altitude + - Land Abort + - Set Waypoint + - Goto Location + - **Remove mission after vehicle lands** - Prompt to remove mission from vehicle after landing. + - **Flight Time** - Flight time is shown in instrument panel. + - **Multi-Vehicle View** - Better control of multiple vehicles. + +- **Analyze View** - New + + - **Log Download** - Moved to Analyze view from menu + - **Mavlink Console** - NSH shell access + +- **Support for third-party customized QGroundControl** + - Standard QGC supports multiple firmware types and multiple vehicle types. There is now support in QGC which allows a third-party to create their own custom version of QGC which is targeted specifically to their custom vehicle. They can then release their own version of QGC with their vehicle. + +## Stable Version 3.2 (Detailed) + +This is a more detailed high level (but still _non-exhaustive_) list of new features added to _QGroundControl_ in version 3.2. + +### Settings + +#### Telemetry log auto-save + +If you have _Save telemetry log after each flight_ turned on you will no longer be prompted as to where to save the log each time the vehicle disarms. +Logs will automatically be saved to the [Application Load/Save Path](../settings_view/general.md#load_save_path) + +For more information see [Settings > General (Miscellaneous)](../settings_view/general.md#autosave_log). + +#### AutoLoad plans + +If this setting is turned on, _QGroundControl_ will automatically upload a plan to the vehicle when it connects. +The plan file must be named **AutoLoad#.plan** where the `#` is replaced with the vehicle id. +The plan file must be located in the [Application Load/Save Path](../settings_view/general.md#load_save_path). + +For more information see [Settings > General (Miscellaneous)](../settings_view/general.md#autoload_missions). + +#### Application Load/Save Path + +You can now specify a save path which QGC will use as the default location to save files such as Parameters, Telemetry or Mission Plans. + +For more information see [Settings > General (Miscellaneous)](../settings_view/general.md#load_save_path). + +#### RTK GPS + +You can now specify the _Survey in accuracy_ and _Minimum observation duration_ for use with a connected RTK GPS. + +For more information see [Settings > General (RTK GPS)](../settings_view/general.md#rtk_gps). + +### Setup + +#### ArduPilot - Pre-Flight Barometer and Airspeed calibration + +This is now supported from the Sensors page. + +#### ArduPilot - Copy RC Trims + +This is now supported from the Copy Trims button on the Radio setup page. + +### Plan View + +#### Plan Files + +Previous version of _QGroundControl_ saved missions, geo-fences and rally points in separate files (**.mission**, **.fence**, **.rally**). QGC now save all information related to a flight plan into a single file called a _Plan File_ with a file extension of **.plan**. + +Information about the format can be found in [Plan File Format](../../qgc-dev-guide/file_formats/plan.md) (QGC Developer Guide). + +#### Plan Toolbar + +![Plan Toolbar](../../../assets/plan/plan_toolbar.jpg) + +The new _Plan Toolbar_ is displayed at the top of the [PlanView](../plan_view/plan_view.md). +It shows you information related to the currently selected waypoint as well as statistics for the entire mission. + +When connected to a vehicle it also shows an **Upload** button, which can be used to upload the plan to the vehicle. + +#### Mission Settings + +The [Mission Settings](../plan_view/plan_view.md#mission_settings) panel allows you to specify values which apply to the entire mission, or settings you want to control right at the beginning of a mission. +This is the first item in the mission list on the right of the screen. + + + +##### Mission Defaults + +###### Waypoint alt + +This specifies the default altitude for newly added mission items. +If you update this value while you have a mission loaded it will prompt you to update all the the waypoints to this new altitude. + +###### Flight speed + +This allows you to set the flight speed for the mission to be different than the default mission speed. + +###### RTL after mission end + +Check this if you want your vehicle to RTL after the final mission item. + +##### Camera section + + + +The camera section allows you to specify a camera action to take, control the gimbal and set your camera into photo or video mode. + +The camera actions available are: + +- Continue current action +- Take photos (time) +- Take photos (distance) +- Stop taking photos +- Start recording video +- Stop recording video + +##### Vehicle Info section + + + +When planning a mission the firmware being run on the vehicle as well as the vehicle type must be known in order for QGroundControl to show you the mission commands which are appropriate for your vehicle. + +If you are planning a mission while you are connected to your vehicle the Firmware and Vehicle Type will be determined from the vehicle. If you are planning a mission while not connected to a vehicle you will need to specify this information yourself. + +The additional value that can be specified when planning a mission is the vehicle flight speed. By specifying this value, total mission or survey times can be approximated even when not connected to a vehicle. + +##### Planned Home Position + + + +The planned home position allows you to simulate the vehicle's home position while planning a mission. This way you see the waypoint trajectory for your vehicle from takeoff to mission completion. Keep in mind that this is only the "planned" home position and you should place it where you plan to start the vehicle from. It has no actual impact on flying the mission. The actual home position of a vehicle is set by the vehicle itself when arming. + +#### New Waypoint features + + + +- You can now adjust heading and flight speed for each waypoint. +- There is a camera section available for camera changes on each waypoint. Explanation of Camera Section can be read under Mission Settings above. + +#### Visual Gimbal direction + + + +If you specify gimbal yaw changes on waypoints, both the plan and fly views will show you a visual representation of the gimbal direction. + +#### Pattern tool + +There is a new _Pattern tool_. The following patterns are supported: + +- Fixed Wing Landing (new) +- Survey (with new features) + +##### Fixed Wing Landing Pattern + +![Fixed Wing Landing Pattern](../../../assets/plan/pattern/fixed_wing_landing_pattern.jpg) + +This adds a landing pattern for fixed wings to your mission. +The first point of the pattern is the loiter point which commands to vehicle to loiter to a specific altitude. +Once that altitude is reached, the vehicle will begin the landing sequence and fly down to the specified landing spot. + +Both the loiter and land points can be dragged to adjust. +Also all the various values associated with the pattern can be adjusted. + +For more information see [Fixed Wing Landing Pattern](../plan_view/pattern_fixed_wing_landing.md). + +##### Survey (new features) + +- Images are not automatically taken in the turnaround zone outside of the polygonal survey area. +- There is a new _Hover and Capture_ option which can be used to capture the highest quality image at each image location. The vehicle will stop at each image location prior to taking the image such that the vehicle is stable while the image is taken. +- There is a new option to re-fly the survey grid at a 90 degree angle to the previous pass. This allows you to generate much denser coverage for the images. + +![](../../../assets/plan/polygon_edit.jpg) + +Manipulating the survey area polygon is now easier to use on tablets with touch screens: + +- You can drag the entire polygon to a new location by dragging the center point handle. +- Each polygon vertex can be dragged to a new location. +- To remove a polygon vertex, simple click on the drag handle for it. +- Click on the **+** handles to add a new vertex between two existing vertices. + +### Fly View + +#### RTK GPS + +RTK status is now shown in the toolbar. + +#### Arm/Disarm + +There is an armed/disarmed indicator in the toolbar. You can click it to arm/disarm your vehicle. If you click Disarm in the toolbar while your vehicle is flying you will provided the option to Emergency Stop your vehicle. + +#### Guided Actions + +- Takeoff +- Land +- RTL +- Pause +- Actions + - Start Mission + - Resume Mission + - Change Altitude + - Land Abort +- Direct interaction with map + - Set Waypoint + - Goto Location + +##### Resume Mission + +The Resume Mission guided action is used to resume a mission after performing an RTL from within the mission to perform a battery change. +After the vehicle lands from RTL and you have disconnected the battery **do not** disconnect QGC from the Vehicle. +Put in your new battery and QGC will detect the vehicle again and automatically restore the connection. +Once this happens you will be prompted with a Resume Mission confirmation slider. +If you want to resume the mission, confirm this and the mission will be rebuilt from your last waypoint traveled through. +Once the mission is rebuilt you will be presented with another Resume Mission slide which allows you to review the rebuilt mission before starting it again. +Confirm this Resume Mission slider to continue on with the mission. + +\####### How resume mission rebuilding works + +In order to resume a mission you cannot simply continue it from the last mission item the vehicle ran. +The reason is is that may skip over important change speed commands or camera control commands which are prior to that item in the mission. +If you skipped over those the remainder of the mission will not run correctly. +In order to make resume mission work correctly QGC rebuilds the mission looking backwards from the last mission item flown and automatically appends relevant commands to the front of the mission. +By doing this the state of the mission prior to the resume point is restore. +The following mission commands are the ones scanned for: + +- `MAV_CMD_DO_CONTROL_VIDEO` +- `MAV_CMD_DO_SET_ROI` +- `MAV_CMD_DO_DIGICAM_CONFIGURE` +- `MAV_CMD_DO_DIGICAM_CONTROL` +- `MAV_CMD_DO_MOUNT_CONFIGURE` +- `MAV_CMD_DO_MOUNT_CONTROL` +- `MAV_CMD_DO_SET_CAM_TRIGG_DIST` +- `MAV_CMD_DO_FENCE_ENABLE` +- `MAV_CMD_IMAGE_START_CAPTURE` +- `MAV_CMD_IMAGE_STOP_CAPTURE` +- `MAV_CMD_VIDEO_START_CAPTURE` +- `MAV_CMD_VIDEO_STOP_CAPTURE` +- `MAV_CMD_DO_CHANGE_SPEED` +- `MAV_CMD_NAV_TAKEOFF` + +#### Remove mission after vehicle lands + +You will be prompted to remove the mission from the vehicle after the mission completes and the vehicle lands and disarms. +This is meant to prevent issues where stale missions are unknowingly left on a vehicle cause unexpected behavior. + +#### Instrument panel + +##### Camera trigger + +##### Flight Time + +Flight time is now available for display in the instrument panel. +For new users, flight time will be shown by default. +For existing users who have already modified their instrument panel values you will have to add it yourself if you want to use it. + +### [Analyze View](../analyze_view/index.md) + +- [Log Download](../analyze_view/log_download.md) moved to _Analyze View_ from menu. +- New [GeoTag Images](../analyze_view/geotag_images.md) support for PX4 Pro firmware +- New [MAVLink Console](../analyze_view/mavlink_console.md) which provides access the the _nsh shell_ running on the vehicle. + +### Multi-Vehicle View + +There is a new view available when you have multiple vehicles connected to QGC. It will only show up when more than one vehicle is connected. When that happens you will see an additional set of radio button at the top right of the Plan view. + + + +Click the **Multi-Vehicle** radio button to replace the instrument panel with the multi-vehicle list: + + + +The example above shows three vehicles. The numbers are the vehicle id. In the large font is the current flight mode. You can click the flight mode name to change to a different flight mode. To the right are small version of the instruments for each vehicle. You can command the vehicle to do the following actions from the control panel: + +- Arm/Disarm +- Start/Stop a mission +- Return to Launch +- Take Control back of the vehicle by returning to manual control from a mission. + +#### Multi-Vehicle Gotchas - Unique vehicle ids + +Each vehicle connected to QGC must have a unique id. Otherwise QGC will think the vehicles are actually the same vehicle. The symptom of this is the Plan view jerking around as it tries to position itself to one vehicle and then the next. For PX4 Pro firmwares this is the `MAV_SYS_ID` parameter. For ArduPilot firmwares it is the `SYSID_THISMAV` parameter. + +### Support for third-party customized QGroundControl + +Standard QGC supports multiple firmware types and multiple vehicle types. There is now support in QGC which allows a third-party to create their own custom version of QGC which is targeted specifically to their custom vehicle. They can then release their own version of QGC with their vehicle. + +## Stable Version 3.1 + +New Features + +- [Survey](../plan_view/pattern_survey.md) mission support +- [GeoFence](../plan_view/plan_geofence.md) support in Plan View +- [Rally Point](../plan_view/plan_rally_points.md) support in Plan View (ArduPilot only) +- ArduPilot onboard compass calibration +- Parameter editor search will now search as you type for quicker access +- Parameter display now supports unit conversion +- GeoTag images from log files (PX4 only) +- System health in instrument panel +- MAVLink 2.0 support (no signing yet) + +Major Bug Fixes + +- Fixed crash after disconnect from Vehicle +- Fixed android crash when using SiK Radios +- Many multi-vehicle fixes +- Bluetooth fixes diff --git a/docs/tr/qgc-user-guide/releases/release_note_stable_v4.md b/docs/tr/qgc-user-guide/releases/release_note_stable_v4.md new file mode 100644 index 00000000000..873f71f3d98 --- /dev/null +++ b/docs/tr/qgc-user-guide/releases/release_note_stable_v4.md @@ -0,0 +1,58 @@ +# QGC v4 Release Notes + +:::warning +Release notes are now tracked in the [Github release page](https://github.com/mavlink/qgroundcontrol/releases). +See that page for information about changes after v4.0.0. +::: + +## Stable Version 4.0 + +:::info +The format for Settings in QGC had to change in this release. Which means all QGC settings will be reset to defaults. +::: + +- Settings + - Language: Allow selection of language + - Optional [CSV Logging](../settings_view/csv.md) of telemetry data for improved accessibility. + - ArduPilot + - Support configurable mavlink stream rates. Available from Settings/Mavlink page. + ![Stream Rates JPG](../../../assets/daily_build_changes/arducopter_stream_rates.jpg) + - Improved support for flashing ChibiOS firmware + - Improved support for connecting to ChibiOS bootloader boards +- Setup + - Joystick + - New joystick setup ui + - Ability to configure held button to single or repeated action + - ArduPilot + - Motor Test + - ArduSub + - Automatic motor direction detection + - ArduCopter + - PID Tuning support ![PID Tuning JPG](../../../assets/daily_build_changes/arducopter_pid_tuning.jpg) + - Additional Basic Tuning options ![Basic Tuning JPG](../../../assets/daily_build_changes/arducopter_basic_tuning.jpg) + - Copter/Rover - Frame setup ui ![Setup Frame Copter JPG](../../../assets/daily_build_changes/arducopter_setup_frame.jpg) +- Plan + - Create Plan from template with wizard like progression for completing full Plan. + - Survey: Save commonly used settings as a Preset + - Polygon editing + - New editing tools ui + - Support for tracing a polygon from map locations + - ArduPilot + - Support for GeoFence and Rally Points using latest firmwares and mavlink v2 + - [Pattern Presets](../plan_view/pattern_presets.md) + - Allows you to save settings for a Pattern item (Survey, Corridor Scan, ...) into a named preset. You can then use this preset over and over again as you create new Pattern. +- Fly + - Click to ROI support + - Added support for connecting to ADSB SBS server. Adds support for ADSB data from USB SDR Dongle running 'dump1090 --net' for example. + - Ability to turn on Heading to home, COG and Next Waypoint heading indicators in Compass. + - Video + - Add support for h.265 video streams + - Automatically add a [Video Overlay](../fly_view/video_overlay.md) with flight data as a subtitle for locally-recorded videos + - Vehicle type specific pre-flight checklists. Turn on from Settings. +- Analyze + - New Mavlink Inspector which includes charting support. Supported on all builds including Android and iOS. +- General + - Released Windows build are now 64 bit only + - Log Replay: Ability to specify replay speed + - ArduPilot + - Improved support for chibios firmwares and ArduPilot bootloader with respect to flashing and auto-connect. diff --git a/docs/tr/qgc-user-guide/releases/release_notes.md b/docs/tr/qgc-user-guide/releases/release_notes.md index b8512cb610c..63ba1f4bd9a 100644 --- a/docs/tr/qgc-user-guide/releases/release_notes.md +++ b/docs/tr/qgc-user-guide/releases/release_notes.md @@ -1,255 +1,7 @@ # Release Notes -This topic contains the cumulative release notes for _QGroundControl_. +Releases and their associated release notes can be found in the [Github releases page](https://github.com/mavlink/qgroundcontrol/releases). :::info -Stable build major/minor numbers are listed below. -_Patch_ release numbers are not listed, but can be found on the [Github release page](https://github.com/mavlink/qgroundcontrol/releases). +Release information about QGC v4.0.0 and earlier can be found in the sub pages. ::: - -## Stable Version 4.0 (current) - -:::info -The format for Settings in QGC had to change in this release. Which means all QGC settings will be reset to defaults. -::: - -- Settings - - Language: Allow selection of language - - Optional [CSV Logging](../settings_view/csv.md) of telemetry data for improved accessibility. - - ArduPilot - - Mavlink: Configurable stream rate settings -- Setup - - Joystick - - New joystick setup ui - - Ability to configure held button to single or repeated action - - ArduPilot - - Motor Test - - ArduSub - - Automatic motor direction detection -- Plan - - Create Plan from template with wizard like progression for completing full Plan. - - Survey: Save commonly used settings as a Preset - - Polygon editing - - New editing tools ui - - Support for tracing a polygon from map locations - - ArduPilot - - Support for GeoFence and Rally Points using latest firmwares and mavlink v2 -- Fly - - Click to ROI support - - Added support for connecting to ADSB SBS server. Adds support for ADSB data from USB SDR Dongle running 'dump1090 --net' for example. - - Ability to turn on Heading to home, COG and Next Waypoint heading indicators in Compass. - - Video - - Add support for h.265 video streams - - Automatically add a [Video Overlay](../fly_view/video_overlay.md) with flight data as a subtitle for locally-recorded videos - - Vehicle type specific pre-flight checklists. Turn on from Settings. -- Analyze - - New Mavlink Inspector which includes charting support. Supported on all builds including Android and iOS. -- General - - Released Windows build are now 64 bit only - - Log Replay: Ability to specify replay speed - - ArduPilot - - Improved support for chibios firmwares and ArduPilot bootloader with respect to flashing and auto-connect. - -Additional notes for some features can be found here: [v4.0 (Additional Notes)](../releases/stable_v4.0_additional.md). - -## Stable Version 3.5 - -This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.5. - -- **Overall** - - Added Airmap integration to QGC. OSX build only. - - Bumped settings version (now 8). - This will cause all settings to be reset to defaults. - - Added Chinese and Turkish localization and partial German localization. - - Added support for the Taisync 2.4GHz ViUlinx digital HD wireless link. - - Fix loading of parameters from multiple components. - This especially affected WiFi connections. - - **ArduPilot** Support for ChibiOS firmware connect and flash. -- **Settings** - - **RTK** Add support for specifying fixed RTK based station location in Settings/General. - - **GCS Location** - - Added UDP Port option for NMEA GPS Device. - - GCS heading shown if available -- **Plan** - - **Polygons** Support loading polygons from SHP files. - - **Fixed Wing Landing Pattern** Add stop photo/video support. - Defaults to on such that doing an RTL will stop camera. - - **Edit Position dialog** Available on polygon vertices. -- **Fly** - - **Camera Page** Updated support for new MAVLInk camera messages. - Camera select, camera mode, start/stop photo/video, storage mangement... - - **Orbit** Support for changing rotation direction. - - **Instrument Panel** - - Added ESTIMATOR_STATUS values to new estimatorStatus Vehicle FactGroup. - These are now available to display in instrument panel. - - Make Distance to GCS available for display from instrument panel. - - Make Heading to Home available for display from instrument panel. - -## Stable Version 3.4 - -This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.4. Not to mention the large number of bug fixes in each stable release. - -- **Settings** - - **Offline Maps** - - Center Tool allows you to specify a map location in lat/lon or UTM coordinates. Making it easier to get to the location you want to create an offline map for. - - Ability to pre-download terrain heights for offline use. - - **Help** Provides links to QGC user guide and forums. - -- **Setup** - - **Firmware** Ability to flash either PX4 or ArduPilot Flow firmware. - - PX4 Pro Firmware - - **Flight Modes** Specify channels for all available transmitter switches. - - **Tuning: Advanced** Initial implementation of vehicle PID tuning support. Note that this is a work in progress that will improve in 3.5 daily builds. - - ArduPilot Firmware - - **Power/Safety** Support for new multi-battery setup. - - **Trad Heli** New setup page. - -- **Plan** - - - **File Load/Save** New model for Plan file loading which matches a standard File Load/Save/Save As user model. - - - **Load KML** Ability to load a KML file directly from the Sync menu. You will be prompted for what type of Pattern you want to create from the KML if needed. - - - **Survey** Better support for irregular shaped polygons. - - - **[Corridor Scan](../plan_view/pattern_corridor_scan.md)** - Create a flight pattern which follows a poly-line. For example can be used to survey a road. - - - **[Fixed Wing Landing Pattern](../plan_view/pattern_fixed_wing_landing.md)** - - Landing area visually represented in Plan. - - Landing position/heading can be copied from Vehicle position/heading. - - - **Terrain** - - - Height of mission items can be specified as height above terrain. - - Survey and Corridor Scan can generate flight plans which follow terrain. - - ::: info - This feature does not support [ArduPilot terrain following](http://ardupilot.org/copter/docs/common-terrain-following.html). - ::: - - - **Edit Position** Set item position from vehicle position. - -- **Fly** - - **Pre-Flight Checklist** You can turn this on from Settings. It provides a generic checklist to follow prior to flight. Expect more feature to appear for this in 3.5 daily builds. - - **Instrument Panel** - - Many new values available for display. - - New Camera page which provides full camera control. Requires a camera which support new MavLink camera specification. - - **ArduPlane** Much better support for guided commands including QuadPlane support. - - **High Latency Links** Support for high latency links such as satellite connections. - Limits the traffic from QGC up to Vehicle on these links to reduce cost. - Supports HIGH_LATENCY MavLink message. - Supports failover back/forth from high latency to normal link with dual link setup. - -## Stable Version 3.3 - -:::tip -More detailed release notes for version 3.3 can be found [here](../releases/stable_v3.3_long.md). -::: - -This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.3. Not to mention the large number of bug fixes of this release. - -- **Settings** - - Local NMEA GPS device support. - - Video Recording save settings. -- **Setup** - - **Parameter Editor** - Searching updates as you type characters for near immediate response to searches. - - **Joystick** - Android joystick support. -- **Plan** - - **NEW - Structure Scan Pattern** - Create a multi-layered flight pattern that captures images over vertical surfaces (polygonal or circular). Used for 3d model generation or vertical surface inspection. - - **Fixed Wing Landing Pattern** - You can now adjust the distance from the loiter to land point by either distance or glide slope fall rate. - - PX4 GeoFence and Rally Point support. - - Terrain height display in lower Mission Item altitude display -- **Fly** - - Start/Stop video recording. - - Better display of vehicle icons when connected to multiple vehicles. - - Multi-Vehicle View supports commands which apply to all vehicles. - - Displays vehicles reported from ADS-B sensor. -- **Analyze** - - **Mavlink console** - New support for communicating with Mavlink console. - - **Log Download** - Moved from Menu to Analyze view. - -## Stable Version 3.2 - -:::tip -More detailed release notes for version 3.2 can be found [here](../releases/stable_v3.2_long.md). -::: - -This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.2. - -- **Settings** - - - **File Save path** - Specify a save path for all files used by QGC. - - **Telemetry log auto-save** - Telemetry logs are now automatically saved without prompting. - - **AutoLoad Plans** - Used to automatically load a Plan onto a vehicle when it first connects. - - **RTK GPS** - Specify the Survey in accuracy and Minimum observation duration. - -- **Setup** - - - ArduPilot only - - **Pre-Flight Barometer and Airspeed calibration** - Now supported - - **Copy RC Trims** - Now supported - -- **Plan View** - - - **Plan files** - Missions are now saved as .plan files which include the mission, geo-fence and rally points. - - **Plan Toolbar** - New toolbar which shows you mission statistics and Upload button. - - **Mission Start** - Allows you to specify values such as flight speed and camera settings to start the mission with. - - **New Waypoint features** - Adjust heading and flight speed for each waypoint as well as camera settings. - - **Visual Gimbal direction** - Gimbal direction is shown on waypoint indicators. - - **Pattern tool** - Allows you to add complex patterns to a mission. - - Fixed Wing Landing (new) - - Survey (many new features) - - **Fixed Wing Landing Pattern** - Adds a landing pattern for fixed wings to your mission. - - **Survey** - New features - - **Take Images in Turnarounds** - Specify whether to take images through entire survey or just within each transect segment. - - **Hover and Capture** - Stop vehicle at each image location and take photo. - - **Refly at 90 degree offset** - Add additional pattern at 90 degree offset to original so get better image coverage. - - **Entry location** - Specify entry point for survey. - - **Polygon editing** - Simple on screen mechanism to drag, resize, add/remove points. Much better touch support. - -- **Fly View** - - - **Arm/Disarm** - Available from toolbar. - - **Guided Actions** - New action toolbar on the left. Supports: - - Takeoff - - Land - - RTL - - Pause - - Start Mission - - Resume Mission - after battery change - - Change Altitude - - Land Abort - - Set Waypoint - - Goto Location - - **Remove mission after vehicle lands** - Prompt to remove mission from vehicle after landing. - - **Flight Time** - Flight time is shown in instrument panel. - - **Multi-Vehicle View** - Better control of multiple vehicles. - -- **Analyze View** - New - - - **Log Download** - Moved to Analyze view from menu - - **Mavlink Console** - NSH shell access - -- **Support for third-party customized QGroundControl** - - Standard QGC supports multiple firmware types and multiple vehicle types. There is now support in QGC which allows a third-party to create their own custom version of QGC which is targeted specifically to their custom vehicle. They can then release their own version of QGC with their vehicle. - -## Stable Version 3.1 - -New Features - -- [Survey](../plan_view/pattern_survey.md) mission support -- [GeoFence](../plan_view/plan_geofence.md) support in Plan View -- [Rally Point](../plan_view/plan_rally_points.md) support in Plan View (ArduPilot only) -- ArduPilot onboard compass calibration -- Parameter editor search will now search as you type for quicker access -- Parameter display now supports unit conversion -- GeoTag images from log files (PX4 only) -- System health in instrument panel -- MAVLink 2.0 support (no signing yet) - -Major Bug Fixes - -- Fixed crash after disconnect from Vehicle -- Fixed android crash when using SiK Radios -- Many multi-vehicle fixes -- Bluetooth fixes diff --git a/docs/tr/qgc-user-guide/settings_view/console_logging.md b/docs/tr/qgc-user-guide/settings_view/console_logging.md index e2f23215edd..61f08b03ce0 100644 --- a/docs/tr/qgc-user-guide/settings_view/console_logging.md +++ b/docs/tr/qgc-user-guide/settings_view/console_logging.md @@ -10,15 +10,15 @@ Click the **Set Logging** button to enable/disable logging information displayed The most commmonly used logging options are listed below. -| Option(s) | Description | -| ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | -| `LinkManagerLog`, `MultiVehicleManagerLog` | Debug connection problems. | +| Option(s) | Description | +| ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | +| `LinkManagerLog`, `MultiVehicleManagerLog` | Debug connection problems. | | `LinkManagerVerboseLog` | Debug serial ports not being detected. Very noisy continuous output of available serial ports. | -| `FirmwareUpgradeLog` | Debug firmware flash issues. | -| `ParameterManagerLog` | Debug parameter load problems. | -| `ParameterManagerDebugCacheFailureLog` | Debug parameter cache crc misses. | -| `PlanManagerLog`, `MissionManagerLog`, `GeoFenceManagerLog`, `RallyPointManagerLog` | Debug Plan upload/download issues. | -| `RadioComponentControllerLog` | Debug Radio calibration issues. | +| `FirmwareUpgradeLog` | Debug firmware flash issues. | +| `ParameterManagerLog` | Debug parameter load problems. | +| `ParameterManagerDebugCacheFailureLog` | Debug parameter cache crc misses. | +| `PlanManagerLog`, `MissionManagerLog`, `GeoFenceManagerLog`, `RallyPointManagerLog` | Debug Plan upload/download issues. | +| `RadioComponentControllerLog` | Debug Radio calibration issues. | ## Logging from the Command Line diff --git a/docs/tr/qgc-user-guide/setup_view/flight_modes.md b/docs/tr/qgc-user-guide/setup_view/flight_modes.md index 1a9b242fffa..d5463b5f249 100644 --- a/docs/tr/qgc-user-guide/setup_view/flight_modes.md +++ b/docs/tr/qgc-user-guide/setup_view/flight_modes.md @@ -56,6 +56,6 @@ Commonly this is done by encoding the positions of a 2- and a 3-position switch On the FrSky Taranis this process involves assigning a "logical switch" to each combination of positions of the two real switches. Each logical switch is then assigned to a different PWM value on the same channel. -This video shows how this is done with the _FrSky Taranis_ transmitter: https\://youtu.be/TFEjEQZqdVA +This video shows how this is done with the _FrSky Taranis_ transmitter: https://youtu.be/TFEjEQZqdVA diff --git a/docs/tr/qgc-user-guide/setup_view/flight_modes_ardupilot.md b/docs/tr/qgc-user-guide/setup_view/flight_modes_ardupilot.md index 9a5b46b8408..87430e37cb1 100644 --- a/docs/tr/qgc-user-guide/setup_view/flight_modes_ardupilot.md +++ b/docs/tr/qgc-user-guide/setup_view/flight_modes_ardupilot.md @@ -42,6 +42,7 @@ To set the flight modes: All values are automatically saved as they are changed. +:::info The ArduCopter screenshot above shows a typical setup for a three position flight mode switch with an additional option of RTL being on a channel 7 switch. You can also setup 6 flight modes using two switches plus mixing on your transmitter. Scroll down to the center section of this [page](http://ardupilot.org/copter/docs/common-rc-transmitter-flight-mode-configuration.html#common-rc-transmitter-flight-mode-configuration) for tutorials on how to do that. ::: diff --git a/docs/tr/qgc-user-guide/setup_view/joystick.md b/docs/tr/qgc-user-guide/setup_view/joystick.md index df49a38a90c..5cbdd423c7b 100644 --- a/docs/tr/qgc-user-guide/setup_view/joystick.md +++ b/docs/tr/qgc-user-guide/setup_view/joystick.md @@ -18,7 +18,7 @@ Belirli bir kontrolcüyle uyumluluk, SDL'ye bağlıdır (bu API tarafından gös ## PX4 Joystick Desteğini Etkinleştirme -To enable Joystick support in PX4 you need to set the parameter [`COM_RC_IN_MODE`](h[ttp://localhost:8080/px4_user_guide/en](https://docs.px4.io/en/main/advanced_config/parameter_reference.html#COM_RC_IN_MODE) to `1` - _Joystick_. +To enable Joystick support in PX4 you need to set the parameter [`COM_RC_IN_MODE`](https://docs.px4.io/en/main/advanced_config/parameter_reference.html#COM_RC_IN_MODE) to `1` - _Joystick_. If this parameter is `0` then _Joystick_ will not be offered as a setup option. Bu, PX4 SITL yapıları için varsayılan olarak etkindir (belirli bir parametrenin nasıl bulunacağı ve ayarlanacağı hakkında bilgi için [Parametreler](../setup_view/parameters.md) konusuna bakın). diff --git a/docs/tr/qgc-user-guide/setup_view/motors.md b/docs/tr/qgc-user-guide/setup_view/motors.md index e67232f3499..061c992e933 100644 --- a/docs/tr/qgc-user-guide/setup_view/motors.md +++ b/docs/tr/qgc-user-guide/setup_view/motors.md @@ -20,13 +20,19 @@ Motorları test etmek için: 2. (_ yalnızca PX4 _) güvenlik anahtarını etkinleştirin - varsa. -3. Motor kaydırıcılarını etkinleştirmek için onaylayıcıyı (_ Pervaneler çıkarıldı - Motor kaydırıcılarını etkinleştirin _) kaydırın. +3. Slide the switch to enable motor slider and buttons (labeled: _Propellers are removed - Enable slider and motors_). -4. Motorları döndürmek ve doğru yönde döndüklerini doğrulamak için tek tek kaydırıcıları ayarlayın. +4. Adjust the slider to select the power for the motors. - > \*\* Not \*\* Motorlar yalnızca kaydırıcıyı bıraktıktan sonra döner ve 3 saniye sonra otomatik olarak dönmeyi durdurur. - > ::: +5. Press the button corresponding to the motor and confirm it spin in the correct direction. + + ::: info + The motors will automatically stop spinning after 3 seconds. + You can also stop the motor by pressing the 'Stop' button. + If no motors turn, raise the “Throttle %” and try again. + ::: ## Ek Bilgi - [Basic Configuration > Motor Setup](http://docs.px4.io/master/en/config/motors.html) (_PX4 User Guide_) -Buradan, PX4 için ek bilgiler bulabilirsiniz. +- [ESCS and Motors](https://ardupilot.org/copter/docs/connect-escs-and-motors.html#motor-order-diagrams) - This is the Motor order diagrams for all frames diff --git a/docs/tr/qgc-user-guide/setup_view/parameters.md b/docs/tr/qgc-user-guide/setup_view/parameters.md index b00c5339783..8941424c7b8 100644 --- a/docs/tr/qgc-user-guide/setup_view/parameters.md +++ b/docs/tr/qgc-user-guide/setup_view/parameters.md @@ -38,6 +38,6 @@ Ekranın sağ üstündeki **Tools** menüsünden ek seçenekler seçebilirsiniz. **Load from file / Save to file**
Parametreleri var olan bir dosyadan yükleyin veya mevcut parametre ayarlarınızı bir dosyaya kaydedin. -**Clear RC to Param**
Bu, RC verici kontrolleri ve parametreleri arasındaki tüm ilişkileri siler. Daha fazla bilgi için göz atın: [Radio Setup > Param Tuning Channels](../setup_view/Radio.md#param-tuning-channels-px4). +**Clear RC to Param**
Bu, RC verici kontrolleri ve parametreleri arasındaki tüm ilişkileri siler. For more information see: [Radio Setup > Param Tuning Channels](../setup_view/radio.md#param-tuning-channels-px4). **Reboot Vehicle**
Aracı yeniden başlatın (bazı parametre değişimlerinden sonra gereklidir). diff --git a/docs/tr/qgc-user-guide/setup_view/tuning_px4.md b/docs/tr/qgc-user-guide/setup_view/tuning_px4.md index 6be4cf09c36..03c07f319c9 100644 --- a/docs/tr/qgc-user-guide/setup_view/tuning_px4.md +++ b/docs/tr/qgc-user-guide/setup_view/tuning_px4.md @@ -36,7 +36,7 @@ To make sure the vehicle is stable enough for auto-tuning: 3. Use the RC transmitter roll stick to perform the following maneuver, tilting the vehicle just a few degrees: _roll left > roll right > center_ (The whole maneuver should take about 3 seconds). The vehicle should stabilise itself within 2 oscillations. 4. Repeat the maneuver, tilting with larger amplitudes at each attempt. - If the vehicle can stabilise itself within 2 oscillations at \~20 degrees move to the next step. + If the vehicle can stabilise itself within 2 oscillations at ~20 degrees move to the next step. 5. Repeat the same maneuvers but on the pitch axis. As above, start with small angles and confirm that the vehicle can itself within 2 oscillations before increasing the tilt. diff --git a/docs/tr/qgc-user-guide/viewer_3d/viewer_3d.md b/docs/tr/qgc-user-guide/viewer_3d/viewer_3d.md new file mode 100644 index 00000000000..f90339efe72 --- /dev/null +++ b/docs/tr/qgc-user-guide/viewer_3d/viewer_3d.md @@ -0,0 +1,53 @@ +# 3D View + +The 3D View is used to visualize and monitor the vehicle, the environment, and the planned mission in 3D. Most of the capabilities available in the [Fly View](../fly_view/fly_view.md) is also available in the 3D View. + +You can use it to: + +- To import and display the 3D map for any region of interest downloaded from the OpenStreetMap website (.osm file). +- Display the vehicle along with its mission in 3D. +- And most of the capabilities of the [Fly View](../fly_view/fly_view.md), including: + - Run an automated [pre-flight checklist](#preflight_checklist). + - Arm the vehicle (or check why it won't arm). + - Control missions: [start](#start_mission), [continue](#continue_mission), [pause](#pause), and [resume](#resume_mission). + - Guide the vehicle to [arm](#arm)/[disarm](#disarm)/[emergency stop](#emergency_stop), [takeoff](#takeoff)/[land](#land), [change altitude](#change_altitude), and [return/RTL](#rtl). + - Switch between a map view and a video view (if available) + - Display video, mission, telemetry, and other information for the current vehicle, and also switch between connected vehicles. + +![3D View](../../../assets/viewer_3d/viewer_3d_overview.jpg) + +# UI Overview + +The screenshot above shows the main elements of the 3D View. + +**Enabling the 3D View:** The 3D View is disabled by default. To enable it, go to **Application Settings** ->**Fly View** tab, and under the **3D View** settings group, toggle the **Enabled** switch as shown below: + +![3D View](../../../assets/viewer_3d/enable_3d_view.jpg) + +To open the 3D View, when you are in the [Fly View](../fly_view/fly_view.md), from the toolbar on the left, select the 3D View icon as illustrated below: + +![3D View](../../../assets/viewer_3d/open_3d_viewer.jpg) + +Once the 3D View is opened, you can navigate through the 3D environment by using either a mouse or a touchscreen as follows: + +- **Mouse:** + - **To move horizontally and vertically**: Press and hold the mouse left-click, then move the cursor. + - **To rotate**: Press and hold the mouse right-click, then move the cursor. + - **To zoom**: Use the mouse wheel\middle button. + +- **Touchscreen:** + - **To move horizontally and vertically**: Use a single finger, then tap and move your finger. + - **To rotate**: Use two fingers, then tap and move your fingers while keeping them together. + - **To zoom**: Use a pinch with two fingers and move them together or apart to zoom in or out. + +To visualize the 3D map of a particular area in the 3D viewer, you have to download the .osm file of that area from the [OpenStreetMap](https://www.openstreetmap.org/#map=16/47.3964/8.5498) website and then import it through the **3D View** settings. More details on the **3D View** settings can be found in the next section. + +# Settings + +You can change the settings of the 3D View from **Application Settings** ->**Fly View** tab under the **3D View** settings group. +The following properties can be modified in the 3D View settings group: + +- **Enabled**: To enable or disable the 3D View. +- **3D Map File**: The path to the .osm file of a region of interest to be visualized in the QGC. The .osm file can be uploaded by clicking on the **Select File** button. To clear the 3D View from the previously loaded .osm file, you can click on the **Clear** button. +- **Average Building Level Height**: This parameter determines the height of each storey of the buildings, as in .osm file sometimes the height of the buildings is specified in terms of the level/storey. +- **Vehicle Altitude Bias**: This refers to the bias in the altitude of vehicles and their missions with respect to the ground level. It is helpful in cases where the estimated altitude of the vehicle by its flight control is biased, as the relative altitude is currently used in the 3D View. diff --git a/docs/zh/SUMMARY.md b/docs/zh/SUMMARY.md index b1ac96f407e..9493285e911 100644 --- a/docs/zh/SUMMARY.md +++ b/docs/zh/SUMMARY.md @@ -2,14 +2,24 @@ - [Overview](qgc-user-guide/index.md) - [Quick Start](qgc-user-guide/getting_started/quick_start.md) - - [Download and Install](qgc-user-guide/getting_started/download_and_install.md) + - [Download and Install (Daily 5.0)](qgc-user-guide/releases/daily_builds.md) - [Support](qgc-user-guide/support/support.md) -- [Fly](qgc-user-guide/fly_view/fly_view.md) +- [Fly View](qgc-user-guide/fly_view/fly_view.md) + - [Toolbar](qgc-user-guide/fly_view/fly_view_toolbar.md) + - [Fly Tools](qgc-user-guide/fly_view/fly_tools.md) + - [Instrument Panel](qgc-user-guide/fly_view/instrument_panel.md) + - [Attitude/Compass](qgc-user-guide/fly_view/hud.md) + - [Camera Tools](qgc-user-guide/fly_view/camera_tools.md) + - [Video](qgc-user-guide/fly_view/video.md) + - [Video Overlay](qgc-user-guide/fly_view/video_overlay.md) - [Replay Flight Data](qgc-user-guide/fly_view/replay_flight_data.md) - - [Video Overlay](qgc-user-guide/fly_view/video_overlay.md) -- [Plan](qgc-user-guide/plan_view/plan_view.md) +- [Mavlink Actions](qgc-user-guide/custom_actions/custom_actions.md) + +- [3D View](qgc-user-guide/viewer_3d/viewer_3d.md) + +- [Plan Flight](qgc-user-guide/plan_view/plan_view.md) - [GeoFence](qgc-user-guide/plan_view/plan_geofence.md) - [Rally Points](qgc-user-guide/plan_view/plan_rally_points.md) - [Pattern](qgc-user-guide/plan_view/pattern.md) @@ -19,7 +29,7 @@ - [Fixed Wing Landing Pattern](qgc-user-guide/plan_view/pattern_fixed_wing_landing.md) - [Pattern Presets](qgc-user-guide/plan_view/pattern_presets.md) -- [Vehicle Setup](qgc-user-guide/setup_view/setup_view.md) +- [Vehicle Configuration](qgc-user-guide/setup_view/setup_view.md) - [Firmware](qgc-user-guide/setup_view/firmware.md) - [Airframe](qgc-user-guide/setup_view/airframe.md) - [Airframe (ArduPilot)](qgc-user-guide/setup_view/airframe_ardupilot.md) @@ -61,15 +71,13 @@ - [Releases](qgc-user-guide/releases/index.md) - [Release Notes](qgc-user-guide/releases/release_notes.md) - - [v4.0 (Additional Notes)](qgc-user-guide/releases/stable_v4.0_additional.md) - - [v3.3 (Detailed)](qgc-user-guide/releases/stable_v3.3_long.md) - - [v3.2 (Detailed)](qgc-user-guide/releases/stable_v3.2_long.md) + - [QGC v4 Release Notes](qgc-user-guide/releases/release_note_stable_v4.md) + - [QGC v3 Release Notes](qgc-user-guide/releases/release_note_stable_v3.md) - [Daily Builds](qgc-user-guide/releases/daily_builds.md) - [Daily Build New Features](qgc-user-guide/releases/daily_build_new_features.md) - [Privacy Policy](qgc-user-guide/releases/privacy_policy.md) - [Troubleshooting](qgc-user-guide/troubleshooting/index.md) - - [Setup Problems](qgc-user-guide/troubleshooting/qgc_setup.md) - [Usage Problems](qgc-user-guide/troubleshooting/qgc_usage.md) - [Connection problems](qgc-user-guide/troubleshooting/vehicle_connection.md) @@ -80,11 +88,11 @@ - [Developer's Guide](qgc-dev-guide/index.md) - [Getting Started with source & builds](qgc-dev-guide/getting_started/index.md) - [Build using Containers](qgc-dev-guide/getting_started/container.md) - - [Using QGC on CentOS](qgc-dev-guide/getting_started/cent_os.md) + - [Navigating the Source Code](qgc-dev-guide/navigating_source.md) + - [Class Hierarchy](qgc-dev-guide/classes/index.md) - [QGC Release/Branching Process](qgc-dev-guide/release_branching_process.md) - [Communication Flow](qgc-dev-guide/communication_flow.md) - [Plugin Architecture](qgc-dev-guide/firmware_plugin.md) - - [Class Hierarchy](qgc-dev-guide/classes/index.md) - [User Interface Design](qgc-dev-guide/user_interface_design/index.md) - [Multi-Device Design Pattern](qgc-dev-guide/user_interface_design/multi_device_pattern.md) - [Font and Colour Palette](qgc-dev-guide/user_interface_design/font_palette.md) @@ -114,7 +122,6 @@ - [Release/Branching Process For Custom Builds](qgc-dev-guide/custom_build/release_branching_process.md) - [MAVLink](qgc-dev-guide/custom_build/mavlink.md) - [Code Submission](qgc-dev-guide/contribute/index.md) - - [Developer Call](qgc-dev-guide/contribute/dev_call.md) - [Coding Style](qgc-dev-guide/contribute/coding_style.md) - [Unit Tests](qgc-dev-guide/contribute/unit_tests.md) - [Pull Requests](qgc-dev-guide/contribute/pull_requests.md) diff --git a/docs/zh/index.md b/docs/zh/index.md index b8879668485..d47fb61bae4 100644 --- a/docs/zh/index.md +++ b/docs/zh/index.md @@ -1,7 +1,7 @@ --- layout: home hero: - name: QGroundControl Guide + name: QGroundControl Guide (Daily Build 5.0) tagline: For beginners, experienced users, and developers actions: - theme: brand diff --git a/docs/zh/qgc-dev-guide/command_line_options.md b/docs/zh/qgc-dev-guide/command_line_options.md index ed78d6cc035..88bd147837a 100644 --- a/docs/zh/qgc-dev-guide/command_line_options.md +++ b/docs/zh/qgc-dev-guide/command_line_options.md @@ -30,16 +30,16 @@ Linux终端： 选项/命令行参数列在下表中。 -| 选项 | 描述 | -| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| `--clear-settings` | Clears the app settings (reverts _QGroundControl_ back to default settings). | -| `--logging:full` | Turns on full logging. See [Console Logging](../../qgc-user-guide/settings_view/console_logging.html#logging-from-the-command-line). | -| `--logging:full,LinkManagerVerboseLog,ParameterLoaderLog` | Turns on full logging and turns off the following listed comma-separated logging options. | -| `--logging:LinkManagerLog,ParameterLoaderLog` | Turns on the specified comma separated logging options | -| `--unittest:name` | (Debug builds only) Runs the specified unit test. Leave off `:name` to run all tests. | -| `--unittest-stress:name` | (Debug builds only) Runs the specified unit test 20 times in a row. Leave off :name to run all tests. | -| `--fake-mobile` | Simulates running on a mobile device. | -| `--test-high-dpi` | Simulates running _QGroundControl_ on a high DPI device. | +| 选项 | 描述 | +| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `--clear-settings` | Clears the app settings (reverts _QGroundControl_ back to default settings). | +| `--logging:full` | Turns on full logging. See [Console Logging](../../qgc-user-guide/settings_view/console_logging.html#logging-from-the-command-line). | +| `--logging:full,LinkManagerVerboseLog,ParameterLoaderLog` | Turns on full logging and turns off the following listed comma-separated logging options. | +| `--logging:LinkManagerLog,ParameterLoaderLog` | Turns on the specified comma separated logging options | +| `--unittest:name` | (Debug builds only) Runs the specified unit test. Leave off `:name` to run all tests. | +| `--unittest-stress:name` | (Debug builds only) Runs the specified unit test 20 times in a row. Leave off :name to run all tests. | +| `--fake-mobile` | Simulates running on a mobile device. | +| `--test-high-dpi` | Simulates running _QGroundControl_ on a high DPI device. | 笔记： diff --git a/docs/zh/qgc-dev-guide/contribute/unit_tests.md b/docs/zh/qgc-dev-guide/contribute/unit_tests.md index 8569f4cec87..46a7d52f916 100644 --- a/docs/zh/qgc-dev-guide/contribute/unit_tests.md +++ b/docs/zh/qgc-dev-guide/contribute/unit_tests.md @@ -6,7 +6,7 @@ _QGroundControl_ (QGC) contains a set of unit tests that must pass before a pull 要运行单元测试： -1. 使用QGC_UNITTEST_BUILD定义在调试模式下构建。 +1. Build in `debug` mode with `QGC_UNITTEST_BUILD` definition. 2. 复制debug目录中的deploy / qgroundcontrol-start.sh脚本 3. Run _all_ unit tests from the command line using the `--unittest` command line option. For Linux this is done as shown: diff --git a/docs/zh/qgc-dev-guide/custom_build/custom_build.md b/docs/zh/qgc-dev-guide/custom_build/custom_build.md index 8f8bce6fba7..dd7b2f484e2 100644 --- a/docs/zh/qgc-dev-guide/custom_build/custom_build.md +++ b/docs/zh/qgc-dev-guide/custom_build/custom_build.md @@ -1,6 +1,6 @@ # 自定义构建 -自定义构建允许第三方创建自己的QGC版本，使其能够轻松跟上常规QGC中所做的更改。 QGC has an architecture built into it which allows custom builds to modify and add to the feature set of regular QGC. custom-example](https\://github.com/mavlink/qgroundcontrol/tree/master/custom-example) source code including the +自定义构建允许第三方创建自己的QGC版本，使其能够轻松跟上常规QGC中所做的更改。 QGC has an architecture built into it which allows custom builds to modify and add to the feature set of regular QGC. custom-example](https://github.com/mavlink/qgroundcontrol/tree/master/custom-example) source code including the Some possibilities with a custom build diff --git a/docs/zh/qgc-dev-guide/custom_build/mavlink.md b/docs/zh/qgc-dev-guide/custom_build/mavlink.md index 6423c43a4bb..24883618f8e 100644 --- a/docs/zh/qgc-dev-guide/custom_build/mavlink.md +++ b/docs/zh/qgc-dev-guide/custom_build/mavlink.md @@ -10,6 +10,6 @@ In order to add support for a new set of messages you should add them to [develo To modify the version of MAVLink used by QGC: - Replace the pre-build C library at [/qgroundcontrol/libs/mavlink/include/mavlink](https://github.com/mavlink/qgroundcontrol/tree/master/libs/mavlink/include/mavlink). - - By default this is a submodule importing https\://github.com/mavlink/c_library_v2 + - By default this is a submodule importing https://github.com/mavlink/c_library_v2 - You can change the submodule, or [build your own libraries](https://mavlink.io/en/getting_started/generate_libraries.html) using the MAVLink toolchain. - You can change the whole dialect used by setting it in [`MAVLINK_CONF`](https://github.com/mavlink/qgroundcontrol/blob/master/QGCExternalLibs.pri#L52) when running _qmake_. diff --git a/docs/zh/qgc-dev-guide/custom_build/release_branching_process.md b/docs/zh/qgc-dev-guide/custom_build/release_branching_process.md index 44890d6b03a..9023e149488 100644 --- a/docs/zh/qgc-dev-guide/custom_build/release_branching_process.md +++ b/docs/zh/qgc-dev-guide/custom_build/release_branching_process.md @@ -8,7 +8,7 @@ The best place to start is understanding the mechanism QGC uses to do it's own r ## Custom build/release types -Regular QGC has two main build types: Stable and Daily. The build type for a custom build is more complex. Throughout this discussion we will use the term "upstream" to refer to the main QGC repo (https\://github.com/mavlink/qgroundcontrol). Also when we talk about a "new" upstream stable release, this means a major/minor release, not a patch release. +Regular QGC has two main build types: Stable and Daily. The build type for a custom build is more complex. Throughout this discussion we will use the term "upstream" to refer to the main QGC repo (https://github.com/mavlink/qgroundcontrol). Also when we talk about a "new" upstream stable release, this means a major/minor release, not a patch release. ### Synchronized Stable diff --git a/docs/zh/qgc-dev-guide/custom_build/resource_override.md b/docs/zh/qgc-dev-guide/custom_build/resource_override.md index 2c8fa94eba1..37a3fdd7d01 100644 --- a/docs/zh/qgc-dev-guide/custom_build/resource_override.md +++ b/docs/zh/qgc-dev-guide/custom_build/resource_override.md @@ -1,8 +1,12 @@ # Resource Overrides -A "resource" in QGC source code terminology is anything found in the [qgroundcontrol.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgroundcontrol.qrc) and [qgcresources.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgcresources.qrc) file. By overriding a resource you can replace it with your own version of it. This could be as simple as a single icon, or as complex as replacing an entire Vehicle Setup page of qml ui code. +A "resource" in QGC source code terminology is anything found in Qt resources file: -Be aware that using resource overrides does not isolate you from upstream QGC changes like the plugin architecture does. In a sense you are directly modify the upstream QGC resources used by the main code. +- [qgroundcontrol.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgroundcontrol.qrc) and +- [qgcresources.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgcresources.qrc) file. +- [InstrumentValueIcons.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/resources/InstrumenValueIcons/InstrumentValueIcons.qrc) + +By overriding a resource you can replace it with your own version of it. This could be as simple as a single icon, or as complex as replacing an entire Vehicle Setup page of qml ui code. Be aware that using resource overrides does not isolate you from upstream QGC changes like the plugin architecture does. In a sense you are directly modify the upstream QGC resources used by the main code. ## Exclusion Files @@ -14,7 +18,7 @@ You must include the custom version of the overriden resouce in you custom build ## Generating the new modified versions of standard QGC resource file -This is done using the `updateqrc.py` python script. It will read the upstream `qgroundcontrol.qrc` and `qgcresources.qrc` file and the corresponding exclusion files and output new versions of these files in your custom directory. These new versions will not have the resources you specified to exclude in them. The build system for custom builds uses these generated files (if they exist) to build with instead of the upstream versions. The generated version of these file should be added to your repo. Also whenever you update the upstream portion of QGC in your custom repo you must re-run `python updateqrc.py` to generate new version of the files since the upstream resources may have changed. +This is done using the resource update python scripts:`python updateqrc.py` and `python updateinstrumentqrc.py`. It will read the upstream resouce files and the corresponding exclusion files and output new versions of these files in your custom directory. These new versions will not have the resources you specified to exclude in them. The build system for custom builds uses these generated files (if they exist) to build with instead of the upstream versions. The generated version of these file should be added to your repo. Also whenever you update the upstream portion of QGC in your custom repo you must re-run the scripts to generate new versions of the files since the upstream resources may have changed. ## Custom Build Example diff --git a/docs/zh/qgc-dev-guide/file_formats/plan.md b/docs/zh/qgc-dev-guide/file_formats/plan.md index ada8951044c..288140f8798 100644 --- a/docs/zh/qgc-dev-guide/file_formats/plan.md +++ b/docs/zh/qgc-dev-guide/file_formats/plan.md @@ -82,15 +82,15 @@ The list may be a mix of both [SimpleItem](#mission_simple_item) and [ComplexIte 需要以下值： -| 键 | 描述 | -| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `version` | 任务对象的版本。 目前的版本是2。 Current version is 2. | -| `firmwareType` | 为此任务创建的固件类型。 这是MAV_AUTOPILOT枚举值之一。 This is one of the [MAV_AUTOPILOT](https://mavlink.io/en/messages/common.html#MAV_AUTOPILOT) enum values. | -| `globalPlanAltitudeMode` | The global plan-wide altitude mode setting. This is used by plan items that don't specify an `"AltitudeMode"`. | -| `vehicleType` | The vehicle type for which this mission was created. This is one of the [MAV_TYPE](https://mavlink.io/en/messages/common.html#MAV_TYPE) enum values. | +| 键 | 描述 | +| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `version` | 任务对象的版本。 目前的版本是2。 Current version is 2. | +| `firmwareType` | 为此任务创建的固件类型。 这是MAV_AUTOPILOT枚举值之一。 This is one of the [MAV_AUTOPILOT](https://mavlink.io/en/messages/common.html#MAV_AUTOPILOT) enum values. | +| `globalPlanAltitudeMode` | The global plan-wide altitude mode setting. This is used by plan items that don't specify an `"AltitudeMode"`. | +| `vehicleType` | The vehicle type for which this mission was created. This is one of the [MAV_TYPE](https://mavlink.io/en/messages/common.html#MAV_TYPE) enum values. | | `cruiseSpeed` | The default forward speed for Fixed wing or VTOL vehicles (i.e. when moving between waypoints). | -| `hoverSpeed` | The default forward speed for multi-rotor vehicles. | -| `items` | The list of mission item objects associated with the mission . The list may contain either/both [SimpleItem](#mission_simple_item) and [ComplexItem](#mission_complex_item) objects. | +| `hoverSpeed` | The default forward speed for multi-rotor vehicles. | +| `items` | The list of mission item objects associated with the mission . The list may contain either/both [SimpleItem](#mission_simple_item) and [ComplexItem](#mission_complex_item) objects. | | `plannedHomePosition` | The planned home position is shown on the map and used for mission planning when no vehicle is connected. The array values shown above are (from top): latitude, longitude and AMSL altitude. | 简单和复杂项目的格式如下。 @@ -123,17 +123,17 @@ The list may be a mix of both [SimpleItem](#mission_simple_item) and [ComplexIte 字段映射如下所示。 -| 键 | 描述 | -| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `type` | SimpleItem用于简单的项目 | -| `AMSLAltAboveTerrain` | 向用户显示的海拔高度值。 | -| `Altitude` | | -| `AltitudeMode` | | -| `autoContinue` | MISSION_ITEM.autoContinue | +| 键 | 描述 | +| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type` | SimpleItem用于简单的项目 | +| `AMSLAltAboveTerrain` | 向用户显示的海拔高度值。 | +| `Altitude` | | +| `AltitudeMode` | | +| `autoContinue` | MISSION_ITEM.autoContinue | | `command` | The command ([MAV_CMD](https://mavlink.io/en/messages/common.html#MAV_CMD)) for this mission item - see [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).command. | -| `doJumpId` | DO_JUMP命令中当前任务项的目标ID。 这些是从1自动编号。 These are auto-numbered from 1. | -| `frame` | [MAV_FRAME](https://mavlink.io/en/messages/common.html#MAV_FRAME) (see [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).frame) | -| `params` | MISSION_ITEM.param1,2,3,4，x，y，z（值取决于特定的MAV_CMD）。 | +| `doJumpId` | DO_JUMP命令中当前任务项的目标ID。 这些是从1自动编号。 These are auto-numbered from 1. | +| `frame` | [MAV_FRAME](https://mavlink.io/en/messages/common.html#MAV_FRAME) (see [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM).frame) | +| `params` | MISSION_ITEM.param1,2,3,4，x，y，z（值取决于特定的MAV_CMD）。 | ### 复杂任务项目 {#mission_complex_item} @@ -176,16 +176,16 @@ The list may be a mix of both [SimpleItem](#mission_simple_item) and [ComplexIte 复杂项目具有与之关联的这些值： -| 键 | 描述 | -| -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `version` | The version number for this `survey` definition. Current version is 3. | -| `type` | ComplexItem（这是一个复杂的项目）。 | -| `complexItemType` | `survey` | -| [`TransectStyleComplexItem `](#TransectStyleComplexItem) | Survey和CorridorScan复杂项目的通用基础定义。 | -| `angle` | 横断面的角度（度数）。 | -| `entryLocation` | ? | +| 键 | 描述 | +| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `version` | The version number for this `survey` definition. Current version is 3. | +| `type` | ComplexItem（这是一个复杂的项目）。 | +| `complexItemType` | `survey` | +| [`TransectStyleComplexItem `](#TransectStyleComplexItem) | Survey和CorridorScan复杂项目的通用基础定义。 | +| `angle` | 横断面的角度（度数）。 | +| `entryLocation` | ? | | `flyAlternateTransects` | 团结积分信息是可选的。 该计划可以包含任意数量的拉力点，每个拉力点具有纬度，经度和高度（高于原始位置）。 如果是，则载具会跳过每个其他横断面，然后在最后返回并飞行这些替代。 This can be used for fixed wing aircraft when the turnaround would be too acute for the vehicle to make the turn. | -| `polygon` | The polygon array which represents the polygonal survey area. Each point is a latitude, longitude pair for a polygon vertex. | +| `polygon` | The polygon array which represents the polygonal survey area. Each point is a latitude, longitude pair for a polygon vertex. | #### 走廊扫描 {#corridor_scan} @@ -216,15 +216,15 @@ CorridorScan复杂任务项的对象定义如下。 }, ``` -| 键 | 描述 | -| -------------------------------------------------------- | -------------------------------------------------- | +| 键 | 描述 | +| -------------------------------------------------------- | ------------------------------------------------------------------ | | `version` | 此CorridorScan定义的版本。 目前的版本是3。 Current version is 3. | -| `type` | ComplexItem（这是一个复杂的项目）。 | -| `complexItemType` | `CorridorScan` | -| `CorridorWidth` | ? | -| `EntryPoint` | ? | -| [`TransectStyleComplexItem `](#TransectStyleComplexItem) | Survey和CorridorScan复杂项目的通用基础定义。 | -| `polyline` | ? | +| `type` | ComplexItem（这是一个复杂的项目）。 | +| `complexItemType` | `CorridorScan` | +| `CorridorWidth` | ? | +| `EntryPoint` | ? | +| [`TransectStyleComplexItem `](#TransectStyleComplexItem) | Survey和CorridorScan复杂项目的通用基础定义。 | +| `polyline` | ? | #### 结构扫描 {#structure_scan} @@ -261,17 +261,17 @@ StructureScan复杂任务项的对象定义如下。 } ``` -| 键 | 描述 | -| --------------------------- | --------------------------------------------------- | -| `version` | 此StructureScan定义的版本。 目前的版本是2。 Current version is 2. | -| `type` | ComplexItem（这是一个复杂的项目）。 | -| `complexItemType` | `StructureScan` | -| `Altitude` | ? | -| [`CameraCalc`](#CameraCalc) | ? | -| `Layers` | ? | -| `StructureHeight` | ? | -| `altitudeRelative` | true: altitude相对于主页，false: altitude是AMSL。 | -| `polygon` | ? | +| 键 | 描述 | +| --------------------------- | ------------------------------------------------------------------------- | +| `version` | 此StructureScan定义的版本。 目前的版本是2。 Current version is 2. | +| `type` | ComplexItem（这是一个复杂的项目）。 | +| `complexItemType` | `StructureScan` | +| `Altitude` | ? | +| [`CameraCalc`](#CameraCalc) | ? | +| `Layers` | ? | +| `StructureHeight` | ? | +| `altitudeRelative` | true: altitude相对于主页，false: altitude是AMSL。 | +| `polygon` | ? | #### `TransectStyleComplexItem ` {#TransectStyleComplexItem} @@ -344,26 +344,26 @@ CameraCalc包含用于调查，走廊或结构扫描的摄像机信息。 }, ``` -| 键 | 描述 | -| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `version` | 此CameraCalc定义的版本。 当前版本为1。 此调查定义的版本号。 目前的版本是3。 | -| `AdjustedFootprintFrontal` | ? | -| `AdjustedFootprintSide` | ? | -| `DistanceToSurface` | ? 单位? | -| `DistanceToSurfaceRelative` | ? | +| 键 | 描述 | +| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `version` | 此CameraCalc定义的版本。 当前版本为1。 此调查定义的版本号。 目前的版本是3。 | +| `AdjustedFootprintFrontal` | ? | +| `AdjustedFootprintSide` | ? | +| `DistanceToSurface` | ? 单位? | +| `DistanceToSurfaceRelative` | ? | | `CameraName` | 正在使用的摄像机名称（必须对应于QGroundControl已知的摄像机之一或： Manual (no camera specs) (手动（无摄像机规格）用于手动设置， Custom Camera (自定义摄像机)用于自定义设置。 未在“手动”摄像机定义中指定此点后列出的键。 The keys listed after this point are not specified for a "Manual" camera definition. | -| `FixedOrientation` | ? （布尔值） | -| `FocalLength` | 相机镜头的焦距，以毫米为单位。 | -| `FrontalOverlap` | 正面图像重叠的百分比。 | -| `ImageDensity` | ? | -| `ImageHeight` | 图像高度以px为单位 | -| `ImageWidth` | 图像宽度以px为单位 | -| `景观` | true：相机以横向方向安装在载具上，false：相机以纵向方向安装在载具上。 | -| `MinTriggerInterval` | ? | -| `SensorHeight` | 传感器高度，以毫米为单位。 | -| `SensorWidth` | 传感器宽度，以毫米为单位。 | -| `SideOverlap` | 侧面图像重叠的百分比。 | -| `ValueSetIsDistance` | ? （布尔值） | +| `FixedOrientation` | ? （布尔值） | +| `FocalLength` | 相机镜头的焦距，以毫米为单位。 | +| `FrontalOverlap` | 正面图像重叠的百分比。 | +| `ImageDensity` | ? | +| `ImageHeight` | 图像高度以px为单位 | +| `ImageWidth` | 图像宽度以px为单位 | +| `景观` | true：相机以横向方向安装在载具上，false：相机以纵向方向安装在载具上。 | +| `MinTriggerInterval` | ? | +| `SensorHeight` | 传感器高度，以毫米为单位。 | +| `SensorWidth` | 传感器宽度，以毫米为单位。 | +| `SideOverlap` | 侧面图像重叠的百分比。 | +| `ValueSetIsDistance` | ? （布尔值） | ## GeoFence (地理围栏) {#geofence} @@ -384,11 +384,11 @@ The plan can contain an arbitrary number of geofences defined in terms of polygo 主要领域是： -| 键 | 描述 | -| ------------------------------ | ----------------------------------------------------------------------------- | +| 键 | 描述 | +| ------------------------------ | ------------------------------------------------------------------------------------------------------------- | | `version` | The version number for the geofence plan format. The documented version is 2. | -| [`circles`](#circle_geofence) | 包含圆形地理围栏定义的列表（以逗号分隔）。 | -| [`polygon`](#polygon_geofence) | 包含多边形地理围栏定义的列表（以逗号分隔）。 | +| [`circles`](#circle_geofence) | 包含圆形地理围栏定义的列表（以逗号分隔）。 | +| [`polygon`](#polygon_geofence) | 包含多边形地理围栏定义的列表（以逗号分隔）。 | ### Circle Geofence (圆形地理围栏) {#circle_geofence} @@ -408,11 +408,11 @@ The items define the centre and radius of the circle, and whether or not the spe 主要领域是： -| 键 | 描述 | -| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | +| 键 | 描述 | +| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `version` | The version number for the geofence "circle" plan format. 拉力点计划格式的版本号。 记录的版本是2。 | | `circle` | 圆的定义。 包括 centre (中心)（纬度，经度）和半径，如上所示。 Includes `centre` (latitude, longitude) and `radisu` as shown above. | -| `inclusion` | 地理围栏是否已启用（true）或已禁用。 | +| `inclusion` | 地理围栏是否已启用（true）或已禁用。 | ### 多边形地理围栏 {#polygon_geofence} @@ -449,11 +449,11 @@ The geofence includes a set of points defined with a clockwise winding (i.e. the 这些领域是： -| 键 | 描述 | -| ----------- | ------------------------------------------------------------------------------------------------------------------------------ | -| `version` | The version number for the geofence "polygon" plan format. The documented version is 2. | +| 键 | 描述 | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `version` | The version number for the geofence "polygon" plan format. The documented version is 2. | | `polygon` | A list of points for the polygon. Each point contains a latitude and longitude. The points are ordered in a clockwise winding. | -| `inclusion` | 地理围栏是否已启用（true）或已禁用。 | +| `inclusion` | 地理围栏是否已启用（true）或已禁用。 | ## 团结积分 {#rally_points} @@ -482,7 +482,7 @@ The plan can contain an arbitrary number of rally points, each of which has a la 这些领域是： -| 键 | 描述 | -| --------- | -------------------------------------------------------------------------------- | +| 键 | 描述 | +| --------- | ---------------------------------------------------------------------------------------------------------------- | | `version` | The version number for the rally point plan format. The documented version is 2. | -| `points` | 拉力点列表。 | +| `points` | 拉力点列表。 | diff --git a/docs/zh/qgc-dev-guide/getting_started/container.md b/docs/zh/qgc-dev-guide/getting_started/container.md index 3bdda672439..5baae13faa7 100644 --- a/docs/zh/qgc-dev-guide/getting_started/container.md +++ b/docs/zh/qgc-dev-guide/getting_started/container.md @@ -12,11 +12,21 @@ The main advantage of using the container is the usage of the `CMake` build syst ## Building the Container -Before using the container, you have to build the image. +### Script + +To build the container using the script, run this command in the qgc root directory + +``` +./deploy/docker/run-docker-ubuntu.sh +``` + +### Manual + +if you want to Build using the container manually, then you first have to build the image. You can accomplish this using docker, running the following script from the root of the QGC source code directory. ``` -docker build --file ./deploy/docker/Dockerfile-build-linux -t qgc-linux-docker . +docker build --file ./deploy/docker/Dockerfile-build-ubuntu -t qgc-ubuntu-docker . ``` :::info @@ -28,7 +38,7 @@ Keep in mind this is tagging the image for later reference since you can have mu If building on a Mac computer with an M1 chip you must also specify the build option `--platform linux/x86_64` as shown: ``` -docker build --platform linux/x86_64 --file ./deploy/docker/Dockerfile-build-linux -t qgc-linux-docker . +docker build --platform linux/x86_64 --file ./deploy/docker/Dockerfile-build-ubuntu -t qgc-ubuntu-docker . ``` Otherwise you will get a build error like: @@ -46,15 +56,20 @@ We recommend you create a `build` directory on the source tree and then run the ``` mkdir build -docker run --rm -v ${PWD}:/project/source -v ${PWD}/build:/project/build qgc-linux-docker +docker run --rm -v ${PWD}:/project/source -v ${PWD}/build:/project/build qgc-ubuntu-docker ``` +::: info +For up to date docker command and options reference relevant run-script in `deploy/docker`, for example [run-docker-ubuntu.sh](https://github.com/mavlink/qgroundcontrol/blob/master/deploy/docker/run-docker-ubuntu.sh#L16). + +::: + ::: info If using the script to build the Linux image on a Windows host, you would need to reference the PWD differently. On Windows the docker command is: ``` -docker run --rm -v %cd%:/project/source -v %cd%/build:/project/build qgc-linux-docker +docker run --rm -v %cd%:/project/source -v %cd%/build:/project/build qgc-ubuntu-docker ``` ::: diff --git a/docs/zh/qgc-dev-guide/getting_started/index.md b/docs/zh/qgc-dev-guide/getting_started/index.md index ade11e31625..61e876c3469 100644 --- a/docs/zh/qgc-dev-guide/getting_started/index.md +++ b/docs/zh/qgc-dev-guide/getting_started/index.md @@ -1,5 +1,5 @@ --- -qt_version: 6.6.1 +qt_version: 6.8.2 --- # Getting Started with Source and Builds @@ -14,7 +14,7 @@ Versions are provided for all platforms. ## 源代码 -_QGroundControl_ 的源代码保存在 github 上，下载地址为: https\://github.com/mavlink/qgroundcontrol。 QGroundControl源代码在Apache 2.0和GPLv3下是双许可的。 有关更多信息，请参阅：许可证。 +_QGroundControl_ 的源代码保存在 github 上，下载地址为: https://github.com/mavlink/qgroundcontrol。 QGroundControl源代码在Apache 2.0和GPLv3下是双许可的。 有关更多信息，请参阅：许可证。 It is [dual-licensed under Apache 2.0 and GPLv3](https://github.com/mavlink/qgroundcontrol/blob/master/.github/COPYING.md). 要获取源文件, 请执行以下操作: @@ -58,139 +58,97 @@ There is a significant risk that other Qt versions will inject bugs that affect For more information see: [Qt 6 supported platform list](https://doc.qt.io/qt-6/supported-platforms.html). -:::info -Native [CentOS Builds](../getting_started/cent_os.md) are also supported, but are documented separately (as the tested environment is different). -::: - #### 安装Qt You **must install Qt as described below** instead of using pre-built packages from say, a Linux distribution. To install Qt: -1. 下载并运行[Qt Online Installer](http://www.qt.io/download-open-source) +1. Download and run the [Qt Online Installer](https://www.qt.io/download-qt-installer-oss) - **Ubuntu:** - 使用以下命令将下载的文件设置为可执行文件：`chmod + x` - - You may also need to install libxcb-cursor. - -2. In the installer _Select Components_ dialog choose: Qt {{ $frontmatter.qt_version }}. - - Then install the following components: - - - Under _Qt _{{ $frontmatter.qt_version }}_ select: - - Depending on the OS you want to build for: - - **Windows**: _MSVC 2019 64 bit_ - - **MacOS**: _macOS_ - - **Linux**: _Desktop gcc 64-bit_ - - **Android**: _Android_ - - _Qt 5 Compatibility Module_ - - _Qt Shader Tools_ - - Under _Additional Libraries_ select: - - _Qt Charts_ - - _Qt Connectivity_ - - _Qt Location (TP)_ - - _Qt Multimedia_ - - _Qt Positioning_ - - _Qt Serial Port_ - - _Qt Speech_ - -3. Install Additional Packages (Platform Specific) - - - **Ubuntu:** `sudo apt-get install speech-dispatcher libudev-dev libsdl2-dev patchelf build-essential` - - **Fedora:** `sudo dnf install speech-dispatcher SDL2-devel SDL2 systemd-devel patchelf` - - **Arch Linux:** `pacman -Sy speech-dispatcher patchelf` - - **OSX** [Setup](https://doc.qt.io/qt-6/macos.html) - - **Android** [Setup](https://doc.qt.io/qt-6/android-getting-started.html) - -4. Install Optional/OS-Specific Functionality - - Optional features that are dependent on the operating system and user-installed libraries are linked/described below. - These features can be forcibly enabled/disabled by specifying additional values to qmake. - ::: + - You may also need to install libxcb-cursor0 - - - **Video Streaming/Gstreamer:** - see [Video Streaming](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoReceiver/README.md). - - **Airmap SDK:** - TBD. +2. On the _Installation Folder_ page select "Custom Installation" -#### Building using Qt Creator {#qt-creator} - -1. Launch _Qt Creator_ and open the **qgroundcontrol.pro** project. - -2. In the **Projects** section, select the appropriate kit for your needs: +3. On the _Select Components_ page: - - **OSX:** Desktop Qt {{ $frontmatter.qt_version }} clang 64 bit + - I you don't see _Qt {{ $frontmatter.qt_version }}_ listed check the _Archive_ checkbox and click _Filter_. - ::: info - iOS builds must be built using [XCode](http://doc.qt.io/qt-5/ios-support.html). - ::: +- Under Qt -> _Qt {{ $frontmatter.qt_version }}_ select: + - **Windows**: MSVC 2022 _arch_ - where _arch_ is the architecture of your machine + - **Mac**: Desktop + - **Linux**: Desktop gcc 64-bit + - **Android**: Android +- Select all _Additional Libraries_ +- Deselect QT Design Studio - - **Ubuntu:** Desktop Qt {{ $frontmatter.qt_version }} GCC 64bit +1. Install Additional Packages (Platform Specific) - - **Windows:** Desktop Qt {{ $frontmatter.qt_version }} MSVC2019 **64bit** + - **Ubuntu:** `sudo bash ./qgroundcontrol/tools/setup/install-dependencies-debian.sh` + - **Fedora:** `sudo dnf install speech-dispatcher SDL2-devel SDL2 systemd-devel patchelf` + - **Arch Linux:** `pacman -Sy speech-dispatcher patchelf` + - **Mac** `sh qgroundcontrol/tools/setup/macos-dependencies.sh` + - **Android** [Setup](https://doc.qt.io/qt-6/android-getting-started.html). JDK17 is required for the latest updated versions. NDK Version: 25.1.8937393 + You can confirm it is being used by reviewing the project setting: **Projects > Manage Kits > Devices > Android (tab) > Android Settings > _JDK location_**. + Note: Visit here for more detailed configurations [android.yml](.github/workflows/android.yml) - - **Android:** Android for armeabi-v7a (GCC 4.9, Qt {{ $frontmatter.qt_version }}) - - JDK11 is required. - You can confirm it is being used by reviewing the project setting: **Projects > Manage Kits > Devices > Android (tab) > Android Settings > _JDK location_**. +2. Install Optional/OS-Specific Functionality -3. Build using the "hammer" (or "play") icons: + Optional features that are dependent on the operating system and user-installed libraries are linked/described below. + These features can be forcibly enabled/disabled by specifying additional values to qmake. + ::: - ![QtCreator Build Button](../../../assets/dev_getting_started/qt_creator_build_qgc.png) + - **Video Streaming/Gstreamer:** - see [Video Streaming](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoManager/VideoReceiver/GStreamer/README.md) -#### Install Visual Studio 2019 (Windows Only) {#vs} +#### Install Visual Studio (Windows Only) {#vs} -The Windows compiler can be found here: [Visual Studio 2019 compiler](https://visualstudio.microsoft.com/vs/older-downloads/) (64 bit) +Install [Visual Studio 2022 Community Edition](https://visualstudio.microsoft.com/downloads/). When installing, select _Desktop development with C++_ as shown: ![Visual Studio 2019 - Select Desktop Environment with C++](../../../assets/dev_getting_started/visual_studio_select_features.png) :::info -Visual Studio is ONLY used to get the compiler. Actually building _QGroundControl_ should be done using [Qt Creator](#qt-creator) or [qmake](#qmake) as outlined below. +Visual Studio is ONLY used to get the compiler. Building _QGroundControl_ is done using [Qt Creator](#qt-creator) or [cmake](#cmake) directly as outlined below. ::: -#### Build using qmake on CLI {#qmake} +#### Building using Qt Creator {#qt-creator} -Example commands to build a default QGC and run it afterwards: +1. Launch _Qt Creator_, select Open Project and select the **CMakeLists.txt** file. -1. Make sure you cloned the repository and updated the submodules before, see chapter _Source Code_ above and switch into the repository folder: `cd qgroundcontrol` +2. On the _Configure Project_ page it should default to the version of Qt you just installed using the instruction above. If not select that kit from the list and click _Configure Project_. - ```sh - cd qgroundcontrol - ``` +3. Build using the "hammer" (or "play") icons or the menus: -2. Create and enter a shadow build directory: + ![QtCreator Build Button](../../../assets/dev_getting_started/qt_creator_build_qgc.png) - ```sh - mkdir build - cd build - ``` +#### Build using CMake on CLI {#cmake} -3. Configure the build using the qmake script in the root of the repository: `qmake ../` +Example commands to build a default QGC and run it afterwards: + +1. Make sure you cloned the repository and updated the submodules before, see chapter _Source Code_ above and switch into the repository folder: `cd qgroundcontrol` ```sh - 入门指南 + cd qgroundcontrol ``` -4. Run make to compile and link. - To accelerate the process things you can use the `-j{number of threads}` parameter. +2. Configure: ```sh - `make -j12` + cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Debug ``` - ::: info - You can also specify build time flags here. - For example, you could disable airmap inclusion using the command: +3. Build ```sh - DEFINES+=DISABLE_AIRMAP make build + cmake --build build --config Debug ``` - ::: - -5. Run the QGroundcontrol binary that was just built: `./staging/QGroundControl` +4. Run the QGroundcontrol binary that was just built: `./staging/QGroundControl` ```sh - ./staging/QGroundControl + ./build/Debug/QGroundControl ``` ### Vagrant @@ -211,13 +169,6 @@ Example commands to build a default QGC and run it afterwards: You can additionally create installation file(s) for _QGroundControl_ as part of the normal build process. -:::tip -On Windows you will need to first install [NSIS](https://sourceforge.net/projects/nsis/). -::: - -To add support for installation file creation you need to add `CONFIG+=installer` to your project file, or when you call _qmake_. - -To do this in _Qt Creator_: - -- Open **Projects > Build > Build Steps > qmake > Additional arguments**. -- Enter `CONFIG+=installer` as shown: ![Installer](../../../assets/dev_getting_started/qt_project_installer.png) +```sh +cmake --install . --config Release +``` diff --git a/docs/zh/qgc-dev-guide/index.md b/docs/zh/qgc-dev-guide/index.md index e5ae8925202..fd3f15743e2 100644 --- a/docs/zh/qgc-dev-guide/index.md +++ b/docs/zh/qgc-dev-guide/index.md @@ -1,6 +1,7 @@ # QGroundControl开发指南 -[![版本发布](https://img.shields.io/github/release/mavlink/QGroundControl.svg)](https://github.com/mavlink/QGroundControl/releases) [![Discuss](https://img.shields.io/badge/discuss-dev-ff69b4.svg)](http://discuss.px4.io/c/qgroundcontrol/qgroundcontrol-developers) +[![Discuss](https://img.shields.io/badge/discuss-dev-ff69b4.svg)](http://discuss.px4.io/c/qgroundcontrol/qgroundcontrol-developers) +[![Discord](https://discordapp.com/api/guilds/1022170275984457759/widget.png?style=shield)](https://discord.com/channels/1022170275984457759/1022185820683255908) 如果要构建，修改或扩展QGroundControl（QGC），此开发人员指南是获取信息的最佳来源。 它展示了如何获取和构建源代码，解释了QGC的工作原理，并提供了为项目贡献代码的指南。 It shows how to obtain and build the source code, explains how QGC works, and provides guidelines for contributing code to the project. @@ -11,14 +12,14 @@ This part of the guide is for **developers**! :::warning This is an active work in progress - information should be correct, but may not be complete! -If you find that it is missing helpful information (or errors) please raise an issue. +If you find that it is missing helpful information (or errors) please raise an issue or better yet submit a pull request to the docs with updated information. ::: ## 设计理念 QGC 的设计是为了提供一个能够跨越多个操作系统平台以及多种设备的单个代码库。 -QGC 用户界面使用[Qt QML](http://doc.qt.io/qt-5/qtqml-index.html)实现。 QML提供硬件加速，这是平板电脑或手机等低功率设备的关键功能。 QML还提供了一些功能，使我们能够更轻松地创建单个用户界面，以适应不同的屏幕尺寸和分辨率。 QML provides for hardware acceleration which is a key feature on lower powered devices such as tablets or phones. QML also provides features which allows us to more easily create a single user interface which can adapt itself to differing screen sizes and resolution. +The QGC user interface is implemented using Qt Qml. Qml provides for hardware acceleration which is a key feature on lower powered devices such as tablets or phones. Qml also provides features which allows us to more easily create a single user interface which can adapt itself to differing screen sizes and resolution. 与基于桌面鼠标的UI相比，QGC UI更倾向于平板电脑+触摸式UI。 这使得单个UI更容易创建，因为平板电脑样式UI也可以在台式机/笔记本电脑上正常工作。 This make a single UI easier to create since tablet style UI also tends to work fine on desktop/laptops. @@ -35,10 +36,6 @@ We expect all contributors to adhere to the [QGroundControl code of conduct](htt This code aims to foster an open and welcoming environment. ::: -### Coordination Call - -The developer team meets bi-weekly to discuss the highest priority issues, project coordination, and discuss any Issues, PRs, or Questions from the Community. ([Developer Call Details](contribute/dev_call.md)) - ### Translations We use [Crowdin](https://crowdin.com) to make it easier to manage translation for both _QGroundControl_ and the documentation. @@ -61,8 +58,6 @@ For more information see: [Licenses](contribute/licences.md). ## 管理 -The QGroundControl mission planner is hosted under the governance of the [Dronecode Project](https://www.dronecode.org/). - -Dronecode Logo Linux Foundation Logo +The QGroundControl ground station is hosted under the governance of the [Dronecode Project](https://www.dronecode.org/).
 
diff --git a/docs/zh/qgc-dev-guide/navigating_source.md b/docs/zh/qgc-dev-guide/navigating_source.md new file mode 100644 index 00000000000..b8a3657e034 --- /dev/null +++ b/docs/zh/qgc-dev-guide/navigating_source.md @@ -0,0 +1,20 @@ +# Navigating QGC Source Code + +QGC is a large code base. With that it can be daunting to find what your are looking for in the source. Below are listed some tips to help you find what you are looking for. + +## Start from the top of the UI + +The top level window Qml UI code is found in `MainRootWindow.qml`. You can start here and work your way down through the UI hierarchy till you find what you are looking for. + +In this qml file you'll find things like: + +- How the toolbar is created +- How the top level views are created: Fly, Plan, ... + +## Global Search + +The best way to find something is to find the UI which is closest to what you are looking for by doing text searches. + +### Example: Find the source for the GPS drop down in the toolbar + +In the dropdown you see the words "Vehicle GPS Status". Do a global search for those words. Make sure you are doing a case sensitive search. Also make sure you are matching whole words. It can also be helpful to exclude the `*.ts` translation files. Since they can lead to multiple results. If you do the search described here it will take you right to `GPSIndicatorPage.qml`. Some times a search may lead to many results in both qml and .cpp files. In this case limit the results to `*.qml` files. diff --git a/docs/zh/qgc-dev-guide/plan/mission_command_tree.md b/docs/zh/qgc-dev-guide/plan/mission_command_tree.md index 55441b4e3fc..80dddd367dd 100644 --- a/docs/zh/qgc-dev-guide/plan/mission_command_tree.md +++ b/docs/zh/qgc-dev-guide/plan/mission_command_tree.md @@ -83,7 +83,7 @@ Let's walk through an example hierarchy for `MAV_CMD_NAV_WAYPOINT`. Root informa ### Root - Vehicle Type Specific leaf node -The next level of the hiearchy is generic mavlink but vehicle specific. Json files are here: [MR](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoMultiRotor.json), [FW](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoFixedWing.json), [ROVER](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoRover.json), [Sub](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoSub.json), [VTOL](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoVTOL.json). And here are the overrides for (Fixed Wings)(https\://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoFixedWing.json#L7): +The next level of the hiearchy is generic mavlink but vehicle specific. Json files are here: [MR](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoMultiRotor.json), [FW](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoFixedWing.json), [ROVER](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoRover.json), [Sub](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoSub.json), [VTOL](https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoVTOL.json). And here are the overrides for (Fixed Wings)(https://github.com/mavlink/qgroundcontrol/blob/master/src/MissionManager/MavCmdInfoFixedWing.json#L7): ``` { diff --git a/docs/zh/qgc-dev-guide/release_branching_process.md b/docs/zh/qgc-dev-guide/release_branching_process.md index da2a0671f6c..0b65a5d4cd8 100644 --- a/docs/zh/qgc-dev-guide/release_branching_process.md +++ b/docs/zh/qgc-dev-guide/release_branching_process.md @@ -74,7 +74,8 @@ A proposed strategy for branching on custom builds can be found [here](custom_bu 2. Create a tag on the HEAD of master name `dX.Y` where the minor version is one greater than the new Stable. For example if you are create a new Stable 4.2 version then the tag would be 'd4.3'. This tag is used to create the version numbers for Android daily builds. Example: `git tag -a d4.3.0 -m "QGroundControl Daily Android Version Base"`. 3. Create an annotated tag on the newly created Stable branch named `vX.Y.0` with the correct major/minor version number. Example: `git tag -a v4.2.0 -m "QGroundControl v4.2.0"`. Pushing this tag to the repo will start a build. 4. Once the build completes verify the builds are pushed up to S3 correctly and sanity check that they at least boot correctly. Location on S3 will be `https://qgroundcontrol.s3.us-west-2.amazonaws.com/latest/...`. -5. Update the `https://qgroundcontrol.s3.us-west-2.amazonaws.com/builds/latest/QGC.version.txt` text file to the latest Stable version. This will notify uses there is a new Stable available the next time they launch QGC. +5. Update the `https://qgroundcontrol.s3.us-west-2.amazonaws.com/latest/QGC.version.txt` text file to the latest Stable version. This will notify users that there is a new Stable available the next time they launch QGC. +6. Note that the cached cloudfront downloads will take up to 24h to refresh. If they need to update earlier, the caches would need to be manually invalidated. ### Patch Version diff --git a/docs/zh/qgc-dev-guide/tools/index.md b/docs/zh/qgc-dev-guide/tools/index.md index 39455731ae0..1880d0e6611 100644 --- a/docs/zh/qgc-dev-guide/tools/index.md +++ b/docs/zh/qgc-dev-guide/tools/index.md @@ -10,7 +10,7 @@ and accessing the System Shell over MAVLink. 工具包括： -- 模拟链接（仅限每日构建） - 创建和停止多个模拟载具链接。 +- **[Mock Link](../tools/mock_link.md)** (Debug Builds only) - Creates and stops multiple simulated vehicle links. - **[Replay Flight Data](../../qgc-user-guide/fly_view/replay_flight_data.md)** - Replay a telemetry log (User Guide). - **[MAVLink Inspector](../../qgc-user-guide/analyze_view/mavlink_inspector.html)** - Display received MAVLink messages/values and plot trends. - **[MAVLink Console](../../qgc-user-guide/analyze_view/mavlink_console.html)** (PX4 Only) - Connect to the PX4 nsh shell and send commands. diff --git a/docs/zh/qgc-dev-guide/user_interface_design/controls.md b/docs/zh/qgc-dev-guide/user_interface_design/controls.md index 6ee5fc1b9f1..4112c206651 100644 --- a/docs/zh/qgc-dev-guide/user_interface_design/controls.md +++ b/docs/zh/qgc-dev-guide/user_interface_design/controls.md @@ -33,3 +33,4 @@ import QGroundControl.Controls 1.0 - QGCViewPanel - QGCView内部的主要视图内容。 - RoundButton - 一个圆形按钮控件，它使用图像作为其内部内容。 - SetupPage - 所有安装载具组件页面的基本控件。 提供标题，说明和组件页面内容区域。 Provides a title, description and component page contents area. +- SelectableControl - Allows users to select from a list of controls to display. Right-click on Desktop or Press and Hold on Mobile will show selection UI. Example usage: Allows user to select between multiple Instrument display variants. diff --git a/docs/zh/qgc-dev-guide/views/fly.md b/docs/zh/qgc-dev-guide/views/fly.md index 3eb89abca21..0856186aa6b 100644 --- a/docs/zh/qgc-dev-guide/views/fly.md +++ b/docs/zh/qgc-dev-guide/views/fly.md @@ -1,6 +1,6 @@ # 飞视图 -- 顶级QML代码在FlightDisplayView\.qml中 +- 顶级QML代码在FlightDisplayView.qml中 - QML代码与MissionController（C ++）通信以进行任务显示 - 仪器小部件与活动的Vehicle对象通信 - 两个主要的内部view是： diff --git a/docs/zh/qgc-dev-guide/views/setup.md b/docs/zh/qgc-dev-guide/views/setup.md index 80d6e1d22b7..c582048bccf 100644 --- a/docs/zh/qgc-dev-guide/views/setup.md +++ b/docs/zh/qgc-dev-guide/views/setup.md @@ -1,5 +1,5 @@ # 设置视图 -- 在SetupView\.qml中实现的顶级QML代码 +- 在SetupView.qml中实现的顶级QML代码 - 固定的按钮/页面集：摘要，固件 - 按钮/页面的剩余部分来自AutoPilot Plugin Vehicle Component列表 diff --git a/docs/zh/qgc-user-guide/custom_actions/custom_actions.md b/docs/zh/qgc-user-guide/custom_actions/custom_actions.md new file mode 100644 index 00000000000..82a56ac8f2c --- /dev/null +++ b/docs/zh/qgc-user-guide/custom_actions/custom_actions.md @@ -0,0 +1,44 @@ +# Custom Mavlink Action + +Both the Fly View and Joysticks support the ability execute arbitrary mavlink commands to the active vehicle. In the Fly View these will show up in the Toolstrip Action list. With Joysticks you can assign then to button presses. + +## Mavlink Actions File + +The actions available are defined in a JSON file. The format of that file is as follows: + +``` +{ + "version": 1, + "fileType": "MavlinkActions", + "actions": [ + { + "label": "First Mavlink Command", + "description": "This is the first command", + "mavCmd": 10, + "compId": 100, + "param1": 1, + "param2": 2, + ... + }, + { + "label": "Second Mavlink Command", + "description": "This is the second command", + "mavCmd": 20, + ... + } + ] +} +``` + +Fields: + +- actions (required) - An array of json objects, one for each command +- label (required) - The user visible short description for the command. This is used as the button text for the Fly View - Actions command list. For Joysticks, this is the command you select from the dropdown. For Joysticks, make sure your name doesn't conflict with the built in names. +- description (required) - This is a longer description of the command used in the Fly View - Action list. This is not used by joysticks. +- mavCmd (required) - The command id of the mavlink command you want to send. +- compId (options) - The component id for where you want to send the command to. If not specified `MAV_COMP_ID_AUTOPILOT1` is used. +- param1 thru param7 (optional) - The parameters for the command. Parameters which are not specified will default to 0.0 + +Mavlink action files should be located in the MavlinkActions directory of the QGC save location. For example on Linux that would be `~/Documents/QGroundControl/MavlinkActions` or `~/Documents/QGroundControl Daily/MavlinkActions`. The Fly View and Joysticks can each have there own custom actions file. + +When you start up QGC it will load these files if they exist and make the commands available for use. diff --git a/docs/zh/qgc-user-guide/fly_view/camera_tools.md b/docs/zh/qgc-user-guide/fly_view/camera_tools.md new file mode 100644 index 00000000000..a1cd5980e3c --- /dev/null +++ b/docs/zh/qgc-user-guide/fly_view/camera_tools.md @@ -0,0 +1,29 @@ +# Camera Tools + +The camera tools are used to capture still images and video, and to configure the camera. + +![Camera Panel](../../../assets/fly/camera_panel/camera_mavlink.png) + +The camera capture and configuration options depend on the connected camera. +The configuration options are selected using the panel gear icon. +The configuration for a simple autopilot-connected camera are shown below. + +![Camera Panel - minimal settings](../../../assets/fly/camera_panel/camera_settings_minimal.png) + +When connected to camera that supports the [MAVLink Camera Protocol](https://mavlink.io/en/services/camera.html) you can additionally configure and use other camera services that it makes available. +For example, if your camera supports video mode you will be able to switch between still image capture and video mode, and start/stop recording. + +![Camera Panel - MAVLink settings](../../../assets/fly/camera_panel/camera_settings_mavlink.png) + +::: info +Most of the settings that are displayed depend on the camera (they are defined in its [MAVLink Camera Definition File](https://mavlink.io/en/services/camera_def.html)). + +> A few common settings at the end are hard-coded: Photo Mode (Single/Time Lapse), Photo Interval (if Time Lapse), Reset Camera Defaults (sends a reset command to the camera), Format (storage) +> ::: + +### Video Stream {#video_instrument_page} + +The video page is used to enable/disable video streaming. +When enabled, you can start/stop the video stream, enable a grid overlay, change how the image fits the screen, and record the video locally with QGC. + +![Instrument Page - Video Stream](../../../assets/fly/instrument_page_video_stream.jpg) diff --git a/docs/zh/qgc-user-guide/fly_view/fly_tools.md b/docs/zh/qgc-user-guide/fly_view/fly_tools.md new file mode 100644 index 00000000000..dff94728e21 --- /dev/null +++ b/docs/zh/qgc-user-guide/fly_view/fly_tools.md @@ -0,0 +1,60 @@ +# Fly Tools + +## Pre Flight Checklist {#preflight_checklist} + +An automated preflight checklist can be used to run through standard checks that the vehicle is configured correctly and it is safe to fly. + +To view the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../settings_view/general.md) and selecting the **Use preflight checklist** checkbox. +The tool will then be added to the _Flight Tools_. +Press it to open the checklist: + +![Pre Flight Checklist](../../../assets/fly/pre_flight_checklist.jpg) + +Once you have performed each test, select it on the UI to mark it as complete. + +## Takeoff {#takeoff} + +:::tip +If you are starting a mission for a multicopter, _QGroundControl_ will automatically perform the takeoff step. +::: + +To takeoff (when landed): + +1. Press the **Takeoff** button in the _Fly Tools_ (this will toggle to a **Land** button after taking off). +2. Optionally set the takeoff altitude in the right-side vertical slider. + +- You can slide up/down to change the altitude +- You can also click on the specified altitude (10 ft in example) and then type in a specific altitude. + +1. Confirm takeoff using the slider. + +![takeoff](../../../assets/fly/takeoff.png) + +## Land {#land} + +You can land at the current position at any time while flying: + +1. Press the **Land** button in the _Fly Tools_ (this will toggle to a **Takeoff** button when landed). +2. Confirm landing using the slider. + +## RTL/Return + +Return to a "safe point" at any time while flying: + +1. Press the **RTL** button in the _Fly Tools_. +2. Confirm RTL using the slider. + +:::info +Vehicles commonly return to the "home" (takeoff) location and land. +This behaviour depends on the vehicle type and configuration. +For example, rally points or mission landings may be used as alternative return targets. +::: + +## Change Altitude {#change_altitude} + +You can change altitude while flying, except when in a mission: + +1. Press the **Actions** button on the _Fly Tools_ +2. Select the _Change Altitude_ button +3. Select the new altitude from the vertical slider +4. Confirm the action diff --git a/docs/zh/qgc-user-guide/fly_view/fly_view.md b/docs/zh/qgc-user-guide/fly_view/fly_view.md index eea8f9fcca4..f34c53a4e91 100644 --- a/docs/zh/qgc-user-guide/fly_view/fly_view.md +++ b/docs/zh/qgc-user-guide/fly_view/fly_view.md @@ -1,293 +1,46 @@ # 飞行视图 -飞行视图用于在飞行时对车辆进行指挥和监视。 +The Fly View is used to command and monitor the vehicle. -您可以使用它： - -- 自动运行[航前检查表](#preflight_checklist)。 -- Arm the vehicle (or check why it won't arm). -- 控制飞行任务：[启动](#start_mission), [继续](#continue_mission), [暂停](#pause), 和[恢复](#resume_mission)。 -- 引导飞行器执行[解锁](#arm)/[上锁](#disarm)/[急停](#emergency_stop)、[起飞](#takeoff)/[着陆](#land)、[改变高度](#change_altitude)、[去](#goto)或[环绕](#orbit)指定位置，以及[返航/RTL](#rtl)。 -- 在地图视图和视频视图之间切换(如果可用) -- Display video, mission, telemetry, and other information for the current vehicle, and also switch between connected vehicles. +## Overview ![Fly View](../../../assets/fly/fly_view_overview.jpg) -## 界面概述 - -以上屏幕截图显示了飞行视图的主要元素： - -- **地图：** 显示所有已连接飞行器的位置及当前飞行器的任务。 - - You can drag the map to move it around (the map automatically re-centres after a certain amount of time). +- **[Toolbar](fly_view_toolbar.md):** The toolbar is at the top of the screen. It provides controls to select views, show flight status and mode as well as the status of the main components of the vehicle. +- **[Vehicle Actions](fly_tools.md):** Allows you command the vehicle to take a specific action. +- **[Instrument Panel](instrument_panel.md):** A widget that displays vehicle telemetry. +- **[Attitude/Compass](hud.md):** A widget that provides virtual horizon and heading information. +- **[Camera Tools](camera_tools.md)**: A widget for switching between still and video modes, starting/stopping capture, and controlling camera settings. +- **[Video](video.md):** Display the video from the vehicle. Allows you to toggle between video or map as the main display. +- **Map:** Displays the positions of all connected vehicles and the mission for the current vehicle. + - You can drag the map to move it around (the map automatically re-centres on the vehicle after a certain amount of time). + - You can zoom the map in and out using the zoom buttons, mouse wheel, track pad or pinch on a tablet. - Once flying, you can click on the map to set a [Go to](#goto) or [Orbit at](#orbit) location. -- **Fly Toolbar:** Key status information for sensors (GPS, battery, RC control), and vehicle state (Flight mode, Armed/Disarmed status). - - Select the sensor indicators to view more detail. - - Press the _Flight mode_ text (e.g. "Hold") to select a new mode. - Not every mode may be available. - - The text next to the **Q** icon indicates the flight readiness using text: "Not Ready", "Ready to Fly", "Flying", and status using colour: "green" (all good!), amber (a warning), red (serious problem). - Select the text when the background is amber or red to find out the cause of any preflight issues (QGC 4.2.0 and later). - You can also select the text to reach a button to arm/disarm/emergency-stop the vehicle. -- **Fly tools:** You can use these to: - - Toggle between takeoff/land. - - Pause/restart the current operation (e.g. landing, or the mission). - - Safety return (also known as RTL or Return). - - The _Action_ button offers other appropriate options for the current state (these overlay the _Confirmation Slider_). - Actions include changing the altitude or continuing a mission. - - Enable the [preflight checklist](#preflight_checklist) (tool option disabled by default). -- **[Instrument Panel](#instrument_panel):** A multi-page widget that displays vehicle information including: telemetry, camera, video, system health, and vibration. -- **Attitude/Compass**: A widget that provides virtual horizon and heading information. -- **Camera Tools**: A widget for switching between still and video modes, starting/stopping capture, and controlling camera settings. -- **[Video/Switcher](#video_switcher):** Toggle between video or map in a window. - - Press the element to switch _Video_ and _Map_ to foreground. - - _QGroundControl_ supports RTP and RTSP video streaming over your vehicles UDP connection. - It also supports directly connected UVC devices. - QGC video support is further discussed in the [Video README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md). - - A [Telemetry Overlay](../fly_view/video_overlay.md) is automatically generated as a subtitle file -- **Confirmation Slider:** Context sensitive slider to confirm requested actions. - Slide to start operation. Press **X** to cancel. - -There are a number of other elements that are not displayed by default/are only displayed in certain conditions. -For example, the multi-vehicle selector is only displayed if you have multiple vehicles, and the preflight checklist tool button is only displayed if the appropriate setting is enabled. - -## Instrument Panel {#instrument_panel} - -The instrument panel is a multi-page widget that displays information about the current vehicle, including: telemetry, camera, video, system health, and vibration information. - -![Instrument Page - for values/telemetry](../../../assets/fly/instrument_page_values.jpg) - -The values page shows telemetry information; by default the altitude (relative to the home location) and the ground speed. - -You can configure what information is display by pressing the small gear icon on the top left of the panel. -This toggles the position of the panel between bottom centre and right-centre. - -![Instrument Panel - hover for move/edit tools](../../../assets/fly/instrument_panel/instrument_panel_tools_move_edit.png) - -You configure what information is display by selecting the edit/pencil icon. -The grid will then display "+" and "-" icons that you can use to add or remove rows and columns (and the pencil icon is replaced by a "lock" icon that you can use to save the settings). - -![Instrument Page - Vibration Clip](../../../assets/fly/instrument_page_vibration.jpg) - -Select a value to launch its "Value Display" editor. -This allows you to change the icon, text, size, units and so on of the current telemetry value. - -Press the _Armed/Disarmed_ text to toggle the armed state. - -The selection list on the top left is used to change the source of the telemetry. -By default this is the vehicle, but you can use the selector to choose a particular sensor type. - -![Instrument Page - Vehicle Health Good](../../../assets/fly/instrument_page_health_good.jpg) ![Instrument Page - Vehicle Health Bad](../../../assets/fly/instrument_page_health_bad.jpg) - -The selection list on the top right is used to select a particular telemetry value for the vehicle or sensor. - -![Instrument Page - values settings](../../../assets/fly/instrument_page_values_settings.jpg) - -### Camera {#camera_instrument_page} - -The camera page is used to configure and control the camera. - -![Instrument Page - for Camera](../../../assets/fly/instrument_page_camera.jpg) - -The camera capture and configuration options depend on the connected camera. -The configuration options are selected using the panel gear icon. -The configuration for a simple autopilot-connected camera are shown below. - -Most of the settings that are displayed depend on the camera (they are defined in its [MAVLink Camera Definition File](https://mavlink.io/en/services/camera_def.html)). - -When connected to camera that supports the [MAVLink Camera Protocol](https://mavlink.io/en/services/camera.html) you can additionally configure and use other camera services that it makes available. -For example, if your camera supports video mode you will be able to switch between still image capture and video mode, and start/stop recording. - -![Instrument Page - Camera MAVLink Settings](../../../assets/fly/instrument_page_camera_mavlink_settings.jpg) - -::: info -Most of the settings that are displayed depend on the camera (they are defined in its [MAVLink Camera Definition File](https://mavlink.io/en/services/camera_def.html)). - -> A few common settings at the end are hard-coded: Photo Mode (Single/Time Lapse), Photo Interval (if Time Lapse), Reset Camera Defaults (sends a reset command to the camera), Format (storage) -### Video Stream {#video_instrument_page} - -The video page is used to enable/disable video streaming. -When enabled, you can start/stop the video stream, enable a grid overlay, change how the image fits the screen, and record the video locally with QGC. - -![Instrument Page - Video Stream](../../../assets/fly/instrument_page_video_stream.jpg) +There are a number of other elements that are not displayed by default and are only displayed in certain conditions or for certain vehicle types. ## Actions/Tasks The following sections describe how to perform common operations/tasks in the Fly View. -Many of the available options depend on both the vehicle type and its current state. -::: - -### Pre Flight Checklist {#preflight_checklist} - -An automated preflight checklist can be used to run through standard checks that the vehicle is configured correctly and it is safe to fly. - -To view the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../settings_view/general.md) and selecting the **Use preflight checklist** checkbox. -The tool will then be added to the _Flight Tools_. -Press it to open the checklist: - -![Pre Flight Checklist](../../../assets/fly/pre_flight_checklist.jpg) - -Once you have performed each test, select it on the UI to mark it as complete. - -### Arming and Preflight Checks {#arm} - -Arming a vehicle starts the motors in preparation for takeoff. -You will only be able to arm the vehicle if it is safe and ready to fly. - -:::tip -Generally _QGroundControl_ does not require you to arm the vehicle explicitly; this is done for you if you start a mission or takeoff. -::: - -The vehicle is ready to fly in all modes if the status text says "Ready to Fly" and the background is green. - -![Vehicle state - ready to fly green/ready background](../../../assets/fly/vehicle_states/ready_to_fly_ok.png) - -If the background is amber then it is ready to take off in the current mode, but may not be able to switch to other modes. -If the background is red and the text is "Not Ready" then you will not be able to arm in the current mode. - -![Vehicle state - ready to fly amber/warning background](../../../assets/fly/vehicle_states/ready_to_fly_warning.png) -![Vehicle state - not ready](../../../assets/fly/vehicle_states/not_ready.png) - -From QGC 4.2.0 (at time of writing, a daily build) you can find out the exact cause of the warning or error, and possible solutions, by pushing the status text. - -This launches the preflight arming checks popup with a list of all preflight warnings. -The toggle on the right expands each error with additional information and possible solutions. - -![UI To check arming warnings](../../../assets/fly/vehicle_states/arming_preflight_check_ui.png) - -Once each issue is resolved it will disappear from the UI. -When all issues blocking arming have been removed you can use the arm button to display the arming confirmation slider, and arm the vehicle (or you can just take off - note that the vehicles will (by default) disarm automatically if you do not take off after a few seconds. - -To arm the vehicle, select **Disarmed** in the _Fly Toolbar_ and then use the confirmation sider. - -::: info -The status text also displays when flying. - -> To disarm the vehicle select **Armed** in the _Fly Toolbar_ when the vehicle is **landed**. -> -> The arming checks UI will open even when flying, allowing you to emergency disarm. -> ::: - -### Disarm {#disarm} - -Disarming the vehicle stops the motors (making the vehicle safe). - -Vehicles usually disarm automatically if you do not take off after a few seconds. - -If needed, you can do so from the Arming Preflight Checks UI. - -![Arm](../../../assets/fly/arm.jpg) - -You will then need to use the disarming slider. - -![Disarm](../../../assets/fly/disarm.jpg) - -Disarming the vehicle while it is flying is called an [Emergency Stop](#emergency_stop) - -### Emergency Stop {#emergency_stop} - -Emergency stop is effectively the same as disarming the vehicle while it is flying. -Your vehicle will crash! - -If needed, you can do so from the Arming Preflight Checks UI. - -To disarm the vehicle select **Armed** in the _Fly Toolbar_ when the vehicle is flying. - -You will then need to use the emergency disarming slider. - -![Emergency Stop](../../../assets/fly/emergency_stop.jpg) - -### Takeoff {#takeoff} - -:::tip -If you are starting a mission for a multicopter, _QGroundControl_ will automatically perform the takeoff step. -::: - -To takeoff (when landed): - -1. Press the **Takeoff** button in the _Fly Tools_ (this will toggle to a **Land** button after taking off). -2. Optionally set the takeoff altitude in the right-side vertical slider. -3. Confirm takeoff using the slider. - -![takeoff](../../../assets/fly/takeoff.png) - -### Land {#land} - -You can land at the current position at any time while flying: - -1. Press the **Land** button in the _Fly Tools_ (this will toggle to a **Takeoff** button when landed). -2. Confirm landing using the slider. - -![land](../../../assets/fly/land.jpg) - -### RTL/Return - -Return to a "safe point" at any time while flying: - -1. Press the **RTL** button in the _Fly Tools_. -2. Confirm RTL using the slider. - -![rtl](../../../assets/fly/rtl.jpg) - -:::info -Vehicles commonly return to the "home" (takeoff) location and land. -This behaviour depends on the vehicle type and configuration. -For example, rally points or mission landings may be used as alternative return targets. -::: - -### Change Altitude {#change_altitude} - -You can change altitude while flying, except when in a mission: - -1. Press the **Action** button on the _Fly Tools_ - -2. Select the _Change Altitude_ action from the dialog. - - ![Continue Mission/Change Altitude action](../../../assets/fly/continue_mission_change_altitude_action.jpg) - -3. Move the vertical slider to the desired altitude, then drag the confirmation slider to start the action. - - ![Change altitude](../../../assets/fly/change_altitude.jpg) - -### Goto Location {#goto} - -After taking off you can specify that you want to fly to a particular location. - -1. Left click/Press on the map where you want the vehicle to move and select **Go to location** on the popup. - -![Goto or orbit](../../../assets/fly/goto_or_orbit.jpg) - -1. The location will be displayed on the map, along with a confirmation slider. - - ![Goto confirmation](../../../assets/fly/goto.jpg) - -2. When you're ready, drag the slider to start the operation (or press the **X** icon to cancel it). - :::info -Goto points must be set within 1 km of the vehicle (hard-coded in QGC). +Many of the available options depend on both the vehicle type and its current state. ::: -### Orbit Location {#orbit} - -After taking off you can specify that you want to orbit a particular location. - -1. Left click/Press on the map (near the centre of your desired orbit) and select **Orbit at location** on the popup. +### Actions associated with a map position (#map_actions) -![Goto or orbit](../../../assets/fly/goto_or_orbit.jpg) +There are a number of actions which can be taken which are associated with a specific position on the map. To use these actions: -1. The proposed orbit will be displayed on the map, along with a confirmation sider. +1. Click on the map at a specific position +2. A popup will display showing you the list of available actions +3. Select the action you want +4. Confirm the action - ![Orbit confirmation](../../../assets/fly/orbit.jpg) - - - Select and drag the central marker to move the orbit location. - - Select and drag the dot on the outer circle to change the orbit radius - -2. When you're ready, drag the slider to start the operation (or press the **X** icon to cancel it). +Examples of map position actions are Go To Location, Orbit and so forth. ### Pause -You can pause most operations, including taking off, landing, RTL, mission execution, orbit at location. -The vehicle behaviour when paused depends on the vehicle type; typically a multicopter will hover, and a fixed wing vehicle will circle. +You can pause most operations, including taking off, landing, RTL, mission execution, orbit at location. The vehicle behaviour when paused depends on the vehicle type; typically a multicopter will hover, and a fixed wing vehicle will circle. :::info You cannot pause a _Goto location_ operation. @@ -299,8 +52,6 @@ To pause: 2. Optionally set a new altitude using the right-side vertical slider. 3. Confirm the pause using the slider. -![pause](../../../assets/fly/pause.jpg) - ### Missions #### Start Mission {#start_mission} diff --git a/docs/zh/qgc-user-guide/fly_view/fly_view_toolbar.md b/docs/zh/qgc-user-guide/fly_view/fly_view_toolbar.md new file mode 100644 index 00000000000..1895c883cfd --- /dev/null +++ b/docs/zh/qgc-user-guide/fly_view/fly_view_toolbar.md @@ -0,0 +1,78 @@ +# Fly View Toolbar + +![Fly View](../../../assets/fly/toolbar/fly_view_toolbar.jpg) + +## Views + +The "Q" icon on the left of the toolbar allows you to select between additional top level views: + +- **[Plan Flight](../plan_view/plan_view.md):** Used to create missions, geo-fences and rally points +- **Analyze Tools:** A set of tools for things like log download, geo-tagging images, or viewing telemetry. +- **Vehicle Configuration:** The various options for the initial configuration of a new vehicle. +- **Application Settings:** Settings for the QGroundControl application itself. + +## Toolbar Indicators + +Next are a multiple toolbar indicators for vehicle status. The dropdowns for each toolbar indicator provide additional detail on status. You can also expand the indicators to show additional application and vehicle settings associated with the indicator. Press the ">" button to expand. + +![Toolbar Indicator - expand button](../../../assets/fly/toolbar_indicator_expand.png) + +### Flight Status + +The Flight Status indicator shows you whether the vehicle is ready to fly or not. It can be in one of the following states: + +- **Ready To Fly** (_green background_) - Vehicle is ready to fly +- **Ready To Fly** (_yellow background_) - Vehicle is ready to fly in the current flight mode. But there are warnings which may cause problems. +- **Not Ready** - Vehicle is not ready to fly and will not takeoff. +- **Armed** - Vehicle is armed and ready to Takeoff. +- **Flying** - Vehicle is in the air and flying. +- **Landing** - Vehicle is in the process of landing. +- **Communication Lost** - QGroundControl has lost communication with the vehicle. + +The Flight Status Indicator dropdown also gives you acess to: + +- **Arm** - Arming a vehicle starts the motors in preparation for takeoff. You will only be able to arm the vehicle if it is safe and ready to fly. Generally you do not need to manually arm the vehicle. You can simply takeoff or start a mission and the vehicle will arm itself. +- **Disarm** - Disarming a vehicle is only availble when the vehicle is on the ground. It will stop the motors. Generally you do not need to explicitly disarm as vehicles will disarm automatically after landing, or shortly after arming if you do not take off. +- **Emergency Stop** - Emergency stop is used to disarm the vehicle while it is flying. For emergency use only, your vehicle will crash! + +In the cases of warnings or not ready state you can click the indicator to display the dropdown which will show the reason(s) why. The toggle on the right expands each error with additional information and possible solutions. + +![UI To check arming warnings](../../../assets/fly/vehicle_states/arming_preflight_check_ui.png) + +Once each issue is resolved it will disappear from the UI. When all issues blocking arming have been removed you should now be ready to fly. + +## Flight Mode + +The Flight Mode indicator shows you the current flight mode. The dropdown allows you to switch between flight modes. The expanded page allows you to: + +- Configure vehicle land settings +- Set global geo-fence settings +- Add/Remove flight modes from the displayed list + +## Vehicle Messages + +The Vehicle Messages indicator dropdown shows you messages which come from the vehicle. The indicator will turn red if there are important messages available. + +## GPS + +The GPS indicator shows you the satellite count and the HDOP in the toolbar icon. The dropdown shows you additional GPS status. The expanded page give you access to RTK settings. + +## Battery + +The Battery indicator shows you a configurable colored battery icon for remaining charge. It can also be configured to show percent remaining, voltage or both. The expanded page allows you to: + +- Set what value(s) you want displayed in the battery icon +- Configure the icon coloring +- Set up the low battery failsafe + +## Remote ID + +## Other Indicators + +There are other indicators which only show in certain situations: + +- Telemetry RSSI +- RC RSSI +- Gimbal +- VTOL transitions +- Select from multiple connected vehicles diff --git a/docs/zh/qgc-user-guide/fly_view/hud.md b/docs/zh/qgc-user-guide/fly_view/hud.md new file mode 100644 index 00000000000..6ec8c28be74 --- /dev/null +++ b/docs/zh/qgc-user-guide/fly_view/hud.md @@ -0,0 +1,429 @@ +# Fly View + +The Fly View is used to command and monitor the vehicle when flying. + +You can use it to: + +- Run an automated [pre-flight checklist](#preflight_checklist). +- Arm the vehicle (or check why it won't arm). +- Control missions: [start](#start_mission), [continue](#continue_mission), [pause](#pause), and [resume](#resume_mission). +- Guide the vehicle to [arm](#arm)/[disarm](#disarm)/[emergency stop](#emergency_stop), [takeoff](#takeoff)/[land](#land), [change altitude](#change_altitude), [go to](#map_actions) or [orbit](#map_actions) a particular location, and [return/RTL](#rtl). +- Switch between a map view and a video view (if available) +- Display video, mission, telemetry, and other information for the current vehicle, and also switch between connected vehicles. + +![Fly View](../../../assets/fly/fly_view_overview.jpg) + +## UI Overview + +The screenshot above shows the main elements of the fly view: + +- **[Fly Toolbar](fly_view_toolbar.md):** Key status information for vehicle components (GPS, battery, RC control), and vehicle state (Flight mode, Armed/Disarmed status). + - Select the [toolbar indicator](#toolbar_indicator) to view more detail. + - Press the _Flight mode_ text (e.g. "Hold") to select a new mode. + Not every mode may be available. + - The text next to the **Q** icon indicates the flight readiness using text: "Not Ready", "Ready to Fly", "Flying", and status using colour: "green" (all good!), amber (a warning), red (serious problem). You can also select the text to reach a button to arm/disarm/emergency-stop the vehicle. +- **[Fly tools](fly_tools.md):** You can use these to: + - Select the [preflight checklist](#preflight_checklist) (tool option disabled by default). + - Toggle between takeoff/land. + - Pause/restart the current operation (e.g. landing, or the mission). + - Safety return (also known as RTL or Return). + - The _Actions_ button offers other appropriate options for the current state. Actions include changing the altitude or continuing a mission. +- **Map:** Displays the positions of all connected vehicles and the mission for the current vehicle. + - You can drag the map to move it around (the map automatically re-centres on the vehicle after a certain amount of time). + - You can zoom the map in and out using the zoom buttons, mouse wheel, track pad or pinch on a tablet. + - Once flying, you can click on the map to set a [Go to](#goto) or [Orbit at](#orbit) location. +- **[Instrument Panel](instrument_panel.md):** A widget that displays vehicle telemetry. +- **[Attitude/Compass](hud.md):** A widget that provides virtual horizon and heading information. +- **Camera Tools**: A widget for switching between still and video modes, starting/stopping capture, and controlling camera settings. +- **[Video/Switcher](#video_switcher):** Toggle between video or map in a window. + - Press the element to switch _Video_ and _Map_ to foreground. + - _QGroundControl_ supports RTP and RTSP video streaming over your vehicles UDP connection. + It also supports directly connected UVC devices. + QGC video support is further discussed in the [Video README](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoStreaming/README.md). + - A [Telemetry Overlay](../fly_view/video_overlay.md) is automatically generated as a subtitle file +- **Confirmation Slider:** Context sensitive slider to confirm requested actions. Slide to confirm operation. You can also hold the spacebar to confirm. Press **X** to cancel. + +There are a number of other elements that are not displayed by default/are only displayed in certain conditions. +For example, the multi-vehicle selector is only displayed if you have multiple vehicles, and the preflight checklist tool button is only displayed if the appropriate setting is enabled. + +## Fly Toolbar {#toolbar} + +### View Selector + +The "Q" icon on the left of the toolbar allows you to select between additional top level views: + +- **[Plan Flight](../plan_view/plan_view.md):** Used to create missions, geo-fences and rally points +- **Analyze Tools:** A set of tools for things like log download, geo-tagging images, or viewing telemetry. +- **Vehicle Configuration:** The various options for the initial configuration of a new vehicle. +- **Application Settings:** Settings for the QGroundControl application itself. + +### Toolbar Indicators {#toolbar_indicators} + +Next are a toolbar indicators for vehicle status. The dropdowns for each toolbar indicator provide additional detail on status. You can also expand the indicators to show additional application and vehicle settings associated with the indicator. Press the ">" button to expand. + +![Toolbar Indicator - expand button](../../../assets/fly/toolbar_indicator_expand.png) + +Here is an example expanded toolbar indicator for flight modes on a vehicle running PX4 firmware. The settings in this indicator provide access to things which may be relevant to change from flight to flight. + +![Toolbar Indicator - expanded](../../../assets/fly/toolbar_indicator_expanded.png) + +They also provide access to the Vehicle Configuration associated with the indicator. In this example: _Flight Modes_ - _Configure_. + +### Ready/Not Ready Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/vehicle_states/ready_to_fly_ok.png) + +Next in the toolbar is the indicator which shows you whether the vehicle is ready to fly or not. + +It can be in one of the following states: + +- **Ready To Fly** (_green background_) - Vehicle is ready to fly +- **Ready To Fly** (_yellow background_) - Vehicle is ready to fly in the current flight mode. But there are warnings which may cause problems. +- **Not Ready** - Vehicle is not ready to fly and will not takeoff. +- **Armed** - Vehicle is armed and ready to Takeoff. +- **Flying** - Vehicle is in the air and flying. +- **Landing** - Vehicle is in the process of landing. +- **Communication Lost** - QGroundControl has lost communication with the vehicle. + +The Ready Indicator dropdown also gives you acess to: + +- **Arming** - Arming a vehicle starts the motors in preparation for takeoff. You will only be able to arm the vehicle if it is safe and ready to fly. Generally you do not need to manually arm the vehicle. You can simply takeoff or start a mission and the vehicle will arm itself. +- **Disarm** - Disarming a vehicle is only availble when the vehicle is on the ground. It will stop the motors. Generally you do not need to explicitly disarm as vehicles will disarm automatically after landing, or shortly after arming if you do not take off. +- **Emergency Stop** - Emergency stop is effectively the same as disarming the vehicle while it is flying. For emergency use only, your vehicle will crash! + +In the cases of warnings or not ready state you can click the indicator to display the dropdown which will show the reason(s) why. The toggle on the right expands each error with additional information and possible solutions. + +![UI To check arming warnings](../../../assets/fly/vehicle_states/arming_preflight_check_ui.png) + +Once each issue is resolved it will disappear from the UI. +When all issues blocking arming have been removed you should now be ready to fly. + +### Flight Mode Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/toolbar/flight_modes_indicator.png) + +The Flight Mode Indicator dropdown allows you to switch between flight modes. The expanded page allows you to: + +- Configure vehicle land settings +- Set global geo-fence settings +- Add/Remove flight modes from the displayed list + +### Vehicle Messages Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/toolbar/messages_indicator.png) + +The Vehicle Messages Indicator dropdown shows you messages which come from the vehicle. The indicator will turn red if there are important messages available. + +### GPS Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/toolbar/gps_indicator.png) + +The GPS Indicator shows you the satellite count and the HDOP in the toolbar icon. The dropdown shows you additional GPS status. The expanded page give you access to RTK settings. + +### Battery Indicator + +![Vehicle state - ready to fly green/ready background](../../../assets/fly/toolbar/battery_indicator.png) + +The Battery Indicator shows you a configurable colored battery icon for remaining charge. It can also be configured to show percent remaining, voltage or both. The expanded page allows you to: + +- Set what value(s) you want displayed in the battery icon +- Configure the icon coloring +- Set up the low battery failsafe + +## Fly Tools {#fly_tools} + +### Pre Flight Checklist {#preflight_checklist} + +An automated preflight checklist can be used to run through standard checks that the vehicle is configured correctly and it is safe to fly. + +To view the checklist, first enable the tool by navigating to [Application Settings > General > Fly View](../settings_view/general.md) and selecting the **Use preflight checklist** checkbox. +The tool will then be added to the _Flight Tools_. +Press it to open the checklist: + +![Pre Flight Checklist](../../../assets/fly/pre_flight_checklist.jpg) + +Once you have performed each test, select it on the UI to mark it as complete. + +### Takeoff {#takeoff} + +:::tip +If you are starting a mission for a multicopter, _QGroundControl_ will automatically perform the takeoff step. +::: + +To takeoff (when landed): + +1. Press the **Takeoff** button in the _Fly Tools_ (this will toggle to a **Land** button after taking off). +2. Optionally set the takeoff altitude in the right-side vertical slider. + +- You can slide up/down to change the altitude +- You can also click on the specified altitude (10 ft in example) and then type in a specific altitude. + +1. Confirm takeoff using the slider. + +![takeoff](../../../assets/fly/takeoff.png) + +### Land {#land} + +You can land at the current position at any time while flying: + +1. Press the **Land** button in the _Fly Tools_ (this will toggle to a **Takeoff** button when landed). +2. Confirm landing using the slider. + +### RTL/Return + +Return to a "safe point" at any time while flying: + +1. Press the **RTL** button in the _Fly Tools_. +2. Confirm RTL using the slider. + +:::info +Vehicles commonly return to the "home" (takeoff) location and land. +This behaviour depends on the vehicle type and configuration. +For example, rally points or mission landings may be used as alternative return targets. +::: + +### Change Altitude {#change_altitude} + +You can change altitude while flying, except when in a mission: + +1. Press the **Actions** button on the _Fly Tools_ +2. Select the _Change Altitude_ button +3. Select the new altitude from the vertical slider +4. Confirm the action + +## Instrument Panel (Telemetry) {#instrument_panel} + +The instrument panel displays telemetry information about the current vehicle. + +![Instrument Panel - for values/telemetry](../../../assets/fly/instrument_panel/instrument_panel_default_values.png) + +The default values include altitude (relative to the home location), horizontal and vertical speed, total flight time, and distance between vehicle and ground station. + +You can configure where the information is displayed by: + +- Tablets: Press and hold over control +- Desktop: Right click control +- Click to Lock icon to close and save changes + +![Instrument Panel - edit tools](../../../assets/fly/instrument_panel/instrument_panel_tools_edit.png) + +You configure what information is display by selecting the edit/pencil icon. +The grid will then display "+" and "-" icons that you can use to add or remove rows and columns (and the pencil icon is replaced by a "lock" icon that you can use to save the settings). + +Select a value to launch its "Value Display" editor. +This allows you to change the icon, text, size, units and so on of the current telemetry value. + +![Instrument Panel - edit a value](../../../assets/fly/instrument_panel/instrument_panel_tools_edit_value.png) + +The selection list on the top left is used to change the source of the telemetry. +By default this is the vehicle, but you can use the selector to choose a particular sensor type. + +![Instrument Panel - value type](../../../assets/fly/instrument_panel/instrument_panel_edit_value_type.png) + +The selection list on the top right is used to select a particular telemetry value for the vehicle or sensor. + +![Instrument Panel - value options](../../../assets/fly/instrument_panel/instrument_panel_edit_value_options.png) + +## Attitude /Compass {#hud} + +You can select from multiple types of instruments by: + +- Tablets: Press and hold over control +- Desktop: Right click over control +- Click the Lock icon to close and save changes + +![Instrument Panel - hover for move/edit tools](../../../assets/fly/hud_select_variant.png) + +### Camera {#camera_instrument_page} + +The camera panel is used to capture still images and video, and to configure the camera. + +![Camera Panel](../../../assets/fly/camera_panel/camera_mavlink.png) + +The camera capture and configuration options depend on the connected camera. +The configuration options are selected using the panel gear icon. +The configuration for a simple autopilot-connected camera are shown below. + +![Camera Panel - minimal settings](../../../assets/fly/camera_panel/camera_settings_minimal.png) + +When connected to camera that supports the [MAVLink Camera Protocol](https://mavlink.io/en/services/camera.html) you can additionally configure and use other camera services that it makes available. +For example, if your camera supports video mode you will be able to switch between still image capture and video mode, and start/stop recording. + +![Camera Panel - MAVLink settings](../../../assets/fly/camera_panel/camera_settings_mavlink.png) + +:::info +Most of the settings that are displayed depend on the camera (they are defined in its [MAVLink Camera Definition File](https://mavlink.io/en/services/camera_def.html)). + +> A few common settings at the end are hard-coded: Photo Mode (Single/Time Lapse), Photo Interval (if Time Lapse), Reset Camera Defaults (sends a reset command to the camera), Format (storage) +> ::: + +### Video Stream {#video_instrument_page} + +The video page is used to enable/disable video streaming. +When enabled, you can start/stop the video stream, enable a grid overlay, change how the image fits the screen, and record the video locally with QGC. + +![Instrument Page - Video Stream](../../../assets/fly/instrument_page_video_stream.jpg) + +## Actions/Tasks + +The following sections describe how to perform common operations/tasks in the Fly View. + +::: info +Many of the available options depend on both the vehicle type and its current state. +::: + +### Actions associated with a map position (#map_actions) + +There are a number of actions which can be taken which are associated with a specific position on the map. To use these actions: + +1. Click on the map at a specific position +2. A popup will display showing you the list of available actions +3. Select the action you want +4. Confirm the action + +Examples of map position actions are Go To Location, Orbit and so forth. + +### Pause + +You can pause most operations, including taking off, landing, RTL, mission execution, orbit at location. The vehicle behaviour when paused depends on the vehicle type; typically a multicopter will hover, and a fixed wing vehicle will circle. + +:::info +You cannot pause a _Goto location_ operation. +::: + +To pause: + +1. Press the **Pause** button in the _Fly Tools_. +2. Optionally set a new altitude using the right-side vertical slider. +3. Confirm the pause using the slider. + +### Missions + +#### Start Mission {#start_mission} + +You can start a mission when the vehicle is landed (the start mission confirmation slider is often displayed by default). + +To start a mission from landed: + +1. Press the **Action** button on the _Fly Tools_ + +2. Select the _Start Mission_ action from the dialog. + + ![Start mission action](../../../assets/fly/start_mission_action.jpg) + + (to display the confirmation slider) + +3. When the confirmation slider appears, drag it to start the mission. + + ![Start mission](../../../assets/fly/start_mission.jpg) + +#### Continue Mission {#continue_mission} + +You can _continue_ mission from the _next_ waypoint when you're flying (the _Continue Mission_ confirmation slider is often displayed by default after you takeoff). + +:::info +Continue and [Resume mission](#resume_mission) are different! +Continue is used to restart a mission that has been paused, or where you have taken off, so you've already missed a takeoff mission command. +Resume mission is used when you've used a RTL or landed midway through a mission (e.g. for a battery change) and then wish to continue the next mission item (i.e. it takes you to where you were up to in the mission, rather than continuing from your place in the mission). +::: + +You can continue the current mission while (unless already in a mission!): + +1. Press the **Action** button on the _Fly Tools_ + +2. Select the _Continue Mission_ action from the dialog. + + ![Continue Mission/Change Altitude action](../../../assets/fly/continue_mission_change_altitude_action.jpg) + +3. Drag the confirmation slider to continue the mission. + + ![Continue Mission](../../../assets/fly/continue_mission.jpg) + +#### Resume Mission {#resume_mission} + +_Resume Mission_ is used to resume a mission after performing an [RTL/Return](#rtl) or [Land](#land) from within a mission (in order, for example, to perform a battery change). + +:::info +If you are performing a battery change, **do not** disconnect QGC from the vehicle after disconnecting the battery. +After you insert the new battery _QGroundControl_ will detect the vehicle again and automatically restore the connection. +::: + +After landing you will be prompted with a _Flight Plan complete_ dialog, which gives you the option to remove the plan from the vehicle, leave it on the vehicle, or to resume the mission from the last waypoint that was traveled through. + +![Resume Mission](../../../assets/fly/resume_mission.jpg) + +If you select to resume the mission, then _QGroundControl_ will rebuild the mission and upload it to the vehicle. +Then use the _Start Mission_ slider to continue the mission. + +The image below shows the mission that was rebuilt after the Return shown above. + +![Resume Rebuilt Mission](../../../assets/fly/resume_mission_rebuilt.jpg) + +:::info +A mission cannot simply resume from the last mission item that the vehicle executed, because there may be multiple items at the last waypoint that affect the next stage of the mission (e.g. speed commands or camera control commands). +Instead _QGroundControl_ rebuilds the mission, starting from the last mission item flown, and automatically prepending any relevant commands to the front of the mission. +::: + +#### Remove Mission Prompt After Landing {#resume_mission_prompt} + +You will be prompted to remove the mission from the vehicle after the mission completes and the vehicle lands and disarms. +This is meant to prevent issues where stale missions are unknowingly left on a vehicle, potentially resulting in unexpected behavior. + +### Display Video {#video_switcher} + +When video streaming is enabled, _QGroundControl_ will display the video stream for the currently selected vehicle in the "video switcher window" at the bottom left of the map. +You can press the switcher anywhere to toggle _Video_ and _Map_ to foreground (in the image below, the video is shown in the foreground). + +![Video Stream Record](../../../assets/fly/video_record.jpg) + +:::info +Video streaming is configured/enabled in [Application Settings > General tab > Video](../settings_view/general.md#video). +::: + +You can further configure video display using controls on the switcher: + +![Video Pop](../../../assets/fly/video_pop.jpg) + +- Resize the switcher by dragging the icon in the top right corner. +- Hide the switcher by pressing the toggle icon in the lower left. +- Detach the video switcher window by pressing on the icon in its top left corner + (once detached, you can move and resize the window just like any other in your OS). + If you close the detached window the switcher will re-lock to the QGC Fly view. + +### Record Video + +If supported by the camera and vehicle, _QGroundControl_ can start and stop video recording on the camera itself. _QGroundControl_ can also record the video stream and save it locally. + +:::tip +Video stored on the camera may be of much higher quality, but it is likely that your ground station will have a much larger recording capacity. +::: + +#### Record Video Stream (on GCS) + +Video stream recording is controlled on the [video stream instrument page](#video_instrument_page). +Press the red circle to start recording a new video (a new video file is created each time the circle is pressed); the circle will change into a red square while recording is in progress. + +![Video Stream Record](../../../assets/fly/video_record.jpg) + +Video stream recording is configured in the [Application Settings > General tab](../settings_view/general.md): + +- [Video Recording](../settings_view/general.md#video-recording) - specifies the recording file format and storage limits. + + ::: info + Videos are saved in Matroska format (.mkv) by default. + This format is relatively robust against corruption in case of errors. + ::: + +- [Miscellaneous](../settings_view/general.md#miscellaneous) - Streamed video is saved under the **Application Load/Save Path**. + +:::tip +The stored video includes just the video stream itself. +To record video with QGroundControl application elements displayed, you should use separate screen recording software. +::: + +#### Record Video on Camera + +Start/stop video recording _on the camera itself_ using the [camera instrument page](#camera_instrument_page). +First toggle to video mode, then select the red button to start recording. + +![Instrument Page - Camera MAVLink Settings](../../../assets/fly/instrument_page_camera_mavlink.jpg) diff --git a/docs/zh/qgc-user-guide/fly_view/instrument_panel.md b/docs/zh/qgc-user-guide/fly_view/instrument_panel.md new file mode 100644 index 00000000000..5f4deed8d8c --- /dev/null +++ b/docs/zh/qgc-user-guide/fly_view/instrument_panel.md @@ -0,0 +1,32 @@ +# Instrument Panel + +The instrument panel displays telemetry information about the current vehicle. + +![Instrument Panel - for values/telemetry](../../../assets/fly/instrument_panel/instrument_panel_default_values.png) + +The default values include altitude (relative to the home location), horizontal and vertical speed, total flight time, and distance between vehicle and ground station. + +You can configure where the information is displayed by: + +- Tablets: Press and hold over control +- Desktop: Right click control +- Click to Lock icon to close and save changes + +![Instrument Panel - edit tools](../../../assets/fly/instrument_panel/instrument_panel_tools_edit.png) + +You configure what information is display by selecting the edit/pencil icon. +The grid will then display "+" and "-" icons that you can use to add or remove rows and columns (and the pencil icon is replaced by a "lock" icon that you can use to save the settings). + +Select a value to launch its "Value Display" editor. +This allows you to change the icon, text, size, units and so on of the current telemetry value. + +![Instrument Panel - edit a value](../../../assets/fly/instrument_panel/instrument_panel_tools_edit_value.png) + +The selection list on the top left is used to change the source of the telemetry. +By default this is the vehicle, but you can use the selector to choose a particular sensor type. + +![Instrument Panel - value type](../../../assets/fly/instrument_panel/instrument_panel_edit_value_type.png) + +The selection list on the top right is used to select a particular telemetry value for the vehicle or sensor. + +![Instrument Panel - value options](../../../assets/fly/instrument_panel/instrument_panel_edit_value_options.png) diff --git a/docs/zh/qgc-user-guide/fly_view/video.md b/docs/zh/qgc-user-guide/fly_view/video.md new file mode 100644 index 00000000000..432252d5c7e --- /dev/null +++ b/docs/zh/qgc-user-guide/fly_view/video.md @@ -0,0 +1,58 @@ +# Video + +When video streaming is enabled (Application Settings - Video), _QGroundControl_ will display the video stream for the currently selected vehicle in the "video switcher window" at the bottom left of the map. +You can press the switcher anywhere to toggle _Video_ and _Map_ to foreground (in the image below, the video is shown in the foreground). + +![Video Stream Record](../../../assets/fly/video_record.jpg) + +:::info +Video streaming is configured/enabled in [Application Settings > General tab > Video](../settings_view/general.md#video). +::: + +You can further configure video display using controls on the switcher: + +![Video Pop](../../../assets/fly/video_pop.jpg) + +- Resize the switcher by dragging the icon in the top right corner. +- Hide the switcher by pressing the toggle icon in the lower left. +- Detach the video switcher window by pressing on the icon in its top left corner + (once detached, you can move and resize the window just like any other in your OS). + If you close the detached window the switcher will re-lock to the QGC Fly view. + +### Record Video + +If supported by the camera and vehicle, _QGroundControl_ can start and stop video recording on the camera itself. _QGroundControl_ can also record the video stream and save it locally. + +:::tip +Video stored on the camera may be of much higher quality, but it is likely that your ground station will have a much larger recording capacity. +::: + +#### Record Video Stream (on GCS) + +Video stream recording is controlled on the [video stream instrument page](#video_instrument_page). +Press the red circle to start recording a new video (a new video file is created each time the circle is pressed); the circle will change into a red square while recording is in progress. + +![Video Stream Record](../../../assets/fly/video_record.jpg) + +Video stream recording is configured in the [Application Settings > General tab](../settings_view/general.md): + +- [Video Recording](../settings_view/general.md#video-recording) - specifies the recording file format and storage limits. + + ::: info + Videos are saved in Matroska format (.mkv) by default. + This format is relatively robust against corruption in case of errors. + ::: + +- [Miscellaneous](../settings_view/general.md#miscellaneous) - Streamed video is saved under the **Application Load/Save Path**. + +:::tip +The stored video includes just the video stream itself. +To record video with QGroundControl application elements displayed, you should use separate screen recording software. +::: + +#### Record Video on Camera + +Start/stop video recording _on the camera itself_ using the [camera instrument page](#camera_instrument_page). +First toggle to video mode, then select the red button to start recording. + +![Instrument Page - Camera MAVLink Settings](../../../assets/fly/instrument_page_camera_mavlink.jpg) diff --git a/docs/zh/qgc-user-guide/getting_started/download_and_install.md b/docs/zh/qgc-user-guide/getting_started/download_and_install.md index 1c21c1f5813..22a452e1ea5 100644 --- a/docs/zh/qgc-user-guide/getting_started/download_and_install.md +++ b/docs/zh/qgc-user-guide/getting_started/download_and_install.md @@ -65,8 +65,8 @@ Before installing _QGroundControl_ for the first time: sudo usermod -a -G dialout $USER sudo apt-get remove modemmanager -y sudo apt install gstreamer1.0-plugins-bad gstreamer1.0-libav gstreamer1.0-gl -y - sudo apt install libqt5gui5 -y sudo apt install libfuse2 -y + sudo apt install libxcb-xinerama0 libxkbcommon-x11-0 libxcb-cursor-dev -y ``` 2. Logout and login again to enable the change to user permissions. @@ -82,6 +82,7 @@ Before installing _QGroundControl_ for the first time: **注意** QGroundControlControl在Catalina系统上如果没有被签名认证，会有些问题发生。 当您首次打开 QGC 应用： ``` +:::info There are known [video steaming issues](../troubleshooting/qgc_setup.md#dual_vga) on Ubuntu 18.04 systems with dual adaptors. ::: @@ -92,8 +93,6 @@ To run these versions on Ubuntu 16.04 you can [build QGroundControl from source ## Android {#android} -_QGroundControl_ is temporily unavailable from the Google Play Store. You can install manually from here: - - [Android 32 位 APK](https://qgroundcontrol.s3-us-west-2.amazonaws.com/latest/QGroundControl32.apk) - [Android 64 位 APK](https://qgroundcontrol.s3-us-west-2.amazonaws.com/latest/QGroundControl64.apk) diff --git a/docs/zh/qgc-user-guide/getting_started/quick_start.md b/docs/zh/qgc-user-guide/getting_started/quick_start.md index 40f6a752a7a..e5435d4f120 100644 --- a/docs/zh/qgc-user-guide/getting_started/quick_start.md +++ b/docs/zh/qgc-user-guide/getting_started/quick_start.md @@ -1,16 +1,16 @@ -# QGroundControl Quick Start +# QGroundControl快速上手指南 -Getting _QGroundControl_ up and running is quick and easy: +让 _QGroundControl_ 轻松入门上手使用： -1. [Download and install](../getting_started/download_and_install.md) the application. -1. Start _QGroundControl_. -1. Attach your vehicle to the ground station device via USB, through a telemetry radio, or over WiFi. _QGroundControl_ should detect your vehicle and connect to it automatically. +1. [Download and install (Daily 5.0)](../releases/daily_builds.md) the application. +2. 启动_QGroundControl_。 +3. Attach your vehicle to the ground station device via USB, through a telemetry radio, or over WiFi. _QGroundControl_ should detect your vehicle and connect to it automatically. -That's it! If the vehicle is ready to fly, _QGroundControl_ should display [Fly View](../fly_view/fly_view.md) as shown below (otherwise it will open [Setup View](../setup_view/setup_view.md)). +That's it! 就这么简单！ 如果设备准备飞行（无人机是飞，其它设备是运行），_QGroundControl_应显示如下[Fly View](../fly_view/fly_view.md) (否则将打开[Setup View](../setup_view/setup_view.md))。 ![](../../../assets/quickstart/fly_view_connected_vehicle.jpg) -A good way to become familiar with _QGroundControl_ is to start experimenting: +要想把_QGroundControl_玩的纯熟，最好方法是亲自上手折腾： - Use the View Selector to switch between main views: - Plan Flight @@ -21,6 +21,6 @@ A good way to become familiar with _QGroundControl_ is to start experimenting: While the UI is fairly intuitive, this documentation can also be referenced to find out more. -::: info +:::info Make sure QGC has an internet connection when you connect a new vehicle in order to display map content. ::: diff --git a/docs/zh/qgc-user-guide/index.md b/docs/zh/qgc-user-guide/index.md index 5856f39765e..d71334d8ec4 100644 --- a/docs/zh/qgc-user-guide/index.md +++ b/docs/zh/qgc-user-guide/index.md @@ -1,6 +1,9 @@ -# QGroundControl用户指南 +# QGroundControl Guide (Daily Build 5.0) -[![Releases](https://img.shields.io/github/release/mavlink/QGroundControl.svg)](https://github.com/mavlink/QGroundControl/releases) [![Discuss](https://img.shields.io/badge/discuss-px4-ff69b4.svg)](http://discuss.px4.io/c/qgroundcontrol/qgroundcontrol-usage) [![Discuss](https://img.shields.io/badge/discuss-ardupilot-ff69b4.svg)](http://discuss.ardupilot.org/c/ground-control-software/qgroundcontrol) [![Gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/mavlink/qgroundcontrol?utm_source=badge\&utm_medium=badge\&utm_campaign=pr-badge\&utm_content=badge) [![Slack](../../assets/site/slack.svg)](https://join.slack.com/t/px4/shared_invite/zt-si4xo5qs-R4baYFmMjlrT4rQK5yUnaA) +[![Discuss](https://img.shields.io/badge/discuss-px4-ff69b4.svg)](http://discuss.px4.io/c/qgroundcontrol/qgroundcontrol-usage) +[![Discuss](https://img.shields.io/badge/discuss-ardupilot-ff69b4.svg)](http://discuss.ardupilot.org/c/ground-control-software/qgroundcontrol) + +_You are viewing the docs for the upcoming 5.0 release of QGroundControl. If you want docs for a Stable build select from the Version dropdown above._ _QGroundControl_ 向PX4 或 ArduPilot 驱动的载具平台提供了全方位的飞行控制接口和载具设置接口。 它为初学者提供了方便直接的使用方法，同时仍然为有经验的用户提供高端功能支持。 It provides easy and straightforward usage for beginners, while still delivering high end feature support for experienced users. @@ -11,6 +14,7 @@ It provides easy and straightforward usage for beginners, while still delivering - 支持运行PX4和ArduPilot的载具(或使用MAVLink协议通信的任何其他自动驾驶仪)。 - 自主飞行的任务规划。 - 飞行地图上可显示载具的位置、飞行轨迹、航点和仪表盘等。 +- 3D viewer visualizing the 3D map of the environment (.osm file), the 3D model of the vehicle (only multi-rotors for the moment), and the mission 3D trajectory (including the waypoints). - Video streaming with instrument display overlays. - Support for managing multiple vehicles. - QGC 可运行于Windows, OS X, Linux平台, iOS 和 Android 设备。 diff --git a/docs/zh/qgc-user-guide/plan_view/pattern.md b/docs/zh/qgc-user-guide/plan_view/pattern.md index e698bfc2d0f..9bc7dc2455f 100644 --- a/docs/zh/qgc-user-guide/plan_view/pattern.md +++ b/docs/zh/qgc-user-guide/plan_view/pattern.md @@ -5,9 +5,9 @@ The available pattern tools depend on the vehicle (and support for the vehicle-t ![Pattern Tool (Plan Tools)](../../../assets/plan/pattern/pattern_tool.jpg) -| Pattern | Description | Vehicles | -| ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | +| Pattern | Description | Vehicles | +| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | | [Survey](../plan_view/pattern_survey.md) | Create a grid flight pattern over a polygonal area. You can specify the polygon as well as the specifications for the grid and camera settings appropriate for creating geotagged images. | All | | [Structure Scan](../plan_view/pattern_structure_scan_v2.md) | Create a grid flight pattern that captures images over vertical surfaces (polygonal or circular). These are typically used for the visual inspection or creation of 3D models of structures. | MultiCopter, VTOL | -| [Corridor Scan](../plan_view/pattern_corridor_scan.md) | Create a flight pattern which follows a poly-line (for example, to survey a road). | All | -| [Fixed Wing Landing](../plan_view/pattern_fixed_wing_landing.md) | Add a landing pattern for fixed wing vehicles to a mission. | Fixed Wing | +| [Corridor Scan](../plan_view/pattern_corridor_scan.md) | Create a flight pattern which follows a poly-line (for example, to survey a road). | All | +| [Fixed Wing Landing](../plan_view/pattern_fixed_wing_landing.md) | Add a landing pattern for fixed wing vehicles to a mission. | Fixed Wing | diff --git a/docs/zh/qgc-user-guide/plan_view/plan_view.md b/docs/zh/qgc-user-guide/plan_view/plan_view.md index 015fb3e4b2b..b0e211e7f53 100644 --- a/docs/zh/qgc-user-guide/plan_view/plan_view.md +++ b/docs/zh/qgc-user-guide/plan_view/plan_view.md @@ -199,5 +199,5 @@ To analyse this possibility you can turn on [Console Logging](../settings_view/c ## Further Info -- New Plan View features for [QGC release v3.2](../releases/stable_v3.2_long.md#plan_view) -- New Plan View features for [QGC release v3.3](../releases/stable_v3.3_long.md#plan_view) +- New Plan View features for [QGC release v3.2](../qgc-user-guide/releases/release_note_stable_v3.md#plan_view) +- New Plan View features for [QGC release v3.3](../qgc-user-guide/releases/release_note_stable_v3.md#plan-view-1) diff --git a/docs/zh/qgc-user-guide/releases/daily_builds.md b/docs/zh/qgc-user-guide/releases/daily_builds.md index 0550549176e..d821dea7b8d 100644 --- a/docs/zh/qgc-user-guide/releases/daily_builds.md +++ b/docs/zh/qgc-user-guide/releases/daily_builds.md @@ -10,23 +10,12 @@ Use at your own risk! These can be downloaded from the links below (install as described in [Download and Install](../getting_started/download_and_install.md)): - [Windows](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl-installer.exe) - - [OS X](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl.dmg) - - ::: info - QGroundControl continues to not be signed which causes problem on Catalina. To open QGC app for the first time: - - - Right-click the QGC app icon, select Open from the menu. You will only be presented with an option to Cancel. Select Cancel. - - Right-click the QGC app icon again, Open from the menu. This time you will be presented with the option to Open. - - ::: - -- [Linux](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl.AppImage) - -- [Android](https://play.google.com/store/apps/details?id=org.mavlink.qgroundcontrolbeta) - Google Play: Listed as _QGroundControl (Daily Test Build)_. - +- [Linux](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl-x86_64.AppImage) - Before running do the following: + - `chmod +x QGroundControl.AppImage` + - On the command prompt enter (one time only): + \- `sudo usermod -a -G dialout $USER` + \- `sudo apt-get remove modemmanager -y` + \- Logout and login again to enable the change to user permissions. +- [Android](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl.apk) - iOS currently unavailable - -:::info -The QGroundControl Continous Delivery pipeline from time to time might experience issues uploading to the Google Play store. You can find the daily build APK for Android devices for direct download here: [QGroundControl32.apk](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl32.apk), and [QGroundControl64.apk](https://d176tv9ibo4jno.cloudfront.net/builds/master/QGroundControl64.apk) -::: diff --git a/docs/zh/qgc-user-guide/releases/privacy_policy.md b/docs/zh/qgc-user-guide/releases/privacy_policy.md index 44718df6e95..e9b88a034ec 100644 --- a/docs/zh/qgc-user-guide/releases/privacy_policy.md +++ b/docs/zh/qgc-user-guide/releases/privacy_policy.md @@ -1,8 +1,69 @@ # Privacy Policy +Dronecode Project, Inc. built the QGroundControl (org.mavlink.qgroundcontrol) app as an Open Source app. This SERVICE is provided by Dronecode Project, Inc. at no cost and is intended for use as is. + +This page is used to inform visitors regarding our policies with the collection, use, and disclosure of Personal Information if anyone decided to use our Service. + +If you choose to use our Service, then you agree to the collection and use of information in relation to this policy. The Personal Information that we collect is used for providing and improving the Service. We will not use or share your information with anyone except as described in this Privacy Policy. + +The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, which are accessible at QGroundControl (org.mavlink.qgroundcontrol) unless otherwise defined in this Privacy Policy. + +**Information Collection and Use** + +For a better experience, while using our Service, we may require you to provide us with certain personally identifiable information, including but not limited to device data. The information that we request will be retained by us and used as described in this privacy policy. + _QGroundControl_ may require access to personal and/or sensitive user data. None of this data is used outside of _QGroundControl_. The list below explains how some of the data is used: -- Camera sensor: This is used for the purpose of overlaying the video with flight telemetry data. -- Location: This is used for tracking current user position on the map. +- Camera sensor: This is used to overlay the video with flight telemetry data. +- Location: This is used for tracking the current user position on the map. + +The app does use third-party services that may collect information used to identify you. + +Link to the privacy policy of third-party service providers used by the app + +- [Google Play Services](https://www.google.com/policies/privacy/) + +**Log Data** + +We want to inform you that whenever you use our Service, in a case of an error in the app we collect data and information (through third-party products) on your phone called Log Data. This Log Data may include information such as your device Internet Protocol (“IP”) address, device name, operating system version, the configuration of the app when utilizing our Service, the time and date of your use of the Service, and other statistics. + +**Cookies** + +Cookies are files with a small amount of data that are commonly used as anonymous unique identifiers. These are sent to your browser from the websites that you visit and are stored on your device's internal memory. + +This Service does not use these “cookies” explicitly. However, the app may use third-party code and libraries that use “cookies” to collect information and improve their services. You have the option to either accept or refuse these cookies and know when a cookie is being sent to your device. If you choose to refuse our cookies, you may not be able to use some portions of this Service. + +**Service Providers** + +We may employ third-party companies and individuals due to the following reasons: + +- To facilitate our Service; +- To provide the Service on our behalf; +- To perform Service-related services; or +- To assist us in analyzing how our Service is used. + +We want to inform users of this Service that these third parties have access to their Personal Information. The reason is to perform the tasks assigned to them on our behalf. However, they are obligated not to disclose or use the information for any other purpose. + +**Security** + +We value your trust in providing us your Personal Information, thus we are striving to use commercially acceptable means of protecting it. But remember that no method of transmission over the internet, or method of electronic storage is 100% secure and reliable, and we cannot guarantee its absolute security. + +**Links to Other Sites** + +This Service may contain links to other sites. If you click on a third-party link, you will be directed to that site. Note that these external sites are not operated by us. Therefore, we strongly advise you to review the Privacy Policy of these websites. We have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services. + +**Children’s Privacy** + +These Services do not address anyone under the age of 13. We do not knowingly collect personally identifiable information from children under 13 years of age. In the case we discover that a child under 13 has provided us with personal information, we immediately delete this from our servers. If you are a parent or guardian and you are aware that your child has provided us with personal information, please contact us so that we will be able to do the necessary actions. + +**Changes to This Privacy Policy** + +We may update our Privacy Policy from time to time. Thus, you are advised to review this page periodically for any changes. We will notify you of any changes by posting the new Privacy Policy on this page. + +This policy is effective as of 2024-03-12 + +**Contact Us** + +If you have any questions or suggestions about our Privacy Policy, do not hesitate to contact us at info@dronecode.org. diff --git a/docs/zh/qgc-user-guide/releases/release_note_stable_v3.md b/docs/zh/qgc-user-guide/releases/release_note_stable_v3.md new file mode 100644 index 00000000000..f20e051fc1a --- /dev/null +++ b/docs/zh/qgc-user-guide/releases/release_note_stable_v3.md @@ -0,0 +1,564 @@ +# QGC v3 Release Notes + +This topic contains the cumulative release notes for _QGroundControl v3.x_. + +## Stable Version 3.5 + +This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.5. + +- **Overall** + - Added Airmap integration to QGC. OSX build only. + - Bumped settings version (now 8). + This will cause all settings to be reset to defaults. + - Added Chinese and Turkish localization and partial German localization. + - Added support for the Taisync 2.4GHz ViUlinx digital HD wireless link. + - Fix loading of parameters from multiple components. + This especially affected WiFi connections. + - **ArduPilot** Support for ChibiOS firmware connect and flash. +- **Settings** + - **RTK** Add support for specifying fixed RTK based station location in Settings/General. + - **GCS Location** + - Added UDP Port option for NMEA GPS Device. + - GCS heading shown if available +- **Plan** + - **Polygons** Support loading polygons from SHP files. + - **Fixed Wing Landing Pattern** Add stop photo/video support. + Defaults to on such that doing an RTL will stop camera. + - **Edit Position dialog** Available on polygon vertices. +- **Fly** + - **Camera Page** Updated support for new MAVLInk camera messages. + Camera select, camera mode, start/stop photo/video, storage mangement... + - **Orbit** Support for changing rotation direction. + - **Instrument Panel** + - Added ESTIMATOR_STATUS values to new estimatorStatus Vehicle FactGroup. + These are now available to display in instrument panel. + - Make Distance to GCS available for display from instrument panel. + - Make Heading to Home available for display from instrument panel. + +## Stable Version 3.4 + +This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.4. Not to mention the large number of bug fixes in each stable release. + +- **Settings** + - **Offline Maps** + - Center Tool allows you to specify a map location in lat/lon or UTM coordinates. Making it easier to get to the location you want to create an offline map for. + - Ability to pre-download terrain heights for offline use. + - **Help** Provides links to QGC user guide and forums. + +- **Setup** + - **Firmware** Ability to flash either PX4 or ArduPilot Flow firmware. + - PX4 Pro Firmware + - **Flight Modes** Specify channels for all available transmitter switches. + - **Tuning: Advanced** Initial implementation of vehicle PID tuning support. Note that this is a work in progress that will improve in 3.5 daily builds. + - ArduPilot Firmware + - **Power/Safety** Support for new multi-battery setup. + - **Trad Heli** New setup page. + +- **Plan** + + - **File Load/Save** New model for Plan file loading which matches a standard File Load/Save/Save As user model. + + - **Load KML** Ability to load a KML file directly from the Sync menu. You will be prompted for what type of Pattern you want to create from the KML if needed. + + - **Survey** Better support for irregular shaped polygons. + + - **[Corridor Scan](../plan_view/pattern_corridor_scan.md)** - Create a flight pattern which follows a poly-line. For example can be used to survey a road. + + - **[Fixed Wing Landing Pattern](../plan_view/pattern_fixed_wing_landing.md)** + - Landing area visually represented in Plan. + - Landing position/heading can be copied from Vehicle position/heading. + + - **Terrain** + + - Height of mission items can be specified as height above terrain. + - Survey and Corridor Scan can generate flight plans which follow terrain. + + ::: info + This feature does not support [ArduPilot terrain following](http://ardupilot.org/copter/docs/common-terrain-following.html). + ::: + + - **Edit Position** Set item position from vehicle position. + +- **Fly** + - **Pre-Flight Checklist** You can turn this on from Settings. It provides a generic checklist to follow prior to flight. Expect more feature to appear for this in 3.5 daily builds. + - **Instrument Panel** + - Many new values available for display. + - New Camera page which provides full camera control. Requires a camera which support new MavLink camera specification. + - **ArduPlane** Much better support for guided commands including QuadPlane support. + - **High Latency Links** Support for high latency links such as satellite connections. + Limits the traffic from QGC up to Vehicle on these links to reduce cost. + Supports HIGH_LATENCY MavLink message. + Supports failover back/forth from high latency to normal link with dual link setup. + +## Stable Version 3.3 (Summary) + +:::tip +More detailed release notes for version 3.3 can be found in the next section. +::: + +This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.3. Not to mention the large number of bug fixes of this release. + +- **Settings** + - Local NMEA GPS device support. + - Video Recording save settings. +- **Setup** + - **Parameter Editor** - Searching updates as you type characters for near immediate response to searches. + - **Joystick** - Android joystick support. +- **Plan** + - **NEW - Structure Scan Pattern** - Create a multi-layered flight pattern that captures images over vertical surfaces (polygonal or circular). Used for 3d model generation or vertical surface inspection. + - **Fixed Wing Landing Pattern** - You can now adjust the distance from the loiter to land point by either distance or glide slope fall rate. + - PX4 GeoFence and Rally Point support. + - Terrain height display in lower Mission Item altitude display +- **Fly** + - Start/Stop video recording. + - Better display of vehicle icons when connected to multiple vehicles. + - Multi-Vehicle View supports commands which apply to all vehicles. + - Displays vehicles reported from ADS-B sensor. +- **Analyze** + - **Mavlink console** - New support for communicating with Mavlink console. + - **Log Download** - Moved from Menu to Analyze view. + +## Stable Version 3.3 (Detailed) + +### Settings View + +#### NMEA GPS Device support + +![NMEA GPS Device support](../../../assets/settings/general/NMEADevice.jpg) + +You can specify a connection to one of these devices on the General page. +The GPS information will then be used for ground station location and in turn follow me support. + +For more information see [Settings > General (AutoConnect to the following devices)](../settings_view/general.md#auto_connect). + +#### Video Recording + +![Video Recording](../../../assets/settings/video_recording.jpg) + +Videos will be saved to the Video directory of your QGC file save path. +You can also specify the maximum amount of space you want video files to consume. +After that size if exceeded the oldest video files will be removed. +Video Recording is turned on/off from the Video widget in the Fly View. + +For more information see [Settings > General (Video / Video Recording)](../settings_view/general.md#video). + +### Plan View + +#### Structure Scan + +A Structure Scan allows you to create a grid flight pattern that captures images over vertical surfaces (polygonal or circular). +These are typically used for the visual inspection or creation of 3d models of structures. + +Details [here](../plan_view/pattern_structure_scan_v2.md). + +#### New MAVLink GeoFence, Rally Point support + +![](../../../assets/plan/geofence_rally.jpg) + +QGC supports the new MAVLink GeoFence and Rally Point specification/protocol. This new system supports multiple polygonal and/or circular fences which can be specified as an exclusion or an inclusion fence. + +The fence which is currently selected by the "Edit" radio button will show the on screen editing controls such as the drag points for polygon editing. + +**Note** Only PX4 Pro firmware supports the new specification. ArduPilot does not yet support the new spec. Support for GeoFence/Rally is temporarily disabled in QGC until QGC ArduPilot code is reworked to the new architecture. + +#### Edit Position Dialog + +![](../../../assets/plan/edit_position_dialog.jpg) + +The Edit Position Dialog allows you to specify a detailed position for an item in either Geographic or UTM coordinate systems. It is available from the Polygon Tools menu as well as the hamburger menu of any mission item which specifies a coordinate: + +![](../../../assets/plan/mission_item_editor_hamburger.jpg) + +#### Polygon Tools + +![](../../../assets/plan/polygon_tools.jpg) + +You can now also click on the polygon center drag handle to bring up a set of polygon manipulation tools. The tools are available anywhere polygon editing is supported: Survey, Structure Scan, GeoFence, ... + +- Circle - Converts the polygon to a circular polygon. +- Polygon - Changes a circular polygon back to a rectangular polygon. +- Set radius - Set radius for circular polygons. +- Edit position - Displays the edit position dialog to specify a detailed position for the circular center. +- Load KML - Set polygon to polygon loaded from KML file. + +Circular polygon example: + + + +### Fly View + +#### Start/Stop Video Recording + +This is now a video record button in the video window. Settings for saved videos are available from General Page of Setup view. + +#### Multi-Vehicle vehicle indicators + +When you are connected to multiple vehicles the vehicle id will be shown below the vehicle icon. The active vehicle will be opaque and the inactive vehicles will be semi-transparent. + +![](../../../assets/fly/multi_vehicle_indicators.jpg) + +#### Multi-Vehicle View supports batch commands + +The multi-vehicle list now supports commands which apply to all vehicles. + +![](../../../assets/fly/multi_vehicle_list.jpg) + +The current list of available commands are Pause and Start Mission but that will be exapanded upon with further development. + +#### ADS-B sensor vehicle display + +Vehicle reported by ADS-B sensor on vehicle are shown on map as smaller blue icons with altitude and callsign below the icon. + +![](../../../assets/fly/adsb_vehicle.jpg) + +## Stable Version 3.2 (Summary) + +:::tip +More detailed release notes for version 3.2 can be found in the next section. +::: + +This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.2. + +- **Settings** + + - **File Save path** - Specify a save path for all files used by QGC. + - **Telemetry log auto-save** - Telemetry logs are now automatically saved without prompting. + - **AutoLoad Plans** - Used to automatically load a Plan onto a vehicle when it first connects. + - **RTK GPS** - Specify the Survey in accuracy and Minimum observation duration. + +- **Setup** + + - ArduPilot only + - **Pre-Flight Barometer and Airspeed calibration** - Now supported + - **Copy RC Trims** - Now supported + +- **Plan View** + + - **Plan files** - Missions are now saved as .plan files which include the mission, geo-fence and rally points. + - **Plan Toolbar** - New toolbar which shows you mission statistics and Upload button. + - **Mission Start** - Allows you to specify values such as flight speed and camera settings to start the mission with. + - **New Waypoint features** - Adjust heading and flight speed for each waypoint as well as camera settings. + - **Visual Gimbal direction** - Gimbal direction is shown on waypoint indicators. + - **Pattern tool** - Allows you to add complex patterns to a mission. + - Fixed Wing Landing (new) + - Survey (many new features) + - **Fixed Wing Landing Pattern** - Adds a landing pattern for fixed wings to your mission. + - **Survey** - New features + - **Take Images in Turnarounds** - Specify whether to take images through entire survey or just within each transect segment. + - **Hover and Capture** - Stop vehicle at each image location and take photo. + - **Refly at 90 degree offset** - Add additional pattern at 90 degree offset to original so get better image coverage. + - **Entry location** - Specify entry point for survey. + - **Polygon editing** - Simple on screen mechanism to drag, resize, add/remove points. Much better touch support. + +- **Fly View** + + - **Arm/Disarm** - Available from toolbar. + - **Guided Actions** - New action toolbar on the left. Supports: + - Takeoff + - Land + - RTL + - Pause + - Start Mission + - Resume Mission - after battery change + - Change Altitude + - Land Abort + - Set Waypoint + - Goto Location + - **Remove mission after vehicle lands** - Prompt to remove mission from vehicle after landing. + - **Flight Time** - Flight time is shown in instrument panel. + - **Multi-Vehicle View** - Better control of multiple vehicles. + +- **Analyze View** - New + + - **Log Download** - Moved to Analyze view from menu + - **Mavlink Console** - NSH shell access + +- **Support for third-party customized QGroundControl** + - Standard QGC supports multiple firmware types and multiple vehicle types. There is now support in QGC which allows a third-party to create their own custom version of QGC which is targeted specifically to their custom vehicle. They can then release their own version of QGC with their vehicle. + +## Stable Version 3.2 (Detailed) + +This is a more detailed high level (but still _non-exhaustive_) list of new features added to _QGroundControl_ in version 3.2. + +### Settings + +#### Telemetry log auto-save + +If you have _Save telemetry log after each flight_ turned on you will no longer be prompted as to where to save the log each time the vehicle disarms. +Logs will automatically be saved to the [Application Load/Save Path](../settings_view/general.md#load_save_path) + +For more information see [Settings > General (Miscellaneous)](../settings_view/general.md#autosave_log). + +#### AutoLoad plans + +If this setting is turned on, _QGroundControl_ will automatically upload a plan to the vehicle when it connects. +The plan file must be named **AutoLoad#.plan** where the `#` is replaced with the vehicle id. +The plan file must be located in the [Application Load/Save Path](../settings_view/general.md#load_save_path). + +For more information see [Settings > General (Miscellaneous)](../settings_view/general.md#autoload_missions). + +#### Application Load/Save Path + +You can now specify a save path which QGC will use as the default location to save files such as Parameters, Telemetry or Mission Plans. + +For more information see [Settings > General (Miscellaneous)](../settings_view/general.md#load_save_path). + +#### RTK GPS + +You can now specify the _Survey in accuracy_ and _Minimum observation duration_ for use with a connected RTK GPS. + +For more information see [Settings > General (RTK GPS)](../settings_view/general.md#rtk_gps). + +### Setup + +#### ArduPilot - Pre-Flight Barometer and Airspeed calibration + +This is now supported from the Sensors page. + +#### ArduPilot - Copy RC Trims + +This is now supported from the Copy Trims button on the Radio setup page. + +### Plan View + +#### Plan Files + +Previous version of _QGroundControl_ saved missions, geo-fences and rally points in separate files (**.mission**, **.fence**, **.rally**). QGC now save all information related to a flight plan into a single file called a _Plan File_ with a file extension of **.plan**. + +Information about the format can be found in [Plan File Format](../../qgc-dev-guide/file_formats/plan.md) (QGC Developer Guide). + +#### Plan Toolbar + +![Plan Toolbar](../../../assets/plan/plan_toolbar.jpg) + +The new _Plan Toolbar_ is displayed at the top of the [PlanView](../plan_view/plan_view.md). +It shows you information related to the currently selected waypoint as well as statistics for the entire mission. + +When connected to a vehicle it also shows an **Upload** button, which can be used to upload the plan to the vehicle. + +#### Mission Settings + +The [Mission Settings](../plan_view/plan_view.md#mission_settings) panel allows you to specify values which apply to the entire mission, or settings you want to control right at the beginning of a mission. +This is the first item in the mission list on the right of the screen. + + + +##### Mission Defaults + +###### Waypoint alt + +This specifies the default altitude for newly added mission items. +If you update this value while you have a mission loaded it will prompt you to update all the the waypoints to this new altitude. + +###### Flight speed + +This allows you to set the flight speed for the mission to be different than the default mission speed. + +###### RTL after mission end + +Check this if you want your vehicle to RTL after the final mission item. + +##### Camera section + + + +The camera section allows you to specify a camera action to take, control the gimbal and set your camera into photo or video mode. + +The camera actions available are: + +- Continue current action +- Take photos (time) +- Take photos (distance) +- Stop taking photos +- Start recording video +- Stop recording video + +##### Vehicle Info section + + + +When planning a mission the firmware being run on the vehicle as well as the vehicle type must be known in order for QGroundControl to show you the mission commands which are appropriate for your vehicle. + +If you are planning a mission while you are connected to your vehicle the Firmware and Vehicle Type will be determined from the vehicle. If you are planning a mission while not connected to a vehicle you will need to specify this information yourself. + +The additional value that can be specified when planning a mission is the vehicle flight speed. By specifying this value, total mission or survey times can be approximated even when not connected to a vehicle. + +##### Planned Home Position + + + +The planned home position allows you to simulate the vehicle's home position while planning a mission. This way you see the waypoint trajectory for your vehicle from takeoff to mission completion. Keep in mind that this is only the "planned" home position and you should place it where you plan to start the vehicle from. It has no actual impact on flying the mission. The actual home position of a vehicle is set by the vehicle itself when arming. + +#### New Waypoint features + + + +- You can now adjust heading and flight speed for each waypoint. +- There is a camera section available for camera changes on each waypoint. Explanation of Camera Section can be read under Mission Settings above. + +#### Visual Gimbal direction + + + +If you specify gimbal yaw changes on waypoints, both the plan and fly views will show you a visual representation of the gimbal direction. + +#### Pattern tool + +There is a new _Pattern tool_. The following patterns are supported: + +- Fixed Wing Landing (new) +- Survey (with new features) + +##### Fixed Wing Landing Pattern + +![Fixed Wing Landing Pattern](../../../assets/plan/pattern/fixed_wing_landing_pattern.jpg) + +This adds a landing pattern for fixed wings to your mission. +The first point of the pattern is the loiter point which commands to vehicle to loiter to a specific altitude. +Once that altitude is reached, the vehicle will begin the landing sequence and fly down to the specified landing spot. + +Both the loiter and land points can be dragged to adjust. +Also all the various values associated with the pattern can be adjusted. + +For more information see [Fixed Wing Landing Pattern](../plan_view/pattern_fixed_wing_landing.md). + +##### Survey (new features) + +- Images are not automatically taken in the turnaround zone outside of the polygonal survey area. +- There is a new _Hover and Capture_ option which can be used to capture the highest quality image at each image location. The vehicle will stop at each image location prior to taking the image such that the vehicle is stable while the image is taken. +- There is a new option to re-fly the survey grid at a 90 degree angle to the previous pass. This allows you to generate much denser coverage for the images. + +![](../../../assets/plan/polygon_edit.jpg) + +Manipulating the survey area polygon is now easier to use on tablets with touch screens: + +- You can drag the entire polygon to a new location by dragging the center point handle. +- Each polygon vertex can be dragged to a new location. +- To remove a polygon vertex, simple click on the drag handle for it. +- Click on the **+** handles to add a new vertex between two existing vertices. + +### Fly View + +#### RTK GPS + +RTK status is now shown in the toolbar. + +#### Arm/Disarm + +There is an armed/disarmed indicator in the toolbar. You can click it to arm/disarm your vehicle. If you click Disarm in the toolbar while your vehicle is flying you will provided the option to Emergency Stop your vehicle. + +#### Guided Actions + +- Takeoff +- Land +- RTL +- Pause +- Actions + - Start Mission + - Resume Mission + - Change Altitude + - Land Abort +- Direct interaction with map + - Set Waypoint + - Goto Location + +##### Resume Mission + +The Resume Mission guided action is used to resume a mission after performing an RTL from within the mission to perform a battery change. +After the vehicle lands from RTL and you have disconnected the battery **do not** disconnect QGC from the Vehicle. +Put in your new battery and QGC will detect the vehicle again and automatically restore the connection. +Once this happens you will be prompted with a Resume Mission confirmation slider. +If you want to resume the mission, confirm this and the mission will be rebuilt from your last waypoint traveled through. +Once the mission is rebuilt you will be presented with another Resume Mission slide which allows you to review the rebuilt mission before starting it again. +Confirm this Resume Mission slider to continue on with the mission. + +\####### How resume mission rebuilding works + +In order to resume a mission you cannot simply continue it from the last mission item the vehicle ran. +The reason is is that may skip over important change speed commands or camera control commands which are prior to that item in the mission. +If you skipped over those the remainder of the mission will not run correctly. +In order to make resume mission work correctly QGC rebuilds the mission looking backwards from the last mission item flown and automatically appends relevant commands to the front of the mission. +By doing this the state of the mission prior to the resume point is restore. +The following mission commands are the ones scanned for: + +- `MAV_CMD_DO_CONTROL_VIDEO` +- `MAV_CMD_DO_SET_ROI` +- `MAV_CMD_DO_DIGICAM_CONFIGURE` +- `MAV_CMD_DO_DIGICAM_CONTROL` +- `MAV_CMD_DO_MOUNT_CONFIGURE` +- `MAV_CMD_DO_MOUNT_CONTROL` +- `MAV_CMD_DO_SET_CAM_TRIGG_DIST` +- `MAV_CMD_DO_FENCE_ENABLE` +- `MAV_CMD_IMAGE_START_CAPTURE` +- `MAV_CMD_IMAGE_STOP_CAPTURE` +- `MAV_CMD_VIDEO_START_CAPTURE` +- `MAV_CMD_VIDEO_STOP_CAPTURE` +- `MAV_CMD_DO_CHANGE_SPEED` +- `MAV_CMD_NAV_TAKEOFF` + +#### Remove mission after vehicle lands + +You will be prompted to remove the mission from the vehicle after the mission completes and the vehicle lands and disarms. +This is meant to prevent issues where stale missions are unknowingly left on a vehicle cause unexpected behavior. + +#### Instrument panel + +##### Camera trigger + +##### Flight Time + +Flight time is now available for display in the instrument panel. +For new users, flight time will be shown by default. +For existing users who have already modified their instrument panel values you will have to add it yourself if you want to use it. + +### [Analyze View](../analyze_view/index.md) + +- [Log Download](../analyze_view/log_download.md) moved to _Analyze View_ from menu. +- New [GeoTag Images](../analyze_view/geotag_images.md) support for PX4 Pro firmware +- New [MAVLink Console](../analyze_view/mavlink_console.md) which provides access the the _nsh shell_ running on the vehicle. + +### Multi-Vehicle View + +There is a new view available when you have multiple vehicles connected to QGC. It will only show up when more than one vehicle is connected. When that happens you will see an additional set of radio button at the top right of the Plan view. + + + +Click the **Multi-Vehicle** radio button to replace the instrument panel with the multi-vehicle list: + + + +The example above shows three vehicles. The numbers are the vehicle id. In the large font is the current flight mode. You can click the flight mode name to change to a different flight mode. To the right are small version of the instruments for each vehicle. You can command the vehicle to do the following actions from the control panel: + +- Arm/Disarm +- Start/Stop a mission +- Return to Launch +- Take Control back of the vehicle by returning to manual control from a mission. + +#### Multi-Vehicle Gotchas - Unique vehicle ids + +Each vehicle connected to QGC must have a unique id. Otherwise QGC will think the vehicles are actually the same vehicle. The symptom of this is the Plan view jerking around as it tries to position itself to one vehicle and then the next. For PX4 Pro firmwares this is the `MAV_SYS_ID` parameter. For ArduPilot firmwares it is the `SYSID_THISMAV` parameter. + +### Support for third-party customized QGroundControl + +Standard QGC supports multiple firmware types and multiple vehicle types. There is now support in QGC which allows a third-party to create their own custom version of QGC which is targeted specifically to their custom vehicle. They can then release their own version of QGC with their vehicle. + +## Stable Version 3.1 + +New Features + +- [Survey](../plan_view/pattern_survey.md) mission support +- [GeoFence](../plan_view/plan_geofence.md) support in Plan View +- [Rally Point](../plan_view/plan_rally_points.md) support in Plan View (ArduPilot only) +- ArduPilot onboard compass calibration +- Parameter editor search will now search as you type for quicker access +- Parameter display now supports unit conversion +- GeoTag images from log files (PX4 only) +- System health in instrument panel +- MAVLink 2.0 support (no signing yet) + +Major Bug Fixes + +- Fixed crash after disconnect from Vehicle +- Fixed android crash when using SiK Radios +- Many multi-vehicle fixes +- Bluetooth fixes diff --git a/docs/zh/qgc-user-guide/releases/release_note_stable_v4.md b/docs/zh/qgc-user-guide/releases/release_note_stable_v4.md new file mode 100644 index 00000000000..873f71f3d98 --- /dev/null +++ b/docs/zh/qgc-user-guide/releases/release_note_stable_v4.md @@ -0,0 +1,58 @@ +# QGC v4 Release Notes + +:::warning +Release notes are now tracked in the [Github release page](https://github.com/mavlink/qgroundcontrol/releases). +See that page for information about changes after v4.0.0. +::: + +## Stable Version 4.0 + +:::info +The format for Settings in QGC had to change in this release. Which means all QGC settings will be reset to defaults. +::: + +- Settings + - Language: Allow selection of language + - Optional [CSV Logging](../settings_view/csv.md) of telemetry data for improved accessibility. + - ArduPilot + - Support configurable mavlink stream rates. Available from Settings/Mavlink page. + ![Stream Rates JPG](../../../assets/daily_build_changes/arducopter_stream_rates.jpg) + - Improved support for flashing ChibiOS firmware + - Improved support for connecting to ChibiOS bootloader boards +- Setup + - Joystick + - New joystick setup ui + - Ability to configure held button to single or repeated action + - ArduPilot + - Motor Test + - ArduSub + - Automatic motor direction detection + - ArduCopter + - PID Tuning support ![PID Tuning JPG](../../../assets/daily_build_changes/arducopter_pid_tuning.jpg) + - Additional Basic Tuning options ![Basic Tuning JPG](../../../assets/daily_build_changes/arducopter_basic_tuning.jpg) + - Copter/Rover - Frame setup ui ![Setup Frame Copter JPG](../../../assets/daily_build_changes/arducopter_setup_frame.jpg) +- Plan + - Create Plan from template with wizard like progression for completing full Plan. + - Survey: Save commonly used settings as a Preset + - Polygon editing + - New editing tools ui + - Support for tracing a polygon from map locations + - ArduPilot + - Support for GeoFence and Rally Points using latest firmwares and mavlink v2 + - [Pattern Presets](../plan_view/pattern_presets.md) + - Allows you to save settings for a Pattern item (Survey, Corridor Scan, ...) into a named preset. You can then use this preset over and over again as you create new Pattern. +- Fly + - Click to ROI support + - Added support for connecting to ADSB SBS server. Adds support for ADSB data from USB SDR Dongle running 'dump1090 --net' for example. + - Ability to turn on Heading to home, COG and Next Waypoint heading indicators in Compass. + - Video + - Add support for h.265 video streams + - Automatically add a [Video Overlay](../fly_view/video_overlay.md) with flight data as a subtitle for locally-recorded videos + - Vehicle type specific pre-flight checklists. Turn on from Settings. +- Analyze + - New Mavlink Inspector which includes charting support. Supported on all builds including Android and iOS. +- General + - Released Windows build are now 64 bit only + - Log Replay: Ability to specify replay speed + - ArduPilot + - Improved support for chibios firmwares and ArduPilot bootloader with respect to flashing and auto-connect. diff --git a/docs/zh/qgc-user-guide/releases/release_notes.md b/docs/zh/qgc-user-guide/releases/release_notes.md index b8512cb610c..63ba1f4bd9a 100644 --- a/docs/zh/qgc-user-guide/releases/release_notes.md +++ b/docs/zh/qgc-user-guide/releases/release_notes.md @@ -1,255 +1,7 @@ # Release Notes -This topic contains the cumulative release notes for _QGroundControl_. +Releases and their associated release notes can be found in the [Github releases page](https://github.com/mavlink/qgroundcontrol/releases). :::info -Stable build major/minor numbers are listed below. -_Patch_ release numbers are not listed, but can be found on the [Github release page](https://github.com/mavlink/qgroundcontrol/releases). +Release information about QGC v4.0.0 and earlier can be found in the sub pages. ::: - -## Stable Version 4.0 (current) - -:::info -The format for Settings in QGC had to change in this release. Which means all QGC settings will be reset to defaults. -::: - -- Settings - - Language: Allow selection of language - - Optional [CSV Logging](../settings_view/csv.md) of telemetry data for improved accessibility. - - ArduPilot - - Mavlink: Configurable stream rate settings -- Setup - - Joystick - - New joystick setup ui - - Ability to configure held button to single or repeated action - - ArduPilot - - Motor Test - - ArduSub - - Automatic motor direction detection -- Plan - - Create Plan from template with wizard like progression for completing full Plan. - - Survey: Save commonly used settings as a Preset - - Polygon editing - - New editing tools ui - - Support for tracing a polygon from map locations - - ArduPilot - - Support for GeoFence and Rally Points using latest firmwares and mavlink v2 -- Fly - - Click to ROI support - - Added support for connecting to ADSB SBS server. Adds support for ADSB data from USB SDR Dongle running 'dump1090 --net' for example. - - Ability to turn on Heading to home, COG and Next Waypoint heading indicators in Compass. - - Video - - Add support for h.265 video streams - - Automatically add a [Video Overlay](../fly_view/video_overlay.md) with flight data as a subtitle for locally-recorded videos - - Vehicle type specific pre-flight checklists. Turn on from Settings. -- Analyze - - New Mavlink Inspector which includes charting support. Supported on all builds including Android and iOS. -- General - - Released Windows build are now 64 bit only - - Log Replay: Ability to specify replay speed - - ArduPilot - - Improved support for chibios firmwares and ArduPilot bootloader with respect to flashing and auto-connect. - -Additional notes for some features can be found here: [v4.0 (Additional Notes)](../releases/stable_v4.0_additional.md). - -## Stable Version 3.5 - -This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.5. - -- **Overall** - - Added Airmap integration to QGC. OSX build only. - - Bumped settings version (now 8). - This will cause all settings to be reset to defaults. - - Added Chinese and Turkish localization and partial German localization. - - Added support for the Taisync 2.4GHz ViUlinx digital HD wireless link. - - Fix loading of parameters from multiple components. - This especially affected WiFi connections. - - **ArduPilot** Support for ChibiOS firmware connect and flash. -- **Settings** - - **RTK** Add support for specifying fixed RTK based station location in Settings/General. - - **GCS Location** - - Added UDP Port option for NMEA GPS Device. - - GCS heading shown if available -- **Plan** - - **Polygons** Support loading polygons from SHP files. - - **Fixed Wing Landing Pattern** Add stop photo/video support. - Defaults to on such that doing an RTL will stop camera. - - **Edit Position dialog** Available on polygon vertices. -- **Fly** - - **Camera Page** Updated support for new MAVLInk camera messages. - Camera select, camera mode, start/stop photo/video, storage mangement... - - **Orbit** Support for changing rotation direction. - - **Instrument Panel** - - Added ESTIMATOR_STATUS values to new estimatorStatus Vehicle FactGroup. - These are now available to display in instrument panel. - - Make Distance to GCS available for display from instrument panel. - - Make Heading to Home available for display from instrument panel. - -## Stable Version 3.4 - -This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.4. Not to mention the large number of bug fixes in each stable release. - -- **Settings** - - **Offline Maps** - - Center Tool allows you to specify a map location in lat/lon or UTM coordinates. Making it easier to get to the location you want to create an offline map for. - - Ability to pre-download terrain heights for offline use. - - **Help** Provides links to QGC user guide and forums. - -- **Setup** - - **Firmware** Ability to flash either PX4 or ArduPilot Flow firmware. - - PX4 Pro Firmware - - **Flight Modes** Specify channels for all available transmitter switches. - - **Tuning: Advanced** Initial implementation of vehicle PID tuning support. Note that this is a work in progress that will improve in 3.5 daily builds. - - ArduPilot Firmware - - **Power/Safety** Support for new multi-battery setup. - - **Trad Heli** New setup page. - -- **Plan** - - - **File Load/Save** New model for Plan file loading which matches a standard File Load/Save/Save As user model. - - - **Load KML** Ability to load a KML file directly from the Sync menu. You will be prompted for what type of Pattern you want to create from the KML if needed. - - - **Survey** Better support for irregular shaped polygons. - - - **[Corridor Scan](../plan_view/pattern_corridor_scan.md)** - Create a flight pattern which follows a poly-line. For example can be used to survey a road. - - - **[Fixed Wing Landing Pattern](../plan_view/pattern_fixed_wing_landing.md)** - - Landing area visually represented in Plan. - - Landing position/heading can be copied from Vehicle position/heading. - - - **Terrain** - - - Height of mission items can be specified as height above terrain. - - Survey and Corridor Scan can generate flight plans which follow terrain. - - ::: info - This feature does not support [ArduPilot terrain following](http://ardupilot.org/copter/docs/common-terrain-following.html). - ::: - - - **Edit Position** Set item position from vehicle position. - -- **Fly** - - **Pre-Flight Checklist** You can turn this on from Settings. It provides a generic checklist to follow prior to flight. Expect more feature to appear for this in 3.5 daily builds. - - **Instrument Panel** - - Many new values available for display. - - New Camera page which provides full camera control. Requires a camera which support new MavLink camera specification. - - **ArduPlane** Much better support for guided commands including QuadPlane support. - - **High Latency Links** Support for high latency links such as satellite connections. - Limits the traffic from QGC up to Vehicle on these links to reduce cost. - Supports HIGH_LATENCY MavLink message. - Supports failover back/forth from high latency to normal link with dual link setup. - -## Stable Version 3.3 - -:::tip -More detailed release notes for version 3.3 can be found [here](../releases/stable_v3.3_long.md). -::: - -This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.3. Not to mention the large number of bug fixes of this release. - -- **Settings** - - Local NMEA GPS device support. - - Video Recording save settings. -- **Setup** - - **Parameter Editor** - Searching updates as you type characters for near immediate response to searches. - - **Joystick** - Android joystick support. -- **Plan** - - **NEW - Structure Scan Pattern** - Create a multi-layered flight pattern that captures images over vertical surfaces (polygonal or circular). Used for 3d model generation or vertical surface inspection. - - **Fixed Wing Landing Pattern** - You can now adjust the distance from the loiter to land point by either distance or glide slope fall rate. - - PX4 GeoFence and Rally Point support. - - Terrain height display in lower Mission Item altitude display -- **Fly** - - Start/Stop video recording. - - Better display of vehicle icons when connected to multiple vehicles. - - Multi-Vehicle View supports commands which apply to all vehicles. - - Displays vehicles reported from ADS-B sensor. -- **Analyze** - - **Mavlink console** - New support for communicating with Mavlink console. - - **Log Download** - Moved from Menu to Analyze view. - -## Stable Version 3.2 - -:::tip -More detailed release notes for version 3.2 can be found [here](../releases/stable_v3.2_long.md). -::: - -This section contains a high level and _non-exhaustive_ list of new features added to _QGroundControl_ in version 3.2. - -- **Settings** - - - **File Save path** - Specify a save path for all files used by QGC. - - **Telemetry log auto-save** - Telemetry logs are now automatically saved without prompting. - - **AutoLoad Plans** - Used to automatically load a Plan onto a vehicle when it first connects. - - **RTK GPS** - Specify the Survey in accuracy and Minimum observation duration. - -- **Setup** - - - ArduPilot only - - **Pre-Flight Barometer and Airspeed calibration** - Now supported - - **Copy RC Trims** - Now supported - -- **Plan View** - - - **Plan files** - Missions are now saved as .plan files which include the mission, geo-fence and rally points. - - **Plan Toolbar** - New toolbar which shows you mission statistics and Upload button. - - **Mission Start** - Allows you to specify values such as flight speed and camera settings to start the mission with. - - **New Waypoint features** - Adjust heading and flight speed for each waypoint as well as camera settings. - - **Visual Gimbal direction** - Gimbal direction is shown on waypoint indicators. - - **Pattern tool** - Allows you to add complex patterns to a mission. - - Fixed Wing Landing (new) - - Survey (many new features) - - **Fixed Wing Landing Pattern** - Adds a landing pattern for fixed wings to your mission. - - **Survey** - New features - - **Take Images in Turnarounds** - Specify whether to take images through entire survey or just within each transect segment. - - **Hover and Capture** - Stop vehicle at each image location and take photo. - - **Refly at 90 degree offset** - Add additional pattern at 90 degree offset to original so get better image coverage. - - **Entry location** - Specify entry point for survey. - - **Polygon editing** - Simple on screen mechanism to drag, resize, add/remove points. Much better touch support. - -- **Fly View** - - - **Arm/Disarm** - Available from toolbar. - - **Guided Actions** - New action toolbar on the left. Supports: - - Takeoff - - Land - - RTL - - Pause - - Start Mission - - Resume Mission - after battery change - - Change Altitude - - Land Abort - - Set Waypoint - - Goto Location - - **Remove mission after vehicle lands** - Prompt to remove mission from vehicle after landing. - - **Flight Time** - Flight time is shown in instrument panel. - - **Multi-Vehicle View** - Better control of multiple vehicles. - -- **Analyze View** - New - - - **Log Download** - Moved to Analyze view from menu - - **Mavlink Console** - NSH shell access - -- **Support for third-party customized QGroundControl** - - Standard QGC supports multiple firmware types and multiple vehicle types. There is now support in QGC which allows a third-party to create their own custom version of QGC which is targeted specifically to their custom vehicle. They can then release their own version of QGC with their vehicle. - -## Stable Version 3.1 - -New Features - -- [Survey](../plan_view/pattern_survey.md) mission support -- [GeoFence](../plan_view/plan_geofence.md) support in Plan View -- [Rally Point](../plan_view/plan_rally_points.md) support in Plan View (ArduPilot only) -- ArduPilot onboard compass calibration -- Parameter editor search will now search as you type for quicker access -- Parameter display now supports unit conversion -- GeoTag images from log files (PX4 only) -- System health in instrument panel -- MAVLink 2.0 support (no signing yet) - -Major Bug Fixes - -- Fixed crash after disconnect from Vehicle -- Fixed android crash when using SiK Radios -- Many multi-vehicle fixes -- Bluetooth fixes diff --git a/docs/zh/qgc-user-guide/settings_view/console_logging.md b/docs/zh/qgc-user-guide/settings_view/console_logging.md index e2f23215edd..61f08b03ce0 100644 --- a/docs/zh/qgc-user-guide/settings_view/console_logging.md +++ b/docs/zh/qgc-user-guide/settings_view/console_logging.md @@ -10,15 +10,15 @@ Click the **Set Logging** button to enable/disable logging information displayed The most commmonly used logging options are listed below. -| Option(s) | Description | -| ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | -| `LinkManagerLog`, `MultiVehicleManagerLog` | Debug connection problems. | +| Option(s) | Description | +| ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | +| `LinkManagerLog`, `MultiVehicleManagerLog` | Debug connection problems. | | `LinkManagerVerboseLog` | Debug serial ports not being detected. Very noisy continuous output of available serial ports. | -| `FirmwareUpgradeLog` | Debug firmware flash issues. | -| `ParameterManagerLog` | Debug parameter load problems. | -| `ParameterManagerDebugCacheFailureLog` | Debug parameter cache crc misses. | -| `PlanManagerLog`, `MissionManagerLog`, `GeoFenceManagerLog`, `RallyPointManagerLog` | Debug Plan upload/download issues. | -| `RadioComponentControllerLog` | Debug Radio calibration issues. | +| `FirmwareUpgradeLog` | Debug firmware flash issues. | +| `ParameterManagerLog` | Debug parameter load problems. | +| `ParameterManagerDebugCacheFailureLog` | Debug parameter cache crc misses. | +| `PlanManagerLog`, `MissionManagerLog`, `GeoFenceManagerLog`, `RallyPointManagerLog` | Debug Plan upload/download issues. | +| `RadioComponentControllerLog` | Debug Radio calibration issues. | ## Logging from the Command Line diff --git a/docs/zh/qgc-user-guide/setup_view/flight_modes.md b/docs/zh/qgc-user-guide/setup_view/flight_modes.md index 4b956cd201d..889e6f19f2d 100644 --- a/docs/zh/qgc-user-guide/setup_view/flight_modes.md +++ b/docs/zh/qgc-user-guide/setup_view/flight_modes.md @@ -56,6 +56,6 @@ Commonly this is done by encoding the positions of a 2- and a 3-position switch On the FrSky Taranis this process involves assigning a "logical switch" to each combination of positions of the two real switches. Each logical switch is then assigned to a different PWM value on the same channel. -This video shows how this is done with the _FrSky Taranis_ transmitter: https\://youtu.be/TFEjEQZqdVA +This video shows how this is done with the _FrSky Taranis_ transmitter: https://youtu.be/TFEjEQZqdVA diff --git a/docs/zh/qgc-user-guide/setup_view/flight_modes_ardupilot.md b/docs/zh/qgc-user-guide/setup_view/flight_modes_ardupilot.md index 9a5b46b8408..87430e37cb1 100644 --- a/docs/zh/qgc-user-guide/setup_view/flight_modes_ardupilot.md +++ b/docs/zh/qgc-user-guide/setup_view/flight_modes_ardupilot.md @@ -42,6 +42,7 @@ To set the flight modes: All values are automatically saved as they are changed. +:::info The ArduCopter screenshot above shows a typical setup for a three position flight mode switch with an additional option of RTL being on a channel 7 switch. You can also setup 6 flight modes using two switches plus mixing on your transmitter. Scroll down to the center section of this [page](http://ardupilot.org/copter/docs/common-rc-transmitter-flight-mode-configuration.html#common-rc-transmitter-flight-mode-configuration) for tutorials on how to do that. ::: diff --git a/docs/zh/qgc-user-guide/setup_view/joystick.md b/docs/zh/qgc-user-guide/setup_view/joystick.md index 6fae0f0511d..c1d9d1fb712 100644 --- a/docs/zh/qgc-user-guide/setup_view/joystick.md +++ b/docs/zh/qgc-user-guide/setup_view/joystick.md @@ -18,7 +18,7 @@ The joystick is _enabled_ as the last step of the calibration process. ## Enabling PX4 Joystick Support -To enable Joystick support in PX4 you need to set the parameter [`COM_RC_IN_MODE`](h[ttp://localhost:8080/px4_user_guide/en](https://docs.px4.io/en/main/advanced_config/parameter_reference.html#COM_RC_IN_MODE) to `1` - _Joystick_. +To enable Joystick support in PX4 you need to set the parameter [`COM_RC_IN_MODE`](https://docs.px4.io/en/main/advanced_config/parameter_reference.html#COM_RC_IN_MODE) to `1` - _Joystick_. If this parameter is `0` then _Joystick_ will not be offered as a setup option. This is enabled by default for PX4 SITL builds (see the [Parameters](../setup_view/parameters.md) topic for information on how to find and set a particular parameter). diff --git a/docs/zh/qgc-user-guide/setup_view/motors.md b/docs/zh/qgc-user-guide/setup_view/motors.md index e190dca8b4e..0e4bdc0136e 100644 --- a/docs/zh/qgc-user-guide/setup_view/motors.md +++ b/docs/zh/qgc-user-guide/setup_view/motors.md @@ -21,14 +21,19 @@ To test the motors: 2. (_PX4-only_) Enable safety switch - if used. -3. Slide the switch to enable motor sliders (labeled: _Propellers are removed - Enable motor sliders_). +3. Slide the switch to enable motor slider and buttons (labeled: _Propellers are removed - Enable slider and motors_). -4. Adjust the individual sliders to spin the motors and confirm they spin in the correct direction. +4. Adjust the slider to select the power for the motors. + +5. Press the button corresponding to the motor and confirm it spin in the correct direction. ::: info - The motors only spin after you release the slider and will automatically stop spinning after 3 seconds. + The motors will automatically stop spinning after 3 seconds. + You can also stop the motor by pressing the 'Stop' button. + If no motors turn, raise the “Throttle %” and try again. ::: ## Additional Information - [Basic Configuration > Motor Setup](http://docs.px4.io/master/en/config/motors.html) (_PX4 User Guide_) - This contains additional PX4-specific information. +- [ESCS and Motors](https://ardupilot.org/copter/docs/connect-escs-and-motors.html#motor-order-diagrams) - This is the Motor order diagrams for all frames diff --git a/docs/zh/qgc-user-guide/setup_view/parameters.md b/docs/zh/qgc-user-guide/setup_view/parameters.md index 8bee143e3c8..85b0b8e6148 100644 --- a/docs/zh/qgc-user-guide/setup_view/parameters.md +++ b/docs/zh/qgc-user-guide/setup_view/parameters.md @@ -38,6 +38,6 @@ You can select additional options from the **Tools** menu on the top right hand **Load from file / Save to file**
Load parameters from an existing file or save your current parameter settings to a file. -**Clear RC to Param**
This clears all associations between RC transmitter controls and parameters. For more information see: [Radio Setup > Param Tuning Channels](../setup_view/Radio.md#param-tuning-channels-px4). +**Clear RC to Param**
This clears all associations between RC transmitter controls and parameters. For more information see: [Radio Setup > Param Tuning Channels](../setup_view/radio.md#param-tuning-channels-px4). **Reboot Vehicle**
Reboot the vehicle (required after changing some parameters). diff --git a/docs/zh/qgc-user-guide/setup_view/tuning_px4.md b/docs/zh/qgc-user-guide/setup_view/tuning_px4.md index 6be4cf09c36..03c07f319c9 100644 --- a/docs/zh/qgc-user-guide/setup_view/tuning_px4.md +++ b/docs/zh/qgc-user-guide/setup_view/tuning_px4.md @@ -36,7 +36,7 @@ To make sure the vehicle is stable enough for auto-tuning: 3. Use the RC transmitter roll stick to perform the following maneuver, tilting the vehicle just a few degrees: _roll left > roll right > center_ (The whole maneuver should take about 3 seconds). The vehicle should stabilise itself within 2 oscillations. 4. Repeat the maneuver, tilting with larger amplitudes at each attempt. - If the vehicle can stabilise itself within 2 oscillations at \~20 degrees move to the next step. + If the vehicle can stabilise itself within 2 oscillations at ~20 degrees move to the next step. 5. Repeat the same maneuvers but on the pitch axis. As above, start with small angles and confirm that the vehicle can itself within 2 oscillations before increasing the tilt. diff --git a/docs/zh/qgc-user-guide/viewer_3d/viewer_3d.md b/docs/zh/qgc-user-guide/viewer_3d/viewer_3d.md new file mode 100644 index 00000000000..f90339efe72 --- /dev/null +++ b/docs/zh/qgc-user-guide/viewer_3d/viewer_3d.md @@ -0,0 +1,53 @@ +# 3D View + +The 3D View is used to visualize and monitor the vehicle, the environment, and the planned mission in 3D. Most of the capabilities available in the [Fly View](../fly_view/fly_view.md) is also available in the 3D View. + +You can use it to: + +- To import and display the 3D map for any region of interest downloaded from the OpenStreetMap website (.osm file). +- Display the vehicle along with its mission in 3D. +- And most of the capabilities of the [Fly View](../fly_view/fly_view.md), including: + - Run an automated [pre-flight checklist](#preflight_checklist). + - Arm the vehicle (or check why it won't arm). + - Control missions: [start](#start_mission), [continue](#continue_mission), [pause](#pause), and [resume](#resume_mission). + - Guide the vehicle to [arm](#arm)/[disarm](#disarm)/[emergency stop](#emergency_stop), [takeoff](#takeoff)/[land](#land), [change altitude](#change_altitude), and [return/RTL](#rtl). + - Switch between a map view and a video view (if available) + - Display video, mission, telemetry, and other information for the current vehicle, and also switch between connected vehicles. + +![3D View](../../../assets/viewer_3d/viewer_3d_overview.jpg) + +# UI Overview + +The screenshot above shows the main elements of the 3D View. + +**Enabling the 3D View:** The 3D View is disabled by default. To enable it, go to **Application Settings** ->**Fly View** tab, and under the **3D View** settings group, toggle the **Enabled** switch as shown below: + +![3D View](../../../assets/viewer_3d/enable_3d_view.jpg) + +To open the 3D View, when you are in the [Fly View](../fly_view/fly_view.md), from the toolbar on the left, select the 3D View icon as illustrated below: + +![3D View](../../../assets/viewer_3d/open_3d_viewer.jpg) + +Once the 3D View is opened, you can navigate through the 3D environment by using either a mouse or a touchscreen as follows: + +- **Mouse:** + - **To move horizontally and vertically**: Press and hold the mouse left-click, then move the cursor. + - **To rotate**: Press and hold the mouse right-click, then move the cursor. + - **To zoom**: Use the mouse wheel\middle button. + +- **Touchscreen:** + - **To move horizontally and vertically**: Use a single finger, then tap and move your finger. + - **To rotate**: Use two fingers, then tap and move your fingers while keeping them together. + - **To zoom**: Use a pinch with two fingers and move them together or apart to zoom in or out. + +To visualize the 3D map of a particular area in the 3D viewer, you have to download the .osm file of that area from the [OpenStreetMap](https://www.openstreetmap.org/#map=16/47.3964/8.5498) website and then import it through the **3D View** settings. More details on the **3D View** settings can be found in the next section. + +# Settings + +You can change the settings of the 3D View from **Application Settings** ->**Fly View** tab under the **3D View** settings group. +The following properties can be modified in the 3D View settings group: + +- **Enabled**: To enable or disable the 3D View. +- **3D Map File**: The path to the .osm file of a region of interest to be visualized in the QGC. The .osm file can be uploaded by clicking on the **Select File** button. To clear the 3D View from the previously loaded .osm file, you can click on the **Clear** button. +- **Average Building Level Height**: This parameter determines the height of each storey of the buildings, as in .osm file sometimes the height of the buildings is specified in terms of the level/storey. +- **Vehicle Altitude Bias**: This refers to the bias in the altitude of vehicles and their missions with respect to the ground level. It is helpful in cases where the estimated altitude of the vehicle by its flight control is biased, as the relative altitude is currently used in the 3D View. diff --git a/src/FlightMap/FlightMap.qml b/src/FlightMap/FlightMap.qml index cc1693a8996..78c5cce605f 100644 --- a/src/FlightMap/FlightMap.qml +++ b/src/FlightMap/FlightMap.qml @@ -146,27 +146,54 @@ Map { property: "zoomLevel" } - DragHandler { - target: null + // We specifically do not use a DragHandler for panning. It just causes too many problems if you overlay anything else like a Flickable above it. + // Causes all sorts of crazy problems where dragging/scrolling no longerr works on items above in the hierarchy. + // Since we are using a MouseArea we also can't use TapHandler for clicks. So we handle that here as well. + MultiPointTouchArea { + anchors.fill: parent + maximumTouchPoints: 1 + mouseEnabled: true + + property bool dragActive: false + property real lastMouseX + property real lastMouseY + + onPressed: (touchPoints) => { + console.log("onPressed", touchPoints[0].x, touchPoints[0].y) + lastMouseX = touchPoints[0].x + lastMouseY = touchPoints[0].y + } - onActiveChanged: { - if (active) { - mapPanStart() - } else { - mapPanStop() + onGestureStarted: (gesture) => { + dragActive = true + gesture.grab() + mapPanStart() + } + + onUpdated: (touchPoints) => { + console.log("onUpdated", touchPoints[0].x, touchPoints[0].y, lastMouseX, lastMouseY) + if (dragActive) { + let deltaX = touchPoints[0].x - lastMouseX + let deltaY = touchPoints[0].y - lastMouseY + if (Math.abs(deltaX) >= 1.0 || Math.abs(deltaY) >= 1.0) { + _map.pan(lastMouseX - touchPoints[0].x, lastMouseY - touchPoints[0].y) + lastMouseX = touchPoints[0].x + lastMouseY = touchPoints[0].y + } } } - onActiveTranslationChanged: (delta) => { - console.log("onActiveTranslationChanged", delta) - _map.pan(-delta.x, -delta.y) + onReleased: (touchPoints) => { + if (dragActive) { + _map.pan(lastMouseX - touchPoints[0].x, lastMouseY - touchPoints[0].y) + dragActive = false + mapPanStop() + } else { + mapClicked(Qt.point(touchPoints[0].x, touchPoints[0].y)) + } } } - TapHandler { - onTapped: (eventPoint) => mapClicked(eventPoint.position) - } - /// Ground Station location MapQuickItem { anchorPoint.x: sourceItem.width / 2 diff --git a/src/Joystick/JoystickAndroid.cc b/src/Joystick/JoystickAndroid.cc index 36548b52d32..aaa58b88244 100644 --- a/src/Joystick/JoystickAndroid.cc +++ b/src/Joystick/JoystickAndroid.cc @@ -224,9 +224,7 @@ bool JoystickAndroid::_getHat(int hat, int i) const bool JoystickAndroid::init() { - static QList ret(_androidBtnListCount); - - _androidBtnList = ret; + QList ret(_androidBtnListCount); (void) AndroidInterface::cleanJavaException(); @@ -258,6 +256,8 @@ bool JoystickAndroid::init() AXIS_HAT_X = QJniObject::getStaticField("android/view/MotionEvent", "AXIS_HAT_X"); AXIS_HAT_Y = QJniObject::getStaticField("android/view/MotionEvent", "AXIS_HAT_Y"); + _androidBtnList = ret; + return true; }