New Crowdin updates (#11025)
* New translations index.md (Korean) * New translations index.md (Turkish) * New translations index.md (Chinese Simplified) * New translations command_line_options.md (Korean) * New translations command_line_options.md (Turkish) * New translations command_line_options.md (Chinese Simplified) * New translations unit_tests.md (Chinese Simplified) * New translations custom_build.md (Chinese Simplified) * New translations mavlink.md (Korean) * New translations mavlink.md (Turkish) * New translations mavlink.md (Chinese Simplified) * New translations release_branching_process.md (Korean) * New translations release_branching_process.md (Turkish) * New translations release_branching_process.md (Chinese Simplified) * New translations parameters.md (Chinese Simplified) * New translations plan.md (Korean) * New translations plan.md (Turkish) * New translations plan.md (Chinese Simplified) * New translations index.md (Korean) * New translations index.md (Turkish) * New translations index.md (Chinese Simplified) * New translations release_branching_process.md (Korean) * New translations release_branching_process.md (Turkish) * New translations release_branching_process.md (Chinese Simplified) * New translations log_download.md (Korean) * New translations fly_view.md (Korean) * New translations fly_view.md (Turkish) * New translations fly_view.md (Chinese Simplified) * New translations download_and_install.md (Korean) * New translations download_and_install.md (Turkish) * New translations download_and_install.md (Chinese Simplified) * New translations quick_start.md (Korean) * New translations quick_start.md (Turkish) * New translations quick_start.md (Chinese Simplified) * New translations pattern.md (Korean) * New translations pattern.md (Turkish) * New translations pattern.md (Chinese Simplified) * New translations pattern_corridor_scan.md (Korean) * New translations pattern_corridor_scan.md (Turkish) * New translations pattern_corridor_scan.md (Chinese Simplified) * New translations pattern_structure_scan_v2.md (Turkish) * New translations pattern_survey.md (Korean) * New translations pattern_survey.md (Turkish) * New translations pattern_survey.md (Chinese Simplified) * New translations plan_rally_points.md (Turkish) * New translations plan_view.md (Korean) * New translations plan_view.md (Turkish) * New translations plan_view.md (Chinese Simplified) * New translations release_notes.md (Korean) * New translations release_notes.md (Turkish) * New translations release_notes.md (Chinese Simplified) * New translations stable_v3.2_long.md (Korean) * New translations stable_v3.2_long.md (Turkish) * New translations stable_v3.2_long.md (Chinese Simplified) * New translations stable_v3.3_long.md (Korean) * New translations stable_v3.3_long.md (Turkish) * New translations stable_v3.3_long.md (Chinese Simplified) * New translations console_logging.md (Turkish) * New translations console_logging.md (Chinese Simplified) * New translations general.md (Korean) * New translations general.md (Turkish) * New translations general.md (Chinese Simplified) * New translations mavlink.md (Korean) * New translations mavlink.md (Turkish) * New translations mavlink.md (Chinese Simplified) * New translations firmware.md (Turkish) * New translations joystick.md (Korean) * New translations joystick.md (Turkish) * New translations joystick.md (Chinese Simplified) * New translations motors.md (Turkish) * New translations motors_ardusub.md (Turkish) * New translations parameters.md (Turkish) * New translations radio.md (Turkish) * New translations safety_ardupilot.md (Korean) * New translations safety_ardupilot.md (Turkish) * New translations safety_ardupilot.md (Chinese Simplified) * New translations sensors_ardupilot.md (Korean) * New translations sensors_ardupilot.md (Turkish) * New translations sensors_ardupilot.md (Chinese Simplified) * New translations sensors_px4.md (Korean) * New translations sensors_px4.md (Turkish) * New translations sensors_px4.md (Chinese Simplified) * New translations support.md (Korean) * New translations support.md (Turkish) * New translations support.md (Chinese Simplified) * New translations toolbar.md (Turkish) * New translations qgc_setup.md (Korean) * New translations qgc_setup.md (Turkish) * New translations qgc_setup.md (Chinese Simplified) * New translations resume_mission.md (Korean) * New translations resume_mission.md (Turkish) * New translations resume_mission.md (Chinese Simplified)
This commit is contained in:
PX4 Build Bot
@@ -24,4 +24,4 @@ Note: There is also a UAS object associated with each Vehicle which is a depreca
|
||||
|
||||
The FirmwarePlugin class is the base class for firmware plugins. A firmware plugin contains the firmware specific code, such that the Vehicle object is clean with respect to it supporting a single standard interface to the UI.
|
||||
|
||||
FirmwarePluginManager is a factory class which creates a FirmwarePlugin instance based on the MAV\_AUTOPILOT/MAV\_TYPE combination for the Vehicle.
|
||||
FirmwarePluginManager is a factory class which creates a FirmwarePlugin instance based on the MAV_AUTOPILOT/MAV_TYPE combination for the Vehicle.
|
||||
|
||||
@@ -32,12 +32,12 @@ 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). |
|
||||
| `--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. |
|
||||
| `--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. |
|
||||
|
||||
|
||||
@@ -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_.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Release Process for Custom Builds \[WIP Docs]
|
||||
# Release Process for Custom Builds [WIP Docs]
|
||||
|
||||
One of the trickier aspects of creating your own custom build is the process to keep it up to date with regular QGC. This document describes a suggested process to follow. But in reality you are welcome to use whatever branching and release strategy you want for your custom builds.
|
||||
|
||||
|
||||
@@ -28,12 +28,12 @@ The plan fence and rally points are also used in modes when no mission is runnin
|
||||
|
||||
The main fields are:
|
||||
|
||||
| Key | Description |
|
||||
| ------------------------------ | ------------------------------------------------------------------------------ |
|
||||
| `version` | The version for this file. Current version is 1. |
|
||||
| `fileType` | Must be `"Plan"`. |
|
||||
| Key | Description |
|
||||
| ------------------------------ | ------------------------------------------------------------------------------------------------- |
|
||||
| `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. |
|
||||
| [`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 |
|
||||
|
||||
@@ -82,22 +82,22 @@ 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.
|
||||
|
||||
### `SimpleItem` - Simple Mission Item {#mission\_simple\_item}
|
||||
### `SimpleItem` - Simple Mission Item {#mission_simple_item}
|
||||
|
||||
A simple item represents a single MAVLink [MISSION\_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM) command.
|
||||
A simple item represents a single MAVLink [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM) command.
|
||||
|
||||
```
|
||||
{
|
||||
@@ -123,19 +123,19 @@ A simple item represents a single MAVLink [MISSION\_ITEM](https://mavlink.io/en/
|
||||
|
||||
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 |
|
||||
| `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) |
|
||||
| `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)). |
|
||||
| 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) |
|
||||
| `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}
|
||||
### Complex Mission Item {#mission_complex_item}
|
||||
|
||||
A complex item is a higher level encapsulation of multiple `MISSION_ITEM` objects treated as a single entity.
|
||||
|
||||
@@ -179,15 +179,15 @@ Complex items have these values associated with them:
|
||||
| Key | Description |
|
||||
| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `version` | The version number for this `survey` definition. Current version is 3. |
|
||||
| `type` | `ComplexItem` (this is a complex item). |
|
||||
| `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). |
|
||||
| `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. |
|
||||
|
||||
#### Corridor Scan {#corridor\_scan}
|
||||
#### Corridor Scan {#corridor_scan}
|
||||
|
||||
The object definition for a `CorridorScan` complex mission item is given below.
|
||||
|
||||
@@ -219,14 +219,14 @@ The object definition for a `CorridorScan` complex mission item is given below.
|
||||
| Key | Description |
|
||||
| ------------------------------------------------------- | --------------------------------------------------------------------- |
|
||||
| `version` | The version for this `CorridorScan` definition. Current version is 3. |
|
||||
| `type` | `ComplexItem` (this is a complex item). |
|
||||
| `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}
|
||||
#### Structure Scan {#structure_scan}
|
||||
|
||||
The object definition for a `StructureScan` complex mission item is given below.
|
||||
|
||||
@@ -264,7 +264,7 @@ 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). |
|
||||
| `type` | `ComplexItem` (this is a complex item). |
|
||||
| `complexItemType` | `StructureScan` |
|
||||
| `Altitude` | ? |
|
||||
| [`CameraCalc`](#CameraCalc) | ? |
|
||||
@@ -309,11 +309,11 @@ The object definition for a `StructureScan` complex mission item is given below.
|
||||
| --------------------------- | --------------------------------------------------------------------------------- |
|
||||
| `version` | The version for this `TransectStyleComplexItem` definition. Current version is 1. |
|
||||
| [`CameraCalc`](#CameraCalc) | ? |
|
||||
| `CameraTriggerInTurnAround` | ? (boolean) |
|
||||
| `FollowTerrain` | ? (boolean) |
|
||||
| `HoverAndCapture` | ? (boolean) |
|
||||
| `CameraTriggerInTurnAround` | ? (boolean) |
|
||||
| `FollowTerrain` | ? (boolean) |
|
||||
| `HoverAndCapture` | ? (boolean) |
|
||||
| `Items` | ? |
|
||||
| `Refly90Degrees` | ? (boolean) |
|
||||
| `Refly90Degrees` | ? (boolean) |
|
||||
| `TurnAroundDistance` | The distance to fly past the polygon edge prior to turning for the next transect. |
|
||||
| `VisualTransectPoints` | ? |
|
||||
|
||||
@@ -344,25 +344,25 @@ 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 |
|
||||
| `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. |
|
||||
| `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) |
|
||||
|
||||
## GeoFence {#geofence}
|
||||
@@ -384,13 +384,13 @@ 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}
|
||||
### Circle Geofence {#circle_geofence}
|
||||
|
||||
Each circular geofence is defined in a separate item, as shown below (multiple comma-separated items can be defined).
|
||||
The items define the centre and radius of the circle, and whether or not the specific geofence is activated.
|
||||
@@ -408,13 +408,13 @@ The items define the centre and radius of the circle, and whether or not the spe
|
||||
|
||||
The fields are:
|
||||
|
||||
| Key | Description |
|
||||
| ----------- | -------------------------------------------------------------------------------------------------- |
|
||||
| `version` | The version number for the geofence "circle" plan format. The documented version is 1. |
|
||||
| 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. |
|
||||
|
||||
### Polygon Geofence {#polygon\_geofence}
|
||||
### Polygon Geofence {#polygon_geofence}
|
||||
|
||||
Each polygon geofence is defined in a separate item, as shown below (multiple comma-separated items can be defined).
|
||||
The geofence includes a set of points defined with a clockwise winding (i.e. they must enclose an area).
|
||||
@@ -453,9 +453,9 @@ The fields are:
|
||||
| ----------- | ------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| `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}
|
||||
## Rally Points {#rally_points}
|
||||
|
||||
Rally point information is optional.
|
||||
The plan can contain an arbitrary number of rally points, each of which has a latitude, longitude, and altitude (above home position).
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
qt_version: 5.15.2
|
||||
qt_version: 6.6.1
|
||||
---
|
||||
|
||||
# Getting Started with Source and Builds
|
||||
@@ -46,30 +46,96 @@ We support Linux builds using a container found on the source tree of the reposi
|
||||
|
||||
### Native Builds
|
||||
|
||||
_QGroundControl_ builds are supported for macOS, Linux, Windows, iOS and Android.
|
||||
_QGroundControl_ uses [Qt](http://www.qt.io) as its cross-platform support library and uses [QtCreator](http://doc.qt.io/qtcreator/index.html) as its default build environment.
|
||||
_QGroundControl_ builds are supported for macOS, Linux, Windows, and Android. Creating a version of QGC for iOS is theoretically possible but is no longer supported as a standard build.
|
||||
_QGroundControl_ uses [Qt](http://www.qt.io) as its cross-platform support library.
|
||||
|
||||
- **macOS:** v10.11 or higher
|
||||
- **Ubuntu:** 64 bit, gcc compiler
|
||||
- **Windows:** Vista or higher, [Visual Studio 2019 compiler](#vs) (64 bit)
|
||||
- **iOS:** 10.0 and higher
|
||||
- **Android:** Android 5.0 and later.
|
||||
- Standard QGC is built against ndk version 19.
|
||||
- Java JDK 11 is required.
|
||||
- **Qt version:** {{ $frontmatter.qt\_version }} **(only)** <!-- NOTE {{ $frontmatter.qt_version }} is set in the frontmatter above -->
|
||||
The required version of Qt is {{ $frontmatter.qt_version }} **(only)**.
|
||||
|
||||
::: warning
|
||||
**Do not use any other version of Qt!**
|
||||
QGC has been thoroughly tested with the specified version of Qt ({{ $frontmatter.qt\_version }}).
|
||||
There is a significant risk that other Qt versions will inject bugs that affect stability and safety (even if QGC compiles).
|
||||
:::
|
||||
::: warning
|
||||
**Do not use any other version of Qt!**
|
||||
QGC has been thoroughly tested with the specified version of Qt ({{ $frontmatter.qt_version }}).
|
||||
There is a significant risk that other Qt versions will inject bugs that affect stability and safety (even if QGC compiles).
|
||||
:::
|
||||
|
||||
For more information see: [Qt 5 supported platform list](http://doc.qt.io/qt-5/supported-platforms.html).
|
||||
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.
|
||||
|
||||
To install Qt:
|
||||
|
||||
1. Download and run the [Qt Online Installer](http://www.qt.io/download-open-source)
|
||||
- **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`
|
||||
- **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
|
||||
|
||||
::: 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).
|
||||
|
||||
#### 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:
|
||||
|
||||
- **OSX:** Desktop Qt {{ $frontmatter.qt_version }} clang 64 bit
|
||||
|
||||
::: info
|
||||
iOS builds must be built using [XCode](http://doc.qt.io/qt-5/ios-support.html).
|
||||
:::
|
||||
|
||||
- **Ubuntu:** Desktop Qt {{ $frontmatter.qt_version }} GCC 64bit
|
||||
|
||||
- **Windows:** Desktop Qt {{ $frontmatter.qt_version }} MSVC2019 **64bit**
|
||||
|
||||
- **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_**.
|
||||
|
||||
3. Build using the "hammer" (or "play") icons:
|
||||
|
||||
|
||||
|
||||
#### 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)
|
||||
@@ -82,94 +148,6 @@ When installing, select _Desktop development with C++_ as shown:
|
||||
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.
|
||||
:::
|
||||
|
||||
#### Install Qt
|
||||
|
||||
You **need to install Qt as described below** instead of using pre-built packages from say, a Linux distribution, because _QGroundControl_ needs access to private Qt headers.
|
||||
|
||||
To install Qt:
|
||||
|
||||
1. Download and run the [Qt Online Installer](http://www.qt.io/download-open-source)
|
||||
- **Ubuntu:**
|
||||
- Set the downloaded file to executable using: `chmod +x`.
|
||||
- Install to default location for use with **./qgroundcontrol-start.sh.** If you install Qt to a non-default location you will need to modify **qgroundcontrol-start.sh** in order to run downloaded builds.
|
||||
|
||||
2. In the installer _Select Components_ dialog choose: {{ $frontmatter.qt\_version }}.
|
||||
|
||||
::: info
|
||||
If the version needed is not displayed, check the archive (show archive and refresh).
|
||||
:::
|
||||
|
||||
Then install just the following components:
|
||||
|
||||
- **Windows**: _MSVC 2019 64 bit_
|
||||
- **MacOS**: _macOS_
|
||||
- **Linux**: _Desktop gcc 64-bit_
|
||||
- All:
|
||||
- _Qt Charts_ <!-- and *Qt Remote Objects (TP)* -->
|
||||
- _Android ARMv7_ (optional, used to build Android)
|
||||
|
||||
|
||||
|
||||
3. Install Additional Packages (Platform Specific)
|
||||
|
||||
- **Ubuntu:** `sudo apt-get install speech-dispatcher libudev-dev libsdl2-dev patchelf build-essential curl`
|
||||
- **Fedora:** `sudo dnf install speech-dispatcher SDL2-devel SDL2 systemd-devel patchelf`
|
||||
- **Arch Linux:** `pacman -Sy speech-dispatcher patchelf`
|
||||
- **Android:** [Qt Android Setup](http://doc.qt.io/qt-5/androidgs.html)
|
||||
|
||||
::: info
|
||||
JDK11 is required (install if needed)!
|
||||
:::
|
||||
|
||||
4. 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).
|
||||
- **Airmap SDK:** - TBD.
|
||||
|
||||
5. Disable platform-specific optional features that are enabled (but not installed), by default.
|
||||
|
||||
::: info
|
||||
This currently applies to Airmap on Linux, which is optional but enabled by default.
|
||||
:::
|
||||
|
||||
- **Ubuntu:**
|
||||
|
||||
- Airmap: Create a file named **user\_config.pri** (in the repo root directory) containing the text `DEFINES += DISABLE_AIRMAP`.
|
||||
This can be done in a bash terminal using the command:
|
||||
|
||||
```sh
|
||||
echo -e "DEFINES += DISABLE_AIRMAP\r\n" | tee user_config.pri
|
||||
```
|
||||
|
||||
#### 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:
|
||||
|
||||
- **OSX:** Desktop Qt {{ $frontmatter.qt\_version }} clang 64 bit
|
||||
|
||||
::: info
|
||||
iOS builds must be built using [XCode](http://doc.qt.io/qt-5/ios-support.html).
|
||||
:::
|
||||
|
||||
- **Ubuntu:** Desktop Qt {{ $frontmatter.qt\_version }} GCC 64bit
|
||||
|
||||
- **Windows:** Desktop Qt {{ $frontmatter.qt\_version }} MSVC2019 **64bit**
|
||||
|
||||
- **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_**.
|
||||
|
||||
3. Build using the "hammer" (or "play") icons:
|
||||
|
||||
|
||||
|
||||
#### Build using qmake on CLI {#qmake}
|
||||
|
||||
Example commands to build a default QGC and run it afterwards:
|
||||
@@ -227,7 +205,6 @@ Example commands to build a default QGC and run it afterwards:
|
||||
### Additional Build Notes for all Supported OS
|
||||
|
||||
- **Parallel builds:** For non Windows builds, you can use the `-j#` option to run parellel builds.
|
||||
- **Location of built files:** Individual build file results can be found in the `build_debug` or `build_release` directories. The built executable can be found in the `debug` or `release` directory.
|
||||
- **If you get this error when running _QGroundControl_**: `/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version 'GLIBCXX_3.4.20' not found.`, you need to either update to the latest _gcc_, or install the latest _libstdc++.6_ using: `sudo apt-get install libstdc++6`.
|
||||
- **Unit tests:** To run the [unit tests](../contribute/unit_tests.md), build in `debug` mode with `UNITTEST_BUILD` definition, and then copy `deploy/qgroundcontrol-start.sh` script into the `debug` directory before running the tests.
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ The current stable build is the highest quality build available for QGC.
|
||||
Stable builds are built from a separate branch that is named with the format: `Stable_VX.Y` (note, there is no patch number!)
|
||||
The branch has one or more git tags for each patch release (with the format `vX.Y.Z`), indicating the point in the repo source code that the associated patch release was created from.
|
||||
|
||||
### Patch Releases {#patch\_releases}
|
||||
### Patch Releases {#patch_releases}
|
||||
|
||||
A patch release contains fixes to the stable release that are important enough to _require_ an update, and are safe enough that the stable release continues to maintain high quality.
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# 로그 다운로드(분석 화면)
|
||||
|
||||
_로그 다운로드_ 화면(**분석 > 로그 다운로드**)은 _새로고침_, _다운로드_ 및 \_ 전체 삭제 \_ 기능을 제공합니다.
|
||||
_로그 다운로드_ 화면(**분석 > 로그 다운로드**)은 _새로고침_, _다운로드_ 및 _ 전체 삭제 _ 기능을 제공합니다.
|
||||
|
||||
|
||||
|
||||
@@ -49,7 +49,7 @@
|
||||
기본적으로 표시되지 않거나 특정 조건에서만 표시되는 다른 요소들 많습니다.
|
||||
예를 들어, 다중 기체 선택기는 여러 대의 기체가 연결된 경우에만 표시되며, 비행 전 체크리스트 도구 버튼은 적절한 설정이 활성화된 경우에만 표시됩니다.
|
||||
|
||||
## 계기판 {#instrument\_panel}
|
||||
## 계기판 {#instrument_panel}
|
||||
|
||||
The instrument panel displays telemetry information about the current vehicle.
|
||||
|
||||
@@ -81,7 +81,7 @@ The selection list on the top right is used to select a particular telemetry val
|
||||
|
||||
비행 중인 기체의 시동을 꺼려면 _비행 도구 모음_에서 **시동**을 선택합니다.
|
||||
|
||||
### 카메라 {#camera\_instrument\_page}
|
||||
### 카메라 {#camera_instrument_page}
|
||||
|
||||
The camera panel is used to capture still images and video, and to configure the camera.
|
||||
|
||||
@@ -103,7 +103,7 @@ Most of the settings that are displayed depend on the camera (they are defined i
|
||||
|
||||
> 마지막에 몇 가지 일반적인 설정이 하드 코딩되어 있습니다: 사진 모드(단일/인터벌), 사진 간격(인터벌인 경우), 카메라 기본값 재설정(카메라에 재설정 명령 전송), 포맷(저장)
|
||||
|
||||
### 비디오 스트림 {#video\_instrument\_page}
|
||||
### 비디오 스트림 {#video_instrument_page}
|
||||
|
||||
비디오 페이지는 비디오 스트리밍을 활성화 하거나 비활성화 합니다.
|
||||
활성화시에는 비디오 스트림을 시작하고, 그리드 오버레이를 활성화하고, 이미지가 화면에 맞는 방식을 변경하고, QGroundControl을 사용하여 로컬로 비디오를 녹화할 수 있습니다.
|
||||
@@ -118,7 +118,7 @@ Most of the settings that are displayed depend on the camera (they are defined i
|
||||
Many of the available options depend on both the vehicle type and its current state.
|
||||
:::
|
||||
|
||||
### 비행 전 점검 사항 {#preflight\_checklist}
|
||||
### 비행 전 점검 사항 {#preflight_checklist}
|
||||
|
||||
자동 비행 전 점검을 통하여 기체의 설정과 비행 안전 여부를 검사합니다.
|
||||
|
||||
@@ -185,7 +185,7 @@ You will then need to use the disarming slider.
|
||||
|
||||
비행 중 기체의 시동을 꺼는 것을 [비상 정지](#emergency_stop)라고 합니다.
|
||||
|
||||
### 비상 정지 {#emergency\_stop}
|
||||
### 비상 정지 {#emergency_stop}
|
||||
|
||||
비상 정지는 비행 중 기체의 시동을 꺼는 것과 동일합니다.
|
||||
Your vehicle will crash!
|
||||
@@ -236,7 +236,7 @@ You will then need to use the emergency disarming slider.
|
||||
예를 들어, 집결지나 임무 착륙을 대체 반환 목표로 사용할 수 있습니다.
|
||||
:::
|
||||
|
||||
### 고도 변경 {#change\_altitude}
|
||||
### 고도 변경 {#change_altitude}
|
||||
|
||||
미션 수행중을 제외하고는, 비행 중 고도 변경이 가능합니다.
|
||||
|
||||
@@ -304,7 +304,7 @@ _위치 이동_ 작업은 일시 중지가 불가능 합니다.
|
||||
|
||||
### 미션
|
||||
|
||||
#### 미션 시작 {#start\_mission}
|
||||
#### 미션 시작 {#start_mission}
|
||||
|
||||
기체는 착륙후 미션를 시작할 수 있습니다(미션 시작 확인 슬라이더는 대부분 기본적으로 표시됩니다).
|
||||
|
||||
@@ -322,7 +322,7 @@ _위치 이동_ 작업은 일시 중지가 불가능 합니다.
|
||||
|
||||
|
||||
|
||||
#### 미션 지속 {#continue\_mission}
|
||||
#### 미션 지속 {#continue_mission}
|
||||
|
||||
비행 중일 때 _다음_ 웨이포인트에서 미션을 _지속_할 수 있습니다(이륙 후에 _미션 지속_ 확인 슬라이더가 기본적으로 표시되는 경우가 많습니다).
|
||||
|
||||
@@ -344,7 +344,7 @@ _위치 이동_ 작업은 일시 중지가 불가능 합니다.
|
||||
|
||||
|
||||
|
||||
#### 임무 재개 {#resume\_mission}
|
||||
#### 임무 재개 {#resume_mission}
|
||||
|
||||
_임무 재개_는 임무 수행중 [착륙지 복귀/복귀](#rtl)나 [착륙](#land)을 수행 후 임무를 재개합니다 (예를 들어 배터리 교체).
|
||||
|
||||
@@ -369,12 +369,12 @@ _임무 재개_는 임무 수행중 [착륙지 복귀/복귀](#rtl)나 [착륙](
|
||||
대신 _QGroundControl_은 비행한 마지막 임무 항목부터 시작하여 임무를 재구성하고 자동으로 임무 앞에 관련 명령을 추가합니다.
|
||||
:::
|
||||
|
||||
#### 착륙 후 임무 프롬프트 제거 {#resume\_mission\_prompt}
|
||||
#### 착륙 후 임무 프롬프트 제거 {#resume_mission_prompt}
|
||||
|
||||
임무가 완료후 기체가 착륙한 다음 시동이 해제되면 기체의 임무를 제거하라는 메시지가 표시됩니다.
|
||||
이는 이전의 임무가 의도치 않게 기체에 저장되어, 예기치 않은 동작을 초래하는 문제를 방지합니다.
|
||||
|
||||
### 비디오 출력 {#video\_switcher}
|
||||
### 비디오 출력 {#video_switcher}
|
||||
|
||||
비디오 스트리밍이 활성화되면, _QGroundControl_은 지도 왼쪽 하단의 "비디오 전환기 창"에 현재 선택된 기체의 비디오 스트림을 표시합니다.
|
||||
아무 곳이나 스위처를 눌러 _동영상_ 및 _지도_를 전경으로 전환할 수 있습니다(아래 이미지에서 동영상은 전경에 표시됨).
|
||||
|
||||
@@ -36,7 +36,7 @@ _QGroundControl_ 4.0 버전 이상의 사전 빌드 버전은 64비트 전용입
|
||||
|
||||
_QGroundControl_은 MacOS 10.11 이상에서 설치할 수 있습니다.
|
||||
|
||||
<!-- match version using https://dev.qgroundcontrol.com/master/en/getting_started/#native-builds -->
|
||||
<!-- match version using https://docs.qgroundcontrol.com/master/en/qgc-dev-guide/getting_started/#native-builds -->
|
||||
|
||||
<!-- usually based on Qt macOS dependency -->
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ QGroundControl에 자주 사용하는 것이 익숙해 질 수 있는 최선의
|
||||
- [설정](../setup_view/setup_view.md): 기체를 설정하고 튜닝합니다.
|
||||
- [계획](../plan_view/plan_view.md): 자율 비행 미션을 생성합니다.
|
||||
- [비행](../fly_view/fly_view.md): 스트리밍 비디오를 포함하여 비행중 기체를 모니터링합니다.
|
||||
- \[분석] \*\* 분석 보기에 대한 설명이 누락되었습니다 \*\*
|
||||
- [분석] \*\* 분석 보기에 대한 설명이 누락되었습니다 \*\*
|
||||
- 툴바에서 _상태 아이콘_을 클릭하여 연결된 기체의 상태를 확인할 수 있습니다.
|
||||
|
||||
While the UI is fairly intuitive, this documentation can also be referenced to find out more.
|
||||
|
||||
@@ -5,9 +5,9 @@ The available pattern tools depend on the vehicle (and support for the vehicle-t
|
||||
|
||||
|
||||
|
||||
| 패턴 | 설명 | 차량 |
|
||||
| ---------------------------------------------------- | --------------------------------------------------------------------------------- | ---------- |
|
||||
| [탐사](../plan_view/pattern_survey.md) | 다각형 영역에 그리드 비행 패턴을 작성합니다. 지오태깅 이미지 생성에 적합한 그리드 및 카메라 설정에 대한 사양과 다각형을 지정할 수 있습니다. | 전체 |
|
||||
| 패턴 | 설명 | 차량 |
|
||||
| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | ---------- |
|
||||
| [탐사](../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 |
|
||||
|
||||
@@ -77,7 +77,7 @@ The corridor scan settings are covered in the next section.
|
||||
- **상대 고도** - 상대 고도를 지정하려면 선택합니다. 이것은 [지형 추적](#terrain_following)을 사용하지 않는 수동 그리드에만 지원됩니다.
|
||||
- **진입점 회전** - 버튼을 클릭하여 복도 스캔의 시작점과 끝점을 변경합니다.
|
||||
|
||||
### 지형 추적 {#terrain\_following}
|
||||
### 지형 추적 {#terrain_following}
|
||||
|
||||
기본적으로 기체는 고정 고도에서 복도 경로를 따라 비행합니다.
|
||||
Enabling _Terrain Following_ makes the vehicle maintain a constant height relative to ground.
|
||||
|
||||
@@ -46,7 +46,7 @@ The survey settings are covered in the next section.
|
||||
|
||||
|
||||
|
||||
#### 알려진 카메라 {#known\_camera}
|
||||
#### 알려진 카메라 {#known_camera}
|
||||
|
||||
드롭다운 옵션에서 알려진 카메라를 선택하면 카메라 기능을 기반으로 격자 패턴이 생성됩니다.
|
||||
|
||||
@@ -61,7 +61,7 @@ The survey settings are covered in the next section.
|
||||
- **고도** - 조사 고도(지상 해상도가 이 고도에 대해 계산/표시됨).
|
||||
- **지상 해상도** - 각 이미지의 지상 해상도(해상도를 계산하고 표시하는 데 필요한 고도).
|
||||
|
||||
#### 카메라 최적화 {#custom\_camera}
|
||||
#### 카메라 최적화 {#custom_camera}
|
||||
|
||||
사용자 정의 카메라 옵션을 선택하면 알려진 카메라와 유사한 방식으로 새 카메라에 대한 설정을 지정할 수 있습니다.
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ _계획 뷰_에서는 차량에 대한 _자율 임무_를 계획하고 차량에
|
||||
<span id="plan_screenshot"></span>
|
||||
|
||||
|
||||
## UI 개요 {#ui\_overview}
|
||||
## UI 개요 {#ui_overview}
|
||||
|
||||
[위의 스크린샷](#plan_screenshot)은 [Planned Home](#planned_home) 위치(H)에서 이륙으로 시작하는 간단한 임무 계획을 보여줍니다.
|
||||
|
||||
@@ -24,7 +24,7 @@ UI의 주요 요소는 다음과 같습니다.
|
||||
|
||||
현재 선택된 웨이포인트와 관련된 정보와 전체 미션에 대한 통계를 보여줍니다.
|
||||
|
||||
## 임무 계획 {#plan\_mission}
|
||||
## 임무 계획 {#plan_mission}
|
||||
|
||||
매우 높은 수준에서 임무를 생성하는 단계는 다음과 같습니다.
|
||||
|
||||
@@ -35,7 +35,7 @@ UI의 주요 요소는 다음과 같습니다.
|
||||
|
||||
다음 섹션에서는 보기의 일부 세부 정보에 대해 설명합니다.
|
||||
|
||||
## 지정된 홈 위치 {#planned\_home}
|
||||
## 지정된 홈 위치 {#planned_home}
|
||||
|
||||
_계획 뷰_에 표시된 _계획된 홈_은 임무 계획시 대략적인 시작 지점을 설정합니다(예: 차량이 QGC에 연결되지 않은 경우).
|
||||
QGC에서 임무 시간을 추정하고 웨이포인트 라인을 그립니다.
|
||||
@@ -51,7 +51,7 @@ QGC에서 임무 시간을 추정하고 웨이포인트 라인을 그립니다.
|
||||
비행 뷰는 시동시에 차량 펌웨어에 의해 설정된 _실제_ 홈 위치를 표시합니다(차량이 리턴/RTL 모드에서 복귀하는 위치).
|
||||
:::
|
||||
|
||||
## 계획 도구 {#plan\_tools}
|
||||
## 계획 도구 {#plan_tools}
|
||||
|
||||
계획 도구는 개별 웨이포인트 추가, 복잡한 형상에 대한 쉬운 임무 생성, 임무 업로드/다운로드/저장/복원 및 지도를 탐색합니다. 주요 도구는 아래와 같습니다.
|
||||
|
||||
@@ -86,7 +86,7 @@ _파일 도구_는 다음과 같은 기능을 제공합니다.
|
||||
|
||||
[패턴](Pattern.md) 도구는 [설문조사](../plan_view/pattern_survey.md) 및 [구조 스캔](../plan_view/pattern_structure_scan_v2.md)을 포함하여 복잡한 형상을 비행하기 위한 임무 생성을 단순화합니다.
|
||||
|
||||
## 임무 명령 목록 {#mission\_command\_list}
|
||||
## 임무 명령 목록 {#mission_command_list}
|
||||
|
||||
현재 임무에 대한 임무 명령은 보기의 오른쪽에 나열됩니다.
|
||||
상단에는 임무 편집, GeoFence 및 집회 지점 간을 전환하는 옵션 세트가 있습니다.
|
||||
@@ -94,7 +94,7 @@ _파일 도구_는 다음과 같은 기능을 제공합니다.
|
||||
|
||||
|
||||
|
||||
### 임무 명령 편집자 {#mission\_command\_editors}
|
||||
### 임무 명령 편집자 {#mission_command_editors}
|
||||
|
||||
목록에서 임무 명령을 클릭하면 편집기가 표시됩니다(여기에서 명령 속성을 설정/변경할 수 있음).
|
||||
|
||||
@@ -111,7 +111,7 @@ _파일 도구_는 다음과 같은 기능을 제공합니다.
|
||||
예로는 경유지, 이미지 캡처 시작, 항목으로 이동(임무 반복) 및 기타 명령이 포함될 수 있습니다.
|
||||
:::
|
||||
|
||||
### 임무 설정 {#mission\_settings}
|
||||
### 임무 설정 {#mission_settings}
|
||||
|
||||
_임무 시작_ 패널은 [임무 명령 목록](#mission_command_list)에 나타나는 첫 번째 항목입니다.
|
||||
임무 시작 또는 종료에 영향을 줄 수 있는 기본 설정 번호를 지정하는 데 사용할 수 있습니다.
|
||||
@@ -181,7 +181,7 @@ _차량에 연결_한 상태에서 임무를 계획하고 있다면 차량에
|
||||
|
||||
## 문제 해결
|
||||
|
||||
### 미션(계획) 업로드/다운로드 실패 {#plan\_transfer\_fail}
|
||||
### 미션(계획) 업로드/다운로드 실패 {#plan_transfer_fail}
|
||||
|
||||
계획 업로드 및 다운로드는 통신 장애로 인하여 실패할 수 있습니다(미션, GeoFence 및 집회 지점에 영향을 미침).
|
||||
오류가 발생하면 QGC UI에 다음과 유사한 상태 메시지가 표시되어야 합니다.
|
||||
|
||||
@@ -80,7 +80,7 @@ QGroundControl의 설정 형식은 이번 배포판에서 변경되었습니다.
|
||||
카메라 선택, 카메라 모드, 사진/동영상 시작/중지, 스토리지 관리 등등
|
||||
- **궤도** 회전 방향 변경 지원.
|
||||
- **계기판**
|
||||
- 새로운 estimatorStatus Vehicle FactGroup에 ESTIMATOR\_STATUS 값을 추가하였습니다.
|
||||
- 새로운 estimatorStatus Vehicle FactGroup에 ESTIMATOR_STATUS 값을 추가하였습니다.
|
||||
이제 계기판에 표시할 수 있습니다.
|
||||
- 계기판에서 표시할 수 있도록 GCS까지의 거리를 설정합니다.
|
||||
- Make Heading to Home available for display from instrument panel.
|
||||
@@ -136,7 +136,7 @@ QGroundControl의 설정 형식은 이번 배포판에서 변경되었습니다.
|
||||
- **ArduPlane** QuadPlane 지원을 포함하여 안내 명령에 대한 지원이 향상되었습니다.
|
||||
- **높은 대기 시간 링크** 위성 연결과 같은 대기 시간이 긴 링크를 지원합니다.
|
||||
비용을 줄이기 위하여 이러한 링크에서 QGroundControl에서 기체 트래픽을 제한합니다.
|
||||
HIGH\_LATENCY MavLink 메시지를 지원합니다.
|
||||
HIGH_LATENCY MavLink 메시지를 지원합니다.
|
||||
듀얼 링크 설정으로, 높은 대기 시간에서 일반 링크로의 장애 복구를 지원합니다.
|
||||
|
||||
## 안정 버전 3.3
|
||||
|
||||
@@ -41,7 +41,7 @@ _비행 후 텔레메트리 로그 저장_을 켠 경우 더 이상 차량이
|
||||
|
||||
이제 라디오 설정 페이지의 트림 복사 버튼에서 지원됩니다.
|
||||
|
||||
## 계획 화면 {#plan\_view}
|
||||
## 계획 화면 {#plan_view}
|
||||
|
||||
### 계획 파일
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ GPS 정보는 지상국 위치 측정에 사용됩니다.
|
||||
|
||||
자세한 내용은 [설정 > 일반(동영상/동영상 녹화)](../settings_view/general.md#video)을 참고하십시오.
|
||||
|
||||
### 계획 화면 {#plan\_view}
|
||||
### 계획 화면 {#plan_view}
|
||||
|
||||
#### 구조 스캔
|
||||
|
||||
|
||||
@@ -64,7 +64,7 @@ Values are settable even if no vehicle is connected. 차량 재시동이 필요
|
||||
|
||||
- <span id="load_save_path"></span>**애플리케이션 로드/저장 경로**: 매개변수, 원격 측정 로그 및 임무 계획을 포함하여 애플리케이션 파일을 로드 및 저장하는 기본 위치입니다.
|
||||
|
||||
## 데이터 지속성 {#data\_persistence}
|
||||
## 데이터 지속성 {#data_persistence}
|
||||
|
||||
|
||||
|
||||
@@ -72,7 +72,7 @@ Values are settable even if no vehicle is connected. 차량 재시동이 필요
|
||||
|
||||
- **모든 데이터 지속성 사용 안함**: 로그, 지도 타일 등 데이터가 저장되거나 캐시되지 않도록 확인합니다.
|
||||
|
||||
## 기체의 텔레메트리 로그 {#telemetry\_logs}
|
||||
## 기체의 텔레메트리 로그 {#telemetry_logs}
|
||||
|
||||
|
||||
|
||||
@@ -83,7 +83,7 @@ Values are settable even if no vehicle is connected. 차량 재시동이 필요
|
||||
차량 연결이 끊어지면 기록을 중지합니다.
|
||||
- [**CSV 로깅**](csv.md): 원격 측정 데이터의 하위 집합을 CSV 파일에 기록합니다.
|
||||
|
||||
## 비행 화면 {#fly\_view}
|
||||
## 비행 화면 {#fly_view}
|
||||
|
||||
|
||||
|
||||
@@ -117,7 +117,7 @@ Values are settable even if no vehicle is connected. 차량 재시동이 필요
|
||||
|
||||
- **이동 위치 최대 거리**: 이동 위치가 현재 차량 위치에서 설정될 수 있는 최대 거리(안내 모드에서).
|
||||
|
||||
## 계획 화면 {#plan\_view}
|
||||
## 계획 화면 {#plan_view}
|
||||
|
||||
|
||||
|
||||
@@ -125,7 +125,7 @@ Values are settable even if no vehicle is connected. 차량 재시동이 필요
|
||||
|
||||
- **기본 임무 고도**: 임무 시작 패널 및 첫 번째 웨이포인트의 기본 고도입니다.
|
||||
|
||||
## 다음 장치에 자동으로 연결 {#auto\_connect}
|
||||
## 다음 장치에 자동으로 연결 {#auto_connect}
|
||||
|
||||
이 섹션은 _QGroundControl_이 자동으로 연결할 기기 세트를 정의합니다.
|
||||
|
||||
@@ -141,7 +141,7 @@ Values are settable even if no vehicle is connected. 차량 재시동이 필요
|
||||
- **RTK GPS:** RTK GPS 기기에 자동 연결
|
||||
- **NMEA GPS 장치:** 외부 GPS 장치에 자동 연결하여 지상국 위치를 획득합니다([아래 참조](#nmea_gps)).
|
||||
|
||||
### 지상국 위치(NMEA GPS 장치) {#nmea\_gps}
|
||||
### 지상국 위치(NMEA GPS 장치) {#nmea_gps}
|
||||
|
||||
_QGroundControl_은 자동으로 내부 GPS를 사용하여 자주색 `Q` 아이콘으로 지도에 자신의 위치를 표시합니다(GPS가 방향을 제공하는 경우 이는 아이콘으로도 표시됩니다.
|
||||
현재 [PX4 멀티콥터에서만](https://docs.px4.io/en/flight_modes/follow_me.html) 지원됩니다.
|
||||
@@ -173,7 +173,7 @@ _NMEA GPS 장치_ 드롭다운 선택기를 사용하여 GPS 장치 및 기타
|
||||
- **NMEA GPS 장치:** _UDP 포트_.
|
||||
- **NMEA 스트림 UDP 포트**: QGC가 NMEA 데이터를 수신할 UDP 포트(QGC는 포트를 서버로 바인딩)
|
||||
|
||||
## RTK GPS {#rtk\_gps}
|
||||
## RTK GPS {#rtk_gps}
|
||||
|
||||
이 섹션에서는 RTK GPS "측량" 설정을 지정하고, 측량 작업의 결과를 저장 및 재사용하거나, 베이스 스테이션에 대해 알려진 다른 위치를 직접 입력할 수 있습니다.
|
||||
|
||||
@@ -203,7 +203,7 @@ _설문조사_ 프로세스는 기지국 위치의 정확한 추정치를 얻기
|
||||
- **기지 위치 정확도:** 기지국 위치 정보의 정확도.
|
||||
- **현재 베이스 위치 저장**(버튼): 마지막 Survey-In 작업의 설정을 위의 _지정된 베이스 위치 사용_ 필드에 복사하려면 누릅니다.
|
||||
|
||||
## ADSB 서버 {#adsb\_server}
|
||||
## ADSB 서버 {#adsb_server}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ MAVLink 설정(**설정 화면> MAVLink**)에서 MAVLink 통신과 관련된 옵
|
||||
|
||||
|
||||
|
||||
## 지상국 {#ground\_station}
|
||||
## 지상국 {#ground_station}
|
||||
|
||||
이 섹션은 _QGroundControl_의 MAVLink 속성과 동작을 설정합니다.
|
||||
|
||||
@@ -23,7 +23,7 @@ MAVLink 설정(**설정 화면> MAVLink**)에서 MAVLink 통신과 관련된 옵
|
||||
Note that this forwarding is one-way: from QGC to the specified host.
|
||||
지정된 호스트에서 수신된 모든 MAVLink 메시지는 무시됩니다.
|
||||
|
||||
## 연결 상태 {#link\_status}
|
||||
## 연결 상태 {#link_status}
|
||||
|
||||
이것은 통신 링크를 통한 MAVLink 메시지 전송의 상태를 보여줍니다.
|
||||
**손실률**이 높으면 매개변수 다운로드 또는 미션 업로드 및 다운로드와 같은 프로토콜 오류가 발생할 수 있습니다.
|
||||
@@ -35,7 +35,7 @@ MAVLink 설정(**설정 화면> MAVLink**)에서 MAVLink 통신과 관련된 옵
|
||||
_MAVLink 2 Logging_ 설정(PX4만 해당)은 PX4에서 _QGroundControl_으로의 실시간 로그 스트리밍과 [Flight Review](https://logs.px4.io)로의 로그 업로드를 설정합니다.
|
||||
|
||||
:::warning
|
||||
MAVLink 2 Logging은 차량에 대한 지속적인 고속 MAVLink 연결이 필요하기 때문에 "기본" 설정에서 사용할 수 없습니다(WiFI를 통해 작동할 수 \_ 있지만\*\* 원격 측정 링크에서는 작동하지 않습니다\_.
|
||||
MAVLink 2 Logging은 차량에 대한 지속적인 고속 MAVLink 연결이 필요하기 때문에 "기본" 설정에서 사용할 수 없습니다(WiFI를 통해 작동할 수 _ 있지만\*\* 원격 측정 링크에서는 작동하지 않습니다_.
|
||||
:::
|
||||
|
||||
:::tip
|
||||
|
||||
@@ -18,7 +18,7 @@ _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)을 `1</0)로 설정합니다.
|
||||
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)을 `1</0)로 설정합니다.
|
||||
이 매개변수가 <code>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).
|
||||
@@ -62,12 +62,12 @@ ArduPilot 기체에서 지원됩니다. 매개변수 설정은 필요하지 않
|
||||
|
||||
|
||||
|
||||
- **조이스틱의 중앙을 스로틀 0으로 설정**: [MANUAL\_CONTROL **z**](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL)에서 중앙 또는 아래로 향한 스틱은 0을 전송하고, 위로 올린 스틱은 1000을 전송합니다.
|
||||
- **조이스틱의 중앙을 스로틀 0으로 설정**: [MANUAL_CONTROL **z**](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL)에서 중앙 또는 아래로 향한 스틱은 0을 전송하고, 위로 올린 스틱은 1000을 전송합니다.
|
||||
- **스프링 로드 스로틀 스무딩**: 이 모드에서는 스로틀 자체가 아니라 스로틀이 증감하는 속도를 제어합니다.
|
||||
이것은 사용자가 원하는 스로틀을 잡고 스틱을 놓을 수 있으므로, 스로틀 스틱에 스프링이 장착된 설정에 유용합니다.
|
||||
- **풀다운 스틱은 제로 스로틀**: 이 모드에서 스틱을 내리면 [MANUAL\_CONTROL **z**](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL)에서 0, 중앙에 500, 올리면 1000이 전송됩니다.
|
||||
- **풀다운 스틱은 제로 스로틀**: 이 모드에서 스틱을 내리면 [MANUAL_CONTROL **z**](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL)에서 0, 중앙에 500, 올리면 1000이 전송됩니다.
|
||||
- **음수 추력 허용**: **중앙 스틱이 0 스로틀** 모드에 있을 때 사용자가 스틱을 내려 음수 값을 전송할 수 있습니다.
|
||||
내려진 스틱은 [MANUAL\_CONTROL **z**](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL)에서 -1000을 전송하고, 중앙에 있는 스틱은 0을 전송하고, 올려진 스틱은 1000을 전송합니다.
|
||||
내려진 스틱은 [MANUAL_CONTROL **z**](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL)에서 -1000을 전송하고, 중앙에 있는 스틱은 0을 전송하고, 올려진 스틱은 1000을 전송합니다.
|
||||
이 모드는 [Rover](http://ardupilot.org/rover/index.html)와 같이 음의 추력을 지원하는 차량에만 사용할 수 있습니다.
|
||||
|
||||
### Expo
|
||||
@@ -95,11 +95,11 @@ ArduPilot 기체에서 지원됩니다. 매개변수 설정은 필요하지 않
|
||||
|
||||
- **조이스틱 모드**: 조이스틱이 실제로 제어하는 것과 차량에 전송되는 MAVLink 메시지를 변경합니다.
|
||||
|
||||
- **일반**: 일반 RC 라디오를 사용하는 것처럼 사용자가 제어하며, MAVLink [MANUAL\_CONTROL](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) 메시지를 사용합니다.
|
||||
- **자세**: 사용자가 차량의 자세를 제어하며 MAVLink [SET\_ATTITUDE\_TARGET](https://mavlink.io/en/messages/common.html#SET_ATTITUDE_TARGET) 메시지를 사용합니다.
|
||||
- MAVLink [SET\_POSITION\_TARGET\_LOCAL\_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) 메시지에는 **위치**에 대한 비트마스크만을 사용합니다.
|
||||
- MAVLink [SET\_POSITION\_TARGET\_LOCAL\_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) 메시지는 **force** 전용 비트마스크를 사용합니다.
|
||||
- **속도**: 사용자가 차량에 가해지는 힘을 제어하며, **속도**에 대한 비트마스크가 있는 MAVLink [SET\_POSITION\_TARGET\_LOCAL\_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) 메시지를 사용합니다.
|
||||
- **일반**: 일반 RC 라디오를 사용하는 것처럼 사용자가 제어하며, MAVLink [MANUAL_CONTROL](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) 메시지를 사용합니다.
|
||||
- **자세**: 사용자가 차량의 자세를 제어하며 MAVLink [SET_ATTITUDE_TARGET](https://mavlink.io/en/messages/common.html#SET_ATTITUDE_TARGET) 메시지를 사용합니다.
|
||||
- MAVLink [SET_POSITION_TARGET_LOCAL_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) 메시지에는 **위치**에 대한 비트마스크만을 사용합니다.
|
||||
- MAVLink [SET_POSITION_TARGET_LOCAL_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) 메시지는 **force** 전용 비트마스크를 사용합니다.
|
||||
- **속도**: 사용자가 차량에 가해지는 힘을 제어하며, **속도**에 대한 비트마스크가 있는 MAVLink [SET_POSITION_TARGET_LOCAL_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) 메시지를 사용합니다.
|
||||
|
||||
- **축 주파수**: 조이스틱이 유휴 상태일 때(입력이 변경되지 않음) 조이스틱 명령이 5Hz로 차량에 전송됩니다. 조이스틱이 사용 중일 때(입력 값이 변경됨) 조이스틱 명령은 이 설정에 의한 (더 높은) 주파수가 기체에 전송됩니다. 기본값은 25Hz입니다.
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ _QGroundControl_은 ArduPilot에서 폴리곤 펜스 또는 랠리 포인트를
|
||||
추가 안전 설정 및 정보는 [안전장치](http://ardupilot.org/copter/docs/failsafe-landing-page.html)를 참고하십시오.
|
||||
:::
|
||||
|
||||
### 배터리 안전장치 {#battery\_failsafe\_copter}
|
||||
### 배터리 안전장치 {#battery_failsafe_copter}
|
||||
|
||||
이 패널은 [배터리 안전장치](http://ardupilot.org/copter/docs/failsafe-battery.html) 매개변수를 설정합니다.
|
||||
전압 및 남은 용량에 대해 낮거나 중요한 임계값을 설정하고 안전 장치 값이 위반되는 경우 조치를 정의할 수 있습니다.
|
||||
@@ -34,14 +34,14 @@ _QGroundControl_은 ArduPilot에서 폴리곤 펜스 또는 랠리 포인트를
|
||||
|
||||
설정 옵션은 다음과 같습니다:
|
||||
|
||||
- **Low action**([BATT\_FS\_LOW\_ACT](http://ardupilot.org/copter/docs/parameters.html#batt-fs-low-act-low-battery-failsafe-action)) - 없음, Land, RTL, SmartRTL, SmartRTL 또는 Land, Terminate 중 하나를 선택합니다.
|
||||
- **Critical action**([BATT\_FS\_CRT\_ACT](http://ardupilot.org/copter/docs/parameters.html#batt-fs-crt-act-critical-battery-failsafe-action)) - 없음, Land, RTL, SmartRTL, SmartRTL 또는 Land, Terminate 중 하나를 선택합니다.
|
||||
- **Low voltage threshold**([BATT\_LOW\_VOLT](http://ardupilot.org/copter/docs/parameters.html#batt-low-volt-low-battery-voltage)) - _낮은 동작_을 트리거하는 배터리 전압입니다.
|
||||
- **Critical voltage threshold<**([BATT\_CRT\_VOLT](http://ardupilot.org/copter/docs/parameters.html#batt-crt-volt-critical-battery-voltage))- _중요 작업_을 트리거하는 배터리 전압입니다.
|
||||
- **Low mAh threshold**([BATT\_LOW\_MAH](http://ardupilot.org/copter/docs/parameters.html#batt-low-mah-low-battery-capacity)) - _낮은 작업_을 트리거하는 배터리 용량입니다.
|
||||
- **Critical mAh threshold**([BATT\_CRT\_MAH](http://ardupilot.org/copter/docs/parameters.html#batt-crt-mah-battery-critical-capacity)) - _중요한 작업_을 트리거하는 배터리 용량입니다.
|
||||
- **Low action**([BATT_FS_LOW_ACT](http://ardupilot.org/copter/docs/parameters.html#batt-fs-low-act-low-battery-failsafe-action)) - 없음, Land, RTL, SmartRTL, SmartRTL 또는 Land, Terminate 중 하나를 선택합니다.
|
||||
- **Critical action**([BATT_FS_CRT_ACT](http://ardupilot.org/copter/docs/parameters.html#batt-fs-crt-act-critical-battery-failsafe-action)) - 없음, Land, RTL, SmartRTL, SmartRTL 또는 Land, Terminate 중 하나를 선택합니다.
|
||||
- **Low voltage threshold**([BATT_LOW_VOLT](http://ardupilot.org/copter/docs/parameters.html#batt-low-volt-low-battery-voltage)) - _낮은 동작_을 트리거하는 배터리 전압입니다.
|
||||
- **Critical voltage threshold<**([BATT_CRT_VOLT](http://ardupilot.org/copter/docs/parameters.html#batt-crt-volt-critical-battery-voltage))- _중요 작업_을 트리거하는 배터리 전압입니다.
|
||||
- **Low mAh threshold**([BATT_LOW_MAH](http://ardupilot.org/copter/docs/parameters.html#batt-low-mah-low-battery-capacity)) - _낮은 작업_을 트리거하는 배터리 용량입니다.
|
||||
- **Critical mAh threshold**([BATT_CRT_MAH](http://ardupilot.org/copter/docs/parameters.html#batt-crt-mah-battery-critical-capacity)) - _중요한 작업_을 트리거하는 배터리 용량입니다.
|
||||
|
||||
### 일반적인 안전장치 트리거 {#failsafe\_triggers\_copter}
|
||||
### 일반적인 안전장치 트리거 {#failsafe_triggers_copter}
|
||||
|
||||
이 패널은 [GCS 안전장치](http://ardupilot.org/copter/docs/gcs-failsafe.html)를 활성화하고 스로틀 안전장치를 설정합니다.
|
||||
|
||||
@@ -51,9 +51,9 @@ _QGroundControl_은 ArduPilot에서 폴리곤 펜스 또는 랠리 포인트를
|
||||
|
||||
- **Ground Station failsafe** - 비활성화, 항상 RTL 활성화, 자동 모드에서 미션 계속 활성화, 항상 SmartRTL 또는 RTL 활성화, 항상 SmartRTL 또는 Land 활성화.
|
||||
- **Throttle failsafe** - 비활성화됨, 항상 RTL, 자동 모드에서 미션 계속, 항상 착륙.
|
||||
- **PWM Threshold**([FS\_THR\_VALUE](http://ardupilot.org/copter/docs/parameters.html#fs-thr-value-throttle-failsafe-value)) - 스로틀 페일세이프가 트리거되는 PWM 값입니다.
|
||||
- **PWM Threshold**([FS_THR_VALUE](http://ardupilot.org/copter/docs/parameters.html#fs-thr-value-throttle-failsafe-value)) - 스로틀 페일세이프가 트리거되는 PWM 값입니다.
|
||||
|
||||
### 지오펜스 {#geofence\_copter}
|
||||
### 지오펜스 {#geofence_copter}
|
||||
|
||||
이 패널은 원통형 [Simple Geofence](http://ardupilot.org/copter/docs/ac2_simple_geofence.html)에 대한 매개변수를 설정합니다.
|
||||
울타리 반경 또는 높이 활성화 여부, 위반 최대값 및 위반 시 조치를 설정할 수 있습니다.
|
||||
@@ -62,15 +62,15 @@ _QGroundControl_은 ArduPilot에서 폴리곤 펜스 또는 랠리 포인트를
|
||||
|
||||
설정 옵션은 다음과 같습니다:
|
||||
|
||||
- **Circle GeoFence enabled**([FENCE\_TYPE](http://ardupilot.org/copter/docs/parameters.html#fence-type-fence-type), [FENCE\_ENABLE](http://ardupilot.org/copter/docs/parameters.html#fence-enable-fence-enable-disable)) - 원형 지오펜스를 활성화합니다.
|
||||
- **Altitude GeoFence enabled**([FENCE\_TYPE](http://ardupilot.org/copter/docs/parameters.html#fence-type-fence-type), [FENCE\_ENABLE](http://ardupilot.org/copter/docs/parameters.html#fence-enable-fence-enable-disable)) - 고도 지오펜스를 활성화합니다.
|
||||
- 울타리 작업([FENCE\_ACTION](http://ardupilot.org/copter/docs/parameters.html#fence-action-fence-action)) 다음 중 하나:
|
||||
- **Circle GeoFence enabled**([FENCE_TYPE](http://ardupilot.org/copter/docs/parameters.html#fence-type-fence-type), [FENCE_ENABLE](http://ardupilot.org/copter/docs/parameters.html#fence-enable-fence-enable-disable)) - 원형 지오펜스를 활성화합니다.
|
||||
- **Altitude GeoFence enabled**([FENCE_TYPE](http://ardupilot.org/copter/docs/parameters.html#fence-type-fence-type), [FENCE_ENABLE](http://ardupilot.org/copter/docs/parameters.html#fence-enable-fence-enable-disable)) - 고도 지오펜스를 활성화합니다.
|
||||
- 울타리 작업([FENCE_ACTION](http://ardupilot.org/copter/docs/parameters.html#fence-action-fence-action)) 다음 중 하나:
|
||||
- **보고만** - 울타리 위반을 보고합니다.
|
||||
- **RTL 또는 Land** - 출발지 복귀 또는 펜스 경계 착륙
|
||||
- **최대 반경**([FENCE\_RADIUS](http://ardupilot.org/copter/docs/parameters.html#fence-radius-circular-fence-radius)) - 부서졌을 때 RTL을 유발하는 원형 울타리 반경.
|
||||
- **최대 고도**([FENCE\_ALT\_MAX](http://ardupilot.org/copter/docs/parameters.html#fence-alt-max-fence-maximum-altitude))- 고도 지오펜스를 트리거하는 최대 고도를 표시합니다.
|
||||
- **최대 반경**([FENCE_RADIUS](http://ardupilot.org/copter/docs/parameters.html#fence-radius-circular-fence-radius)) - 부서졌을 때 RTL을 유발하는 원형 울타리 반경.
|
||||
- **최대 고도**([FENCE_ALT_MAX](http://ardupilot.org/copter/docs/parameters.html#fence-alt-max-fence-maximum-altitude))- 고도 지오펜스를 트리거하는 최대 고도를 표시합니다.
|
||||
|
||||
### 출발지 복귀 {#rtl\_copter}
|
||||
### 출발지 복귀 {#rtl_copter}
|
||||
|
||||
이 패널은 [RTL 모드](http://ardupilot.org/copter/docs/rtl-mode.html)의 기능을 설정합니다.
|
||||
|
||||
@@ -78,15 +78,15 @@ _QGroundControl_은 ArduPilot에서 폴리곤 펜스 또는 랠리 포인트를
|
||||
|
||||
설정 옵션은 다음과 같습니다:
|
||||
|
||||
- RTL 복귀 고도 선택([RTL\_ALT](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-rtl-altitude)):
|
||||
- RTL 복귀 고도 선택([RTL_ALT](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-rtl-altitude)):
|
||||
- **현재 고도에서 복귀** - 현재 고도에서 복귀합니다.
|
||||
- **지정된 고도에서 복귀** - 현재 고도 미만인 경우 지정된 고도로 상승하여 복귀합니다.
|
||||
- **집 위 배회**([RTL\_LOIT\_TIME](http://ardupilot.org/copter/docs/parameters.html#rtl-loit-time-rtl-loiter-time)) - 착륙 전 배회 시간을 설정합니다.
|
||||
- **집 위 배회**([RTL_LOIT_TIME](http://ardupilot.org/copter/docs/parameters.html#rtl-loit-time-rtl-loiter-time)) - 착륙 전 배회 시간을 설정합니다.
|
||||
- 다음 중 하나
|
||||
- **하강 속도가 있는 착지**([LAND\_SPEED](http://ardupilot.org/copter/docs/parameters.html#land-speed-land-speed)) - 최종 하강 속도를 선택합니다.
|
||||
- **최종 배회 고도**([RTL\_ALT\_FINAL](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-final-rtl-final-altitude)) - RTL 또는 임무 후 착륙을 위한 최종 고도를 선택하고 설정합니다(착륙하려면 0으로 설정).
|
||||
- **하강 속도가 있는 착지**([LAND_SPEED](http://ardupilot.org/copter/docs/parameters.html#land-speed-land-speed)) - 최종 하강 속도를 선택합니다.
|
||||
- **최종 배회 고도**([RTL_ALT_FINAL](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-final-rtl-final-altitude)) - RTL 또는 임무 후 착륙을 위한 최종 고도를 선택하고 설정합니다(착륙하려면 0으로 설정).
|
||||
|
||||
### 시동 검사 {#arming\_checks\_copter}
|
||||
### 시동 검사 {#arming_checks_copter}
|
||||
|
||||
이 패널은 어떤 [사전 ARM 안전 검사](http://ardupilot.org/copter/docs/prearm_safety_check.html) 활성 여부를 설정합니다.
|
||||
|
||||
@@ -94,7 +94,7 @@ _QGroundControl_은 ArduPilot에서 폴리곤 펜스 또는 랠리 포인트를
|
||||
|
||||
설정 옵션은 다음과 같습니다:
|
||||
|
||||
- **수행할 무장 점검**([ARMING\_CHECK](http://ardupilot.org/copter/docs/parameters.html#arming-check-arm-checks-to-peform-bitmask)) - 모든 적절한 점검: 기압계, 나침반, GPS 잠금, INS, 매개변수, RC 채널, 보드 전압, 배터리 잔량, 대기 속도, 사용 가능한 로깅 , 하드웨어 안전 스위치, GPS 구성, 시스템.
|
||||
- **수행할 무장 점검**([ARMING_CHECK](http://ardupilot.org/copter/docs/parameters.html#arming-check-arm-checks-to-peform-bitmask)) - 모든 적절한 점검: 기압계, 나침반, GPS 잠금, INS, 매개변수, RC 채널, 보드 전압, 배터리 잔량, 대기 속도, 사용 가능한 로깅 , 하드웨어 안전 스위치, GPS 구성, 시스템.
|
||||
|
||||
## 비행기
|
||||
|
||||
@@ -106,13 +106,13 @@ _QGroundControl_은 ArduPilot에서 폴리곤 펜스 또는 랠리 포인트를
|
||||
추가 안전 설정 및 정보는 [비행기 안전 장치 기능](http://ardupilot.org/plane/docs/apms-failsafe-function.html) 및 [고급 안전 장치 설정](http://ardupilot.org/plane/docs/advanced-failsafe-configuration.html)을 참고하십시오.
|
||||
:::
|
||||
|
||||
### 배터리 안전장치 {#battery\_failsafe\_plane}
|
||||
### 배터리 안전장치 {#battery_failsafe_plane}
|
||||
|
||||
비행기 배터리 안전 장치는 [낮음](http://ardupilot.org/plane/docs/parameters.html#batt-fs-low-act-low-battery-failsafe-action) 및 [치명적](http://ardupilot.org/plane/docs/parameters.html#batt-fs-crt-act-critical-battery-failsafe-action) 작업(없음, RTL, 착륙, 종료)에 대해 다른 옵션이 있다는 점을 제외하고 헬리콥터와 동일합니다.
|
||||
|
||||
자세한 내용은 [배터리 안전장치](#battery_failsafe_copter)(콥터)를 참고하십시오.
|
||||
|
||||
### 안전장치 트리거 {#failsafe\_triggers\_plane}
|
||||
### 안전장치 트리거 {#failsafe_triggers_plane}
|
||||
|
||||
이 패널은 [GCS 안전장치](http://ardupilot.org/plane/docs/advanced-failsafe-configuration.html#ground-station-communications-loss)를 활성화하고 스로틀 안전장치를 설정합니다.
|
||||
|
||||
@@ -120,10 +120,10 @@ _QGroundControl_은 ArduPilot에서 폴리곤 펜스 또는 랠리 포인트를
|
||||
|
||||
설정 옵션은 다음과 같습니다:
|
||||
|
||||
- **스로틀 PWM 임계치**([THR\_FS\_VALUE](http://ardupilot.org/plane/docs/parameters.html#thr-fs-value-throttle-failsafe-value)) - 스로틀 페일세이프가 트리거되는 PWM 값입니다.
|
||||
- **GCS 비상안전장치**([FS\_GCS\_ENABL](http://ardupilot.org/plane/docs/parameters.html#fs-gcs-enabl-gcs-failsafe-enable)) - GCS 비상안전장치를 활성화합니다.
|
||||
- **스로틀 PWM 임계치**([THR_FS_VALUE](http://ardupilot.org/plane/docs/parameters.html#thr-fs-value-throttle-failsafe-value)) - 스로틀 페일세이프가 트리거되는 PWM 값입니다.
|
||||
- **GCS 비상안전장치**([FS_GCS_ENABL](http://ardupilot.org/plane/docs/parameters.html#fs-gcs-enabl-gcs-failsafe-enable)) - GCS 비상안전장치를 활성화합니다.
|
||||
|
||||
### 출발지 복귀 {#rtl\_plane}
|
||||
### 출발지 복귀 {#rtl_plane}
|
||||
|
||||
이 패널은 [RTL 모드](http://ardupilot.org/copter/docs/rtl-mode.html)의 기능을 설정합니다.
|
||||
|
||||
@@ -131,11 +131,11 @@ _QGroundControl_은 ArduPilot에서 폴리곤 펜스 또는 랠리 포인트를
|
||||
|
||||
설정 옵션은 다음과 같습니다:
|
||||
|
||||
- RTL 복귀 고도 선택([RTL\_ALT](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-rtl-altitude)):
|
||||
- RTL 복귀 고도 선택([RTL_ALT](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-rtl-altitude)):
|
||||
- **현재 고도에서 복귀** - 현재 고도에서 복귀합니다.
|
||||
- **지정된 고도에서 복귀** - 현재 고도 미만인 경우 지정된 고도로 상승하여 복귀합니다.
|
||||
|
||||
### 시동 검사 {#arming\_checks\_plane}
|
||||
### 시동 검사 {#arming_checks_plane}
|
||||
|
||||
[시동 점검](#arming_checks_copter)은 헬리콥터와 동일합니다.
|
||||
|
||||
@@ -149,11 +149,11 @@ _QGroundControl_은 ArduPilot에서 폴리곤 펜스 또는 랠리 포인트를
|
||||
추가 안전 설정 및 정보는 [비상안전장치](http://ardupilot.org/rover/docs/rover-failsafes.html)를 참고하십시오.
|
||||
:::
|
||||
|
||||
### 배터리 비상안전장치 {#battery\_failsafe\_rover}
|
||||
### 배터리 비상안전장치 {#battery_failsafe_rover}
|
||||
|
||||
로버 배터리 비상안전장치는 [콥터](#battery_failsafe_copter)와 동일합니다.
|
||||
|
||||
### 비상안전장치 트리거 {#failsafe\_triggers\_rover}
|
||||
### 비상안전장치 트리거 {#failsafe_triggers_rover}
|
||||
|
||||
이 패널은 로버 [비상안전장치](http://ardupilot.org/rover/docs/rover-failsafes.html)를 활성화합니다.
|
||||
|
||||
@@ -161,12 +161,12 @@ _QGroundControl_은 ArduPilot에서 폴리곤 펜스 또는 랠리 포인트를
|
||||
|
||||
설정 옵션은 다음과 같습니다:
|
||||
|
||||
- **지상국 비상안전장치**([FS\_GCS\_ENABL](http://ardupilot.org/rover/docs/parameters.html#fs-gcs-enable-gcs-failsafe-enable)) - GCS 비상안전장치를 활성화합니다.
|
||||
- **안전 장치 조절**([FS\_THR\_ENABLE](http://ardupilot.org/rover/docs/parameters.html#fs-thr-enable-throttle-failsafe-enable)) - 안전 장치 조절을 활성화 또는 비활성화합니다(값은 아래 _PWM 임계값_).
|
||||
- **PWM Threshold**([FS\_THR\_VALUE](http://ardupilot.org/rover/docs/parameters.html#fs-thr-value-throttle-failsafe-value)) - 스로틀 페일세이프가 트리거되는 PWM 값입니다.
|
||||
- **Failsafe Crash Check**([FS\_CRASH\_CHECK](http://ardupilot.org/rover/docs/parameters.html#fs-crash-check-crash-check-action)) - 충돌 발생 시 수행할 작업: Disabled, Hold, HoldAndDisarm
|
||||
- **지상국 비상안전장치**([FS_GCS_ENABL](http://ardupilot.org/rover/docs/parameters.html#fs-gcs-enable-gcs-failsafe-enable)) - GCS 비상안전장치를 활성화합니다.
|
||||
- **안전 장치 조절**([FS_THR_ENABLE](http://ardupilot.org/rover/docs/parameters.html#fs-thr-enable-throttle-failsafe-enable)) - 안전 장치 조절을 활성화 또는 비활성화합니다(값은 아래 _PWM 임계값_).
|
||||
- **PWM Threshold**([FS_THR_VALUE](http://ardupilot.org/rover/docs/parameters.html#fs-thr-value-throttle-failsafe-value)) - 스로틀 페일세이프가 트리거되는 PWM 값입니다.
|
||||
- **Failsafe Crash Check**([FS_CRASH_CHECK](http://ardupilot.org/rover/docs/parameters.html#fs-crash-check-crash-check-action)) - 충돌 발생 시 수행할 작업: Disabled, Hold, HoldAndDisarm
|
||||
|
||||
### 시동 검사 {#arming\_checks\_rover}
|
||||
### 시동 검사 {#arming_checks_rover}
|
||||
|
||||
[시동 점검](#arming_checks_copter)은 헬리콥터와 동일합니다.
|
||||
|
||||
@@ -180,7 +180,7 @@ _QGroundControl_은 ArduPilot에서 폴리곤 펜스 또는 랠리 포인트를
|
||||
추가 안전 설정 및 정보는 [비상안전장치](https://www.ardusub.com/operators-manual/failsafes.html)를 참고하십시오.
|
||||
:::
|
||||
|
||||
### 비상안전장치 동작 {#failsafe\_actions\_sub}
|
||||
### 비상안전장치 동작 {#failsafe_actions_sub}
|
||||
|
||||
설정 옵션은 다음과 같습니다:
|
||||
|
||||
@@ -194,6 +194,6 @@ _QGroundControl_은 ArduPilot에서 폴리곤 펜스 또는 랠리 포인트를
|
||||
- **내부 온도** - 비활성화, 경고만 중 하나를 선택합니다.
|
||||
- **내부 압력** - 비활성화, 경고만 중 하나를 선택합니다.
|
||||
|
||||
### 시동 검사 {#arming\_checks\_sub}
|
||||
### 시동 검사 {#arming_checks_sub}
|
||||
|
||||
[시동 점검](#arming_checks_copter)은 헬리콥터와 동일합니다.
|
||||
|
||||
@@ -43,7 +43,7 @@ ArduPilot은 보다 정확한 보정을 가능한 온보드 보정 기능을 사
|
||||
|
||||
이것은 각 나침반에 대한 보정 품질을 보여줍니다. 이 값을 사용하여 성능이 좋지 않은 나침반의 사용 여부를 결정합니다.
|
||||
|
||||
## 수평 보정 {#level\_horizon}
|
||||
## 수평 보정 {#level_horizon}
|
||||
|
||||
가속도계 보정 후, 수평선(HUD에 표시됨)이 수평이 아닌 경우 차량의 수평 수평을 보정할 수 있습니다.
|
||||
정보를 캡처하는 동안 기체를 수평 방향으로 배치하라는 메시지가 표시됩니다.
|
||||
@@ -91,7 +91,7 @@ CompassMot only works well if you have a battery current monitor because the mag
|
||||
|
||||
|
||||
|
||||
## 센서 설정 {#sensor\_settings}
|
||||
## 센서 설정 {#sensor_settings}
|
||||
|
||||
_센서 설정_ 섹션에서 나침반 방향과 활성화된 나침반을 지정할 수 있습니다.
|
||||
|
||||
|
||||
@@ -129,7 +129,7 @@ _센서 설정_ 섹션에서는 차량의 나침반, 자이로스코프, 가속
|
||||
|
||||
5. 덮개를 제거하기 전에 2-3 초간 기다립니다(몇 초 후 캘리브레이션이 자동으로 완료됩니다).
|
||||
|
||||
## 방향 설정 {#flight\_controller\_orientation}
|
||||
## 방향 설정 {#flight_controller_orientation}
|
||||
|
||||
:::tip
|
||||
비행 컨트롤러와 나침반이 차량에 똑바로 장착되어 있고 정면을 향하고 있는 경우 이 섹션을 건너뛸 수 있습니다(기본 방향 - `ROTATION_NONE`).
|
||||
|
||||
@@ -10,7 +10,7 @@ _QGroundControl_ 사용 방법에 대한 _질문_은 관련 플라이트 스택
|
||||
|
||||
이 포럼은 또한 _QGroundControl_에 대한 버그, 문제 및 원하는 기능에 대한 토론을 시작하기에 가장 적합합니다. 거기에서 추가 해결을 위하여 GitHub 문제에 정보를 입력할 수 있습니다.
|
||||
|
||||
### 개발자 채팅 {#developer\_chat}
|
||||
### 개발자 채팅 {#developer_chat}
|
||||
|
||||
_QGroundControl_ 개발자(및 많은 일반/깊은 관련 사용자)는 [#QGroundControl Slack 채널](https://px4.slack.com/)에서 찾을 수 있습니다.
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ Windows 64비트 시스템에서 _QGroundControl_은 때때로 **제어판 > 음
|
||||
Windows 음성 API에 대한 추가 정보는 [여기](https://www.webbie.org.uk/blog/microsoft-speech/)를 참고하십시오.
|
||||
:::
|
||||
|
||||
## Windows: UI 렌더링/비디오 드라이버 문제 {#opengl\_troubleshooting}
|
||||
## Windows: UI 렌더링/비디오 드라이버 문제 {#opengl_troubleshooting}
|
||||
|
||||
Windows에서 UI 렌더링 문제 또는 비디오 드라이버 충돌이 발생하는 경우에는 "비정상적" OpenGL 드라이버가 원인일 수 있습니다. _QGroundControl_은 "안전한" 동영상 모드에서 _QGroundControl_을 시작하는 데 사용할 수 있는 3가지 단축키를 제공합니다(순서대로 시도).
|
||||
|
||||
@@ -30,7 +30,7 @@ Windows에서 UI 렌더링 문제 또는 비디오 드라이버 충돌이 발생
|
||||
- **GPU 호환성 모드:** QGC는 DirectX 위에 OpenGL을 구현하는 ANGLE 드라이버를 사용합니다.
|
||||
- **GPU 안전 모드:** QGroundControl은 UI에 소프트웨어 래스터라이저를 사용합니다(매우 느림).
|
||||
|
||||
## Windows: WiFi 기체 연결 불량 {#waiting\_for\_connection}
|
||||
## Windows: WiFi 기체 연결 불량 {#waiting_for_connection}
|
||||
|
||||
Wi-Fi를 통해 기체 연결시 _QGroundControl_이 영구적으로 유지되는 경우(예: _기체 연결 대기_), 가능한 원인은 IP 트래픽이 방화벽 소프트웨어에 의해 차단되기 때문일 수 있습니다.
|
||||
|
||||
@@ -51,7 +51,7 @@ _Windows Defender_를 사용하는 경우:
|
||||
**Tip** 프로그램은 파일 이름이 아닌 설명의 알파벳 순서로 나열됩니다.
|
||||
_QGroundControl 개발 팀에서 제공하는 오픈 소스 지상 관제 앱_
|
||||
|
||||
## Ubuntu: 비디오 스트리밍 실패(Gstreamer 누락) {#missing\_gstreamer}
|
||||
## Ubuntu: 비디오 스트리밍 실패(Gstreamer 누락) {#missing_gstreamer}
|
||||
|
||||
Ubuntu에서 비디오 스트림을 보려면 _Gstreamer_ 구성요소를 설치하여야 합니다.
|
||||
이것들이 설치되어 있지 않으면, _QGroundControl_이 gstreamer 노드를 생성할 수 없고 다음과 같은 에러가 발생합니다.
|
||||
@@ -62,7 +62,7 @@ VideoReceiver::start()가 실패했습니다. gst_element_factory_make('avdec_h2
|
||||
|
||||
[Ubuntu용 다운로드/설치 지침](../getting_started/download_and_install.md#ubuntu)에는 _GStreamer_ 설정 정보가 포함되어 있습니다.
|
||||
|
||||
## Ubuntu 18.04: 듀얼 비디오 어댑터 시스템에서 비디오 스트리밍 실패 {#dual\_vga}
|
||||
## Ubuntu 18.04: 듀얼 비디오 어댑터 시스템에서 비디오 스트리밍 실패 {#dual_vga}
|
||||
|
||||
|
||||
|
||||
@@ -80,7 +80,7 @@ LIBVA_DRIVER_NAME=fakedriver ./QGroundControl
|
||||
|
||||
다른 대안은 VGA 중 하나를 비활성화하거나 VA API 구성 요소를 제거하거나 GStreamer 1.16으로 업그레이드하는 것입니다(Ubuntu 18.04에서는 이를 수행하는 쉬운 방법이 없습니다.
|
||||
|
||||
## Ubuntu 16.04: GLIBC\_2.27을 찾을 수 없음 {#glibc\_2\_27}
|
||||
## Ubuntu 16.04: GLIBC_2.27을 찾을 수 없음 {#glibc_2_27}
|
||||
|
||||
사전 빌드된 QGroundControl 4.0(이상)용 AppImages는 Ubuntu 18.04 LTS(이상)에서만 실행 가능합니다.
|
||||
Ubuntu 16.04에서는 실행되지 않습니다.
|
||||
|
||||
@@ -11,7 +11,7 @@
|
||||
_QGroundControl_ 개발 팀이 이러한 문제를 디버그하려면 _임무 재개_에 입력된 모든 github 문제에 다음 정보가 **제공되어야 합니다**.
|
||||
:::
|
||||
|
||||
## 임무 재개 대화창 또는 생성을 위한 일반적인 단계 {#common\_steps}
|
||||
## 임무 재개 대화창 또는 생성을 위한 일반적인 단계 {#common_steps}
|
||||
|
||||
두 가지 유형의 문제를 디버깅하려면 다음 단계가 필요합니다.
|
||||
|
||||
|
||||
@@ -24,4 +24,4 @@ Note: There is also a UAS object associated with each Vehicle which is a depreca
|
||||
|
||||
The FirmwarePlugin class is the base class for firmware plugins. A firmware plugin contains the firmware specific code, such that the Vehicle object is clean with respect to it supporting a single standard interface to the UI.
|
||||
|
||||
FirmwarePluginManager is a factory class which creates a FirmwarePlugin instance based on the MAV\_AUTOPILOT/MAV\_TYPE combination for the Vehicle.
|
||||
FirmwarePluginManager is a factory class which creates a FirmwarePlugin instance based on the MAV_AUTOPILOT/MAV_TYPE combination for the Vehicle.
|
||||
|
||||
@@ -32,12 +32,12 @@ 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). |
|
||||
| `--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. |
|
||||
| `--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. |
|
||||
|
||||
|
||||
@@ -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_.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Release Process for Custom Builds \[WIP Docs]
|
||||
# Release Process for Custom Builds [WIP Docs]
|
||||
|
||||
One of the trickier aspects of creating your own custom build is the process to keep it up to date with regular QGC. This document describes a suggested process to follow. But in reality you are welcome to use whatever branching and release strategy you want for your custom builds.
|
||||
|
||||
|
||||
@@ -28,12 +28,12 @@ The plan fence and rally points are also used in modes when no mission is runnin
|
||||
|
||||
The main fields are:
|
||||
|
||||
| Key | Description |
|
||||
| ------------------------------ | ------------------------------------------------------------------------------ |
|
||||
| `version` | The version for this file. Current version is 1. |
|
||||
| `fileType` | Must be `"Plan"`. |
|
||||
| Key | Description |
|
||||
| ------------------------------ | ------------------------------------------------------------------------------------------------- |
|
||||
| `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. |
|
||||
| [`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 |
|
||||
|
||||
@@ -82,22 +82,22 @@ 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.
|
||||
|
||||
### `SimpleItem` - Simple Mission Item {#mission\_simple\_item}
|
||||
### `SimpleItem` - Simple Mission Item {#mission_simple_item}
|
||||
|
||||
A simple item represents a single MAVLink [MISSION\_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM) command.
|
||||
A simple item represents a single MAVLink [MISSION_ITEM](https://mavlink.io/en/messages/common.html#MISSION_ITEM) command.
|
||||
|
||||
```
|
||||
{
|
||||
@@ -123,19 +123,19 @@ A simple item represents a single MAVLink [MISSION\_ITEM](https://mavlink.io/en/
|
||||
|
||||
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 |
|
||||
| `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) |
|
||||
| `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)). |
|
||||
| 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) |
|
||||
| `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}
|
||||
### Complex Mission Item {#mission_complex_item}
|
||||
|
||||
A complex item is a higher level encapsulation of multiple `MISSION_ITEM` objects treated as a single entity.
|
||||
|
||||
@@ -179,15 +179,15 @@ Complex items have these values associated with them:
|
||||
| Key | Description |
|
||||
| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `version` | The version number for this `survey` definition. Current version is 3. |
|
||||
| `type` | `ComplexItem` (this is a complex item). |
|
||||
| `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). |
|
||||
| `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. |
|
||||
|
||||
#### Corridor Scan {#corridor\_scan}
|
||||
#### Corridor Scan {#corridor_scan}
|
||||
|
||||
The object definition for a `CorridorScan` complex mission item is given below.
|
||||
|
||||
@@ -219,14 +219,14 @@ The object definition for a `CorridorScan` complex mission item is given below.
|
||||
| Key | Description |
|
||||
| ------------------------------------------------------- | --------------------------------------------------------------------- |
|
||||
| `version` | The version for this `CorridorScan` definition. Current version is 3. |
|
||||
| `type` | `ComplexItem` (this is a complex item). |
|
||||
| `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}
|
||||
#### Structure Scan {#structure_scan}
|
||||
|
||||
The object definition for a `StructureScan` complex mission item is given below.
|
||||
|
||||
@@ -264,7 +264,7 @@ 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). |
|
||||
| `type` | `ComplexItem` (this is a complex item). |
|
||||
| `complexItemType` | `StructureScan` |
|
||||
| `Altitude` | ? |
|
||||
| [`CameraCalc`](#CameraCalc) | ? |
|
||||
@@ -309,11 +309,11 @@ The object definition for a `StructureScan` complex mission item is given below.
|
||||
| --------------------------- | --------------------------------------------------------------------------------- |
|
||||
| `version` | The version for this `TransectStyleComplexItem` definition. Current version is 1. |
|
||||
| [`CameraCalc`](#CameraCalc) | ? |
|
||||
| `CameraTriggerInTurnAround` | ? (boolean) |
|
||||
| `FollowTerrain` | ? (boolean) |
|
||||
| `HoverAndCapture` | ? (boolean) |
|
||||
| `CameraTriggerInTurnAround` | ? (boolean) |
|
||||
| `FollowTerrain` | ? (boolean) |
|
||||
| `HoverAndCapture` | ? (boolean) |
|
||||
| `Items` | ? |
|
||||
| `Refly90Degrees` | ? (boolean) |
|
||||
| `Refly90Degrees` | ? (boolean) |
|
||||
| `TurnAroundDistance` | The distance to fly past the polygon edge prior to turning for the next transect. |
|
||||
| `VisualTransectPoints` | ? |
|
||||
|
||||
@@ -344,25 +344,25 @@ 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 |
|
||||
| `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. |
|
||||
| `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) |
|
||||
|
||||
## GeoFence {#geofence}
|
||||
@@ -384,13 +384,13 @@ 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}
|
||||
### Circle Geofence {#circle_geofence}
|
||||
|
||||
Each circular geofence is defined in a separate item, as shown below (multiple comma-separated items can be defined).
|
||||
The items define the centre and radius of the circle, and whether or not the specific geofence is activated.
|
||||
@@ -408,13 +408,13 @@ The items define the centre and radius of the circle, and whether or not the spe
|
||||
|
||||
The fields are:
|
||||
|
||||
| Key | Description |
|
||||
| ----------- | -------------------------------------------------------------------------------------------------- |
|
||||
| `version` | The version number for the geofence "circle" plan format. The documented version is 1. |
|
||||
| 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. |
|
||||
|
||||
### Polygon Geofence {#polygon\_geofence}
|
||||
### Polygon Geofence {#polygon_geofence}
|
||||
|
||||
Each polygon geofence is defined in a separate item, as shown below (multiple comma-separated items can be defined).
|
||||
The geofence includes a set of points defined with a clockwise winding (i.e. they must enclose an area).
|
||||
@@ -453,9 +453,9 @@ The fields are:
|
||||
| ----------- | ------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| `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}
|
||||
## Rally Points {#rally_points}
|
||||
|
||||
Rally point information is optional.
|
||||
The plan can contain an arbitrary number of rally points, each of which has a latitude, longitude, and altitude (above home position).
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
qt_version: 5.15.2
|
||||
qt_version: 6.6.1
|
||||
---
|
||||
|
||||
# Getting Started with Source and Builds
|
||||
@@ -46,30 +46,96 @@ We support Linux builds using a container found on the source tree of the reposi
|
||||
|
||||
### Native Builds
|
||||
|
||||
_QGroundControl_ builds are supported for macOS, Linux, Windows, iOS and Android.
|
||||
_QGroundControl_ uses [Qt](http://www.qt.io) as its cross-platform support library and uses [QtCreator](http://doc.qt.io/qtcreator/index.html) as its default build environment.
|
||||
_QGroundControl_ builds are supported for macOS, Linux, Windows, and Android. Creating a version of QGC for iOS is theoretically possible but is no longer supported as a standard build.
|
||||
_QGroundControl_ uses [Qt](http://www.qt.io) as its cross-platform support library.
|
||||
|
||||
- **macOS:** v10.11 or higher
|
||||
- **Ubuntu:** 64 bit, gcc compiler
|
||||
- **Windows:** Vista or higher, [Visual Studio 2019 compiler](#vs) (64 bit)
|
||||
- **iOS:** 10.0 and higher
|
||||
- **Android:** Android 5.0 and later.
|
||||
- Standard QGC is built against ndk version 19.
|
||||
- Java JDK 11 is required.
|
||||
- **Qt version:** {{ $frontmatter.qt\_version }} **(only)** <!-- NOTE {{ $frontmatter.qt_version }} is set in the frontmatter above -->
|
||||
The required version of Qt is {{ $frontmatter.qt_version }} **(only)**.
|
||||
|
||||
::: warning
|
||||
**Do not use any other version of Qt!**
|
||||
QGC has been thoroughly tested with the specified version of Qt ({{ $frontmatter.qt\_version }}).
|
||||
There is a significant risk that other Qt versions will inject bugs that affect stability and safety (even if QGC compiles).
|
||||
:::
|
||||
::: warning
|
||||
**Do not use any other version of Qt!**
|
||||
QGC has been thoroughly tested with the specified version of Qt ({{ $frontmatter.qt_version }}).
|
||||
There is a significant risk that other Qt versions will inject bugs that affect stability and safety (even if QGC compiles).
|
||||
:::
|
||||
|
||||
For more information see: [Qt 5 supported platform list](http://doc.qt.io/qt-5/supported-platforms.html).
|
||||
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.
|
||||
|
||||
To install Qt:
|
||||
|
||||
1. Download and run the [Qt Online Installer](http://www.qt.io/download-open-source)
|
||||
- **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`
|
||||
- **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
|
||||
|
||||
::: 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).
|
||||
|
||||
#### 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:
|
||||
|
||||
- **OSX:** Desktop Qt {{ $frontmatter.qt_version }} clang 64 bit
|
||||
|
||||
::: info
|
||||
iOS builds must be built using [XCode](http://doc.qt.io/qt-5/ios-support.html).
|
||||
:::
|
||||
|
||||
- **Ubuntu:** Desktop Qt {{ $frontmatter.qt_version }} GCC 64bit
|
||||
|
||||
- **Windows:** Desktop Qt {{ $frontmatter.qt_version }} MSVC2019 **64bit**
|
||||
|
||||
- **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_**.
|
||||
|
||||
3. Build using the "hammer" (or "play") icons:
|
||||
|
||||
|
||||
|
||||
#### 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)
|
||||
@@ -82,94 +148,6 @@ When installing, select _Desktop development with C++_ as shown:
|
||||
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.
|
||||
:::
|
||||
|
||||
#### Install Qt
|
||||
|
||||
You **need to install Qt as described below** instead of using pre-built packages from say, a Linux distribution, because _QGroundControl_ needs access to private Qt headers.
|
||||
|
||||
To install Qt:
|
||||
|
||||
1. Download and run the [Qt Online Installer](http://www.qt.io/download-open-source)
|
||||
- **Ubuntu:**
|
||||
- Set the downloaded file to executable using: `chmod +x`.
|
||||
- Install to default location for use with **./qgroundcontrol-start.sh.** If you install Qt to a non-default location you will need to modify **qgroundcontrol-start.sh** in order to run downloaded builds.
|
||||
|
||||
2. In the installer _Select Components_ dialog choose: {{ $frontmatter.qt\_version }}.
|
||||
|
||||
::: info
|
||||
If the version needed is not displayed, check the archive (show archive and refresh).
|
||||
:::
|
||||
|
||||
Then install just the following components:
|
||||
|
||||
- **Windows**: _MSVC 2019 64 bit_
|
||||
- **MacOS**: _macOS_
|
||||
- **Linux**: _Desktop gcc 64-bit_
|
||||
- All:
|
||||
- _Qt Charts_ <!-- and *Qt Remote Objects (TP)* -->
|
||||
- _Android ARMv7_ (optional, used to build Android)
|
||||
|
||||
|
||||
|
||||
3. Install Additional Packages (Platform Specific)
|
||||
|
||||
- **Ubuntu:** `sudo apt-get install speech-dispatcher libudev-dev libsdl2-dev patchelf build-essential curl`
|
||||
- **Fedora:** `sudo dnf install speech-dispatcher SDL2-devel SDL2 systemd-devel patchelf`
|
||||
- **Arch Linux:** `pacman -Sy speech-dispatcher patchelf`
|
||||
- **Android:** [Qt Android Setup](http://doc.qt.io/qt-5/androidgs.html)
|
||||
|
||||
::: info
|
||||
JDK11 is required (install if needed)!
|
||||
:::
|
||||
|
||||
4. 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).
|
||||
- **Airmap SDK:** - TBD.
|
||||
|
||||
5. Disable platform-specific optional features that are enabled (but not installed), by default.
|
||||
|
||||
::: info
|
||||
This currently applies to Airmap on Linux, which is optional but enabled by default.
|
||||
:::
|
||||
|
||||
- **Ubuntu:**
|
||||
|
||||
- Airmap: Create a file named **user\_config.pri** (in the repo root directory) containing the text `DEFINES += DISABLE_AIRMAP`.
|
||||
This can be done in a bash terminal using the command:
|
||||
|
||||
```sh
|
||||
echo -e "DEFINES += DISABLE_AIRMAP\r\n" | tee user_config.pri
|
||||
```
|
||||
|
||||
#### 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:
|
||||
|
||||
- **OSX:** Desktop Qt {{ $frontmatter.qt\_version }} clang 64 bit
|
||||
|
||||
::: info
|
||||
iOS builds must be built using [XCode](http://doc.qt.io/qt-5/ios-support.html).
|
||||
:::
|
||||
|
||||
- **Ubuntu:** Desktop Qt {{ $frontmatter.qt\_version }} GCC 64bit
|
||||
|
||||
- **Windows:** Desktop Qt {{ $frontmatter.qt\_version }} MSVC2019 **64bit**
|
||||
|
||||
- **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_**.
|
||||
|
||||
3. Build using the "hammer" (or "play") icons:
|
||||
|
||||
|
||||
|
||||
#### Build using qmake on CLI {#qmake}
|
||||
|
||||
Example commands to build a default QGC and run it afterwards:
|
||||
@@ -227,7 +205,6 @@ Example commands to build a default QGC and run it afterwards:
|
||||
### Additional Build Notes for all Supported OS
|
||||
|
||||
- **Parallel builds:** For non Windows builds, you can use the `-j#` option to run parellel builds.
|
||||
- **Location of built files:** Individual build file results can be found in the `build_debug` or `build_release` directories. The built executable can be found in the `debug` or `release` directory.
|
||||
- **If you get this error when running _QGroundControl_**: `/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version 'GLIBCXX_3.4.20' not found.`, you need to either update to the latest _gcc_, or install the latest _libstdc++.6_ using: `sudo apt-get install libstdc++6`.
|
||||
- **Unit tests:** To run the [unit tests](../contribute/unit_tests.md), build in `debug` mode with `UNITTEST_BUILD` definition, and then copy `deploy/qgroundcontrol-start.sh` script into the `debug` directory before running the tests.
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ The current stable build is the highest quality build available for QGC.
|
||||
Stable builds are built from a separate branch that is named with the format: `Stable_VX.Y` (note, there is no patch number!)
|
||||
The branch has one or more git tags for each patch release (with the format `vX.Y.Z`), indicating the point in the repo source code that the associated patch release was created from.
|
||||
|
||||
### Patch Releases {#patch\_releases}
|
||||
### Patch Releases {#patch_releases}
|
||||
|
||||
A patch release contains fixes to the stable release that are important enough to _require_ an update, and are safe enough that the stable release continues to maintain high quality.
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ Yukarıdaki ekran görüntüsü, uçuş ekranının ana öğelerini gösterir:
|
||||
- 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.
|
||||
- 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).
|
||||
@@ -49,7 +49,7 @@ Yukarıdaki ekran görüntüsü, uçuş ekranının ana öğelerini gösterir:
|
||||
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}
|
||||
## Bilgi Paneli {#instrument_panel}
|
||||
|
||||
The instrument panel displays telemetry information about the current vehicle.
|
||||
|
||||
@@ -81,7 +81,7 @@ The selection list on the top right is used to select a particular telemetry val
|
||||
|
||||
Aracı devre dışı bırakmak için araç **landed** halindeyken _Fly Toolbar_ 'dan **Armed**'ı seçin.
|
||||
|
||||
### Kamera {#camera\_instrument\_page}
|
||||
### Kamera {#camera_instrument_page}
|
||||
|
||||
Kamera sayfası, kamerayı ayarlamak ve kontrol etmek için kullanılır.
|
||||
|
||||
@@ -103,7 +103,7 @@ Most of the settings that are displayed depend on the camera (they are defined i
|
||||
|
||||
> 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 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.
|
||||
@@ -117,7 +117,7 @@ Aşağıdaki bölümler, Uçuş Ekranı'nda genel işlemlerin / görevlerin nas
|
||||
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}
|
||||
### 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.
|
||||
|
||||
@@ -135,7 +135,7 @@ 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.
|
||||
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.
|
||||
@@ -184,7 +184,7 @@ You will then need to use the disarming slider.
|
||||
|
||||
Aracı uçarken devre dışı bırakmak [Emergency Stop](#emergency_stop) olarak adlandırılır
|
||||
|
||||
### Acil Durdurma {#emergency\_stop}
|
||||
### 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!
|
||||
@@ -235,7 +235,7 @@ 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}
|
||||
### 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:
|
||||
|
||||
@@ -303,7 +303,7 @@ Durdurmak için:
|
||||
|
||||
### Görevler
|
||||
|
||||
#### Görevi Başlatma {#start\_mission}
|
||||
#### Görevi Başlatma {#start_mission}
|
||||
|
||||
Araç inmiş durumdayken bir görevi başlatabilirsiniz (görevi başlatma onay kaydıracı varsayılan olarak çoğu kez gösterilir).
|
||||
|
||||
@@ -321,7 +321,7 @@ Yerdeki bir aracın görevini başlatmak için:
|
||||
|
||||
|
||||
|
||||
#### Göreve Devam Etme (Continue Mission) {#continue\_mission}
|
||||
#### Göreve Devam Etme (Continue Mission) {#continue_mission}
|
||||
|
||||
Göreve _sıradaki_ hedef noktanızdan _devam_ edebilirsiniz (_Continue Mission_ kaydırmalı onay butonu kalkıştan sonra çoğu kez varsayılan olarak gösterilir).
|
||||
|
||||
@@ -343,7 +343,7 @@ Görevinize aşağıdakileri yaparak devam edebilirsiniz (hali hazırda bir gör
|
||||
|
||||
|
||||
|
||||
#### Göreve Devam Etme (Resume Mission) {#resume\_mission}
|
||||
#### Göreve Devam Etme (Resume Mission) {#resume_mission}
|
||||
|
||||
_Resume Mission_, bir görevin içinde [RTL/Return](#rtl) ya da [Land](#land) gerçekleştirdikten sonra (ör. batarya değiştirmek için) kullanılır.
|
||||
|
||||
@@ -368,12 +368,12 @@ Bir görev, basit bir şekilde aracın son gerçekleştirdiği görev aşamasın
|
||||
Basit bir şekilde devam etmek yerine, _QGroundControl_ son gerçekleştirilen görev aşamasından başlayarak, ilgili komutları da dikkate alarak görevi tekrar yapılandırır.
|
||||
:::
|
||||
|
||||
#### İnişten Sonra Görevi Kaldırma {#resume\_mission\_prompt}
|
||||
#### İnişten Sonra Görevi Kaldırma {#resume_mission_prompt}
|
||||
|
||||
Görev bittikten sonra aracın inişi ve devre dışı bırakılmasının ardından görevi araçtan kaldırmanız istenecektir.
|
||||
This is meant to prevent issues where stale missions are unknowingly left on a vehicle, potentially resulting in unexpected behavior.
|
||||
|
||||
### Videoyu Görüntüleme {#video\_switcher}
|
||||
### Videoyu Görüntüleme {#video_switcher}
|
||||
|
||||
Video akışı etkinleştirildiğinde, _QGroundControl_ haritanın sol altında bulunan "videoya geçiş penceresi"nde videoyu göstermeye başlıyacaktır.
|
||||
You can press the switcher anywhere to toggle _Video_ and _Map_ to foreground (in the image below, the video is shown in the foreground).
|
||||
|
||||
@@ -36,7 +36,7 @@ Manuel olarak 32 bit sürümler oluşturmak mümkündür (bu, geliştirici ekip
|
||||
|
||||
_QGroundControl_ can be installed on macOS 10.11 or later: <!-- match version using https://dev.qgroundcontrol.com/master/en/getting_started/#native-builds -->
|
||||
|
||||
<!-- match version using https://dev.qgroundcontrol.com/master/en/getting_started/#native-builds -->
|
||||
<!-- match version using https://docs.qgroundcontrol.com/master/en/qgc-dev-guide/getting_started/#native-builds -->
|
||||
|
||||
<!-- usually based on Qt macOS dependency -->
|
||||
|
||||
@@ -55,8 +55,8 @@ QGroundControl continues to not be signed which causes problem on Catalina. To o
|
||||
_QGroundControl_ can be installed/run on Ubuntu LTS 20.04 (and later).
|
||||
|
||||
Ubuntu, bir seri bağlantı noktasının (veya USB serisinin) robotikle ilgili kullanımına müdahale eden bir seri modem yöneticisi ile birlikte gelir.
|
||||
\_ QGroundControl \_ 'ü kurmadan önce modem yöneticisini kaldırmalı ve seri bağlantı noktasına erişim için kendinize izin vermelisiniz.
|
||||
Ayrıca video akışını desteklemek için \_ GStreamer \_ 'ı da yüklemeniz gerekmektedir.
|
||||
_ QGroundControl _ 'ü kurmadan önce modem yöneticisini kaldırmalı ve seri bağlantı noktasına erişim için kendinize izin vermelisiniz.
|
||||
Ayrıca video akışını desteklemek için _ GStreamer _ 'ı da yüklemeniz gerekmektedir.
|
||||
|
||||
QGroundControl \* 'ı ilk kez kurmadan önce:
|
||||
|
||||
@@ -71,7 +71,7 @@ QGroundControl \* 'ı ilk kez kurmadan önce:
|
||||
<!-- Note, remove install of libqt5gui5 https://github.com/mavlink/qgroundcontrol/issues/10176 fixed -->
|
||||
2. Logout and login again to enable the change to user permissions.
|
||||
|
||||
\_ QGroundControl \_ yüklemek için:
|
||||
_ QGroundControl _ yüklemek için:
|
||||
|
||||
1. Download [QGroundControl.AppImage](https://d176tv9ibo4jno.cloudfront.net/latest/QGroundControl.AppImage).
|
||||
2. Install (and run) using the terminal commands:
|
||||
|
||||
@@ -17,7 +17,7 @@ _QGroundControl_'e alışmanın iyi bir yolu denemeye başlamaktır:
|
||||
- [Setup](../setup_view/setup_view.md): Aracınızı yapılandırın ve ayarlayın.
|
||||
- [Plan](../plan_view/plan_view.md): Otonom görevler oluşturun.
|
||||
- [Fly](../fly_view/fly_view.md): Video akışıyla birlikte araç(lar)ınızı uçarken izleyin.
|
||||
- \[Analyze] \*\* Description of Analyze view is missing \*\*
|
||||
- [Analyze] \*\* Description of Analyze view is missing \*\*
|
||||
- Bağlı aracın durumunu öğrenmek için araç çubuğundaki _Status icons_'a tıklayın.
|
||||
|
||||
Kullanıcı arayüzü gayet açık olsa da, daha fazlasını öğrenmek için bu dokümantasyona başvurulabilir.
|
||||
|
||||
@@ -5,9 +5,9 @@ Uygun şablon araçları, araca (ve uçuş dizinindeki araç tipinin desteğine)
|
||||
|
||||
|
||||
|
||||
| Ş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 |
|
||||
| Ş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 |
|
||||
| [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 |
|
||||
|
||||
@@ -77,7 +77,7 @@ Ayarlanabilir seçenekler şunlardır:
|
||||
- **Relative altitude** - Bağlı bir yüksekik belirtmek için işaretleyin. Bu özellik sadece [terrain following](#terrain_following) kullanmayan manuel ayarlanmış ızgaralarda desteklenir.
|
||||
- **Rotate entry point** - Koridor taramasının başlangıç ve bitiş noktasını birbirleriyle değiştirmek için butona basın.
|
||||
|
||||
### Arazi Takibi {#terrain\_following}
|
||||
### Arazi Takibi {#terrain_following}
|
||||
|
||||
Varsayılan olarak, uçan bir araç sabit bir yükseklikte koridor yolunu takip edecektir.
|
||||
_Terrain Following_'i aktif hale getirmek, aracın yere göre sabit bir yükseklikte devam etmesini sağlar.
|
||||
|
||||
@@ -22,7 +22,7 @@ Uçuş yolundaki yeşil numaralı daire, taramaya giriş/çıkış noktasıdır
|
||||
|
||||
|
||||
|
||||
Tarama, yapıyı eşit olarak katmanlara ayırır; araç, yapının çevresinde belirli bir irtifada ve yapıya \_ scan distance\_'den uçar, ardından tüm yüzey taranana kadar işlemi her katmanda tekrarlar.
|
||||
Tarama, yapıyı eşit olarak katmanlara ayırır; araç, yapının çevresinde belirli bir irtifada ve yapıya _ scan distance_'den uçar, ardından tüm yüzey taranana kadar işlemi her katmanda tekrarlar.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -46,7 +46,7 @@ Mevcut kameraların listesi (QGC 3.4) aşağıda verilmiştir.
|
||||
|
||||
|
||||
|
||||
#### Bilinen Kamera {#known\_camera}
|
||||
#### Bilinen Kamera {#known_camera}
|
||||
|
||||
Seçenekler açılır listesinden bilinen bir kamerayı seçmek, kameranın özelliklerine göre bir ızgara deseni oluşturur.
|
||||
|
||||
@@ -61,7 +61,7 @@ Varsayılan ayarlar, yapılandırma seçenekleri kullanılarak gözleminiz için
|
||||
- **Altitude** - Tarama yüksekliği (bu yükseklik için zemin çözünürlüğü hesaplanacak/görüntülenecektir).
|
||||
- **Ground resolution** - Her görüntü için zemin çözünürlüğü (bu çözünürlüğü sağlamak için gerekli yükseklik hesaplanacak/görüntülenecektir).
|
||||
|
||||
#### Özel Kamera {#custom\_camera}
|
||||
#### Özel Kamera {#custom_camera}
|
||||
|
||||
Özel kamera seçeneğinin seçilmesi, yeni bir kamera için ayarları bilinen bir kameraya benzer şekilde belirlemenize olanak tanır.
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ Toparlanma Noktası oluşturmak için:
|
||||
- şu anda aktif olan işaretçi farklı bir renge (yeşil) sahiptir ve _Rally Point_ paneli kullanılarak düzenlenebilir.
|
||||
4. Harita üzerinde seçerek herhangi bir toplanma noktasını etkinleştirin:
|
||||
- Seçilen toplanma noktasını harita üzerinde sürükleyerek veya paneldeki konumu düzenleyerek hareket ettirin.
|
||||
- Aktif toplanma noktasını \_ Rally Point\_ panelindeki menü seçeneğini seçerek silin 
|
||||
- Aktif toplanma noktasını _ Rally Point_ panelindeki menü seçeneğini seçerek silin 
|
||||
|
||||
## Upload Rally Points
|
||||
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
# Plan Ekranı
|
||||
|
||||
_Plan View_, aracınız için \_ otonom görevler \_ planlamak ve onları araca yüklemek için kullanılır. Görev [planlanıp](#plan_mission) araca gönderildiğinde, görevi gerçekleştirmek için [Uçuş Ekranı](../fly_view/fly_view.md)'na geçillir.
|
||||
_Plan View_, aracınız için _ otonom görevler _ planlamak ve onları araca yüklemek için kullanılır. Görev [planlanıp](#plan_mission) araca gönderildiğinde, görevi gerçekleştirmek için [Uçuş Ekranı](../fly_view/fly_view.md)'na geçillir.
|
||||
|
||||
Ayrıca eğer yazılım tarafından destekleniyorsa [GeoFence](plan_geofence.md) ve [Rally Points](plan_rally_points.md)'leri ayalarmak için kullanılır.
|
||||
|
||||
<span id="plan_screenshot"></span>
|
||||
|
||||
|
||||
## Kullanıcı Arayüzü'ne Genel Bakış {#ui\_overview}
|
||||
## Kullanıcı Arayüzü'ne Genel Bakış {#ui_overview}
|
||||
|
||||
Yukarıdaki [ ekran görüntüsü ](#plan_screenshot), [ Planlanan Ev ](#planned_home) konumundan (H) kalkışla başlayan basit bir görev planını gösterir, üç hedef noktadan geçer ve ardından son hedef noktaya (yani hedef noktası 3) iner.
|
||||
|
||||
@@ -24,7 +24,7 @@ Arayüzün temel elemanları şunlardır:
|
||||
|
||||
Size o anda seçili olan hedef noktasıyla ilgili bilgilerin yanı sıra tüm görevin istatistiklerini gösterir.
|
||||
|
||||
## Görev Planlama {#plan\_mission}
|
||||
## Görev Planlama {#plan_mission}
|
||||
|
||||
At very high level, the steps to create a mission are:
|
||||
|
||||
@@ -35,7 +35,7 @@ At very high level, the steps to create a mission are:
|
||||
|
||||
Aşağıdaki bölümler, ekrandaki bazı ayrıntıları açıklamaktadır.
|
||||
|
||||
## Planlanmış Ev Konumu {#planned\_home}
|
||||
## Planlanmış Ev Konumu {#planned_home}
|
||||
|
||||
The _Planned Home_ shown in _Plan View_ is used to set the approximate start point when planning a mission (i.e. when a vehicle may not even be connected to QGC).
|
||||
QGC tarafından görev sürelerini tahmin etmek ve hedef noktalar arası çizgileri çizmek için kullanılır.
|
||||
@@ -51,7 +51,7 @@ Planlanan ana konumun yüksekliği, [ Mission Settings ](#mission_settings) pane
|
||||
The Fly View displays the _actual_ home position set by the vehicle firmware when it arms (this is where the vehicle will return in Return/RTL mode).
|
||||
:::
|
||||
|
||||
## Plan Araçları {#plan\_tools}
|
||||
## Plan Araçları {#plan_tools}
|
||||
|
||||
Plan araçları, ara noktalar eklemek, karmaşık yerler için görev oluşturmayı kolaylaştırmak, görevleri yüklemek/indirmek/kaydetmek/geri yüklemek ve haritada gezinmek için kullanılır. Ana araçlar aşağıda açıklanmıştır.
|
||||
|
||||
@@ -80,13 +80,13 @@ _Dosya araçları_ aşağıdaki fonksiyonları sağlar:
|
||||
- İndir (Araçtan yüklemek)
|
||||
- KML dosyası dahil olmak üzere Dosyaya Kaydet/Farklı Kaydet.
|
||||
- Dosyadan Yükle
|
||||
- Tümünü Kaldır (tüm görev hedef noktalarını \_ Plan ekranından\_ ve araçtan kaldırır)
|
||||
- Tümünü Kaldır (tüm görev hedef noktalarını _ Plan ekranından_ ve araçtan kaldırır)
|
||||
|
||||
### Şablon
|
||||
|
||||
[Pattern](Pattern.md) aracı, [gözlem](../plan_view/pattern_survey.md) ve [yapı taramaları](../plan_view/pattern_structure_scan_v2.md) da dahil olmak üzere karmaşık şekillerin uçulması için görevlerin oluşturulmasını basitleştirir.
|
||||
|
||||
## Görev Komutları Listesi {#mission\_command\_list}
|
||||
## Görev Komutları Listesi {#mission_command_list}
|
||||
|
||||
Mission commands for the current mission are listed on the right side of the view.
|
||||
En üstte görev, coğrafi sınır ve toparlanma noktaları arasında geçiş yapmak için bir dizi seçenek vardır.
|
||||
@@ -94,24 +94,24 @@ Listede, değerlerini düzenlemek için görev öğelerini ayrı ayrı seçebili
|
||||
|
||||
|
||||
|
||||
### Görev Komutları Düzenleyicisi {#mission\_command\_editors}
|
||||
### Görev Komutları Düzenleyicisi {#mission_command_editors}
|
||||
|
||||
Düzenleyicisini görüntülemek için listedeki bir görev komutuna tıklayın (buradan komut özellikerini ayarlayabilir/değiştirebilirsiniz).
|
||||
|
||||
Komut adına tıklayarak komutun \*\* tipini \*\* değiştirebilirsiniz (örneğin: _Waypoint_).
|
||||
Bu, aşağıda gösterilen \_ Select Mission Command\_ diyaloğunu görüntüler.
|
||||
Bu, aşağıda gösterilen _ Select Mission Command_ diyaloğunu görüntüler.
|
||||
Varsayılan olarak bu sadece "Temel Komutlar" görüntülenir, daha fazlasını görüntülemek için \*\* Category\*\* açılır menüsünü kullanabilirsiniz (örneğin tüm seçenekleri görmek için \*\* All commands \*\* 'ı seçin).
|
||||
|
||||
<img src="../../../assets/plan/mission/mission_commands.jpg" style="width: 200px;"/>
|
||||
|
||||
Her komut adının sağında, \_ Ekle \_ ve \_ Sil \_ gibi ek seçeneklere erişmek için tıklayabileceğiniz bir menü bulunur.
|
||||
Her komut adının sağında, _ Ekle _ ve _ Sil _ gibi ek seçeneklere erişmek için tıklayabileceğiniz bir menü bulunur.
|
||||
|
||||
:::info
|
||||
Kullanılabilir komutların listesi aracın yazılımına ve türüne bağlıdır.
|
||||
Örnek olarak şunlar verilebilir: Hedef nokta, Görüntü yakalamayı başlat, Öğeye atla (görevi tekrarlamak için) ve diğer komutlar.
|
||||
:::
|
||||
|
||||
### Görev Ayarları {#mission\_settings}
|
||||
### Görev Ayarları {#mission_settings}
|
||||
|
||||
_Mission Start_ paneli [ görev komut listesinde ](#mission_command_list) görünen ilk öğedir.
|
||||
Görevin başlangıcını veya sonunu etkileyebilecek bir takım varsayılan ayarı düzenlemek için kullanılabilir.
|
||||
@@ -145,7 +145,7 @@ Bu, kalkıştan görevin tamamlanmasına kadar aracınızın hedef noktalar aras
|
||||
|
||||
|
||||
:::info
|
||||
Bu yalnızca \_ planlanan \_ ev konumudur ve aracı çalıştırmayı planladığınız yere konumlandırılmalıdır.
|
||||
Bu yalnızca _ planlanan _ ev konumudur ve aracı çalıştırmayı planladığınız yere konumlandırılmalıdır.
|
||||
Görevin gerçekleşmesinde gerçek bir etkisi yoktur.
|
||||
Asıl ev konumu, araç tarafından devreye alınırken ayarlanır.
|
||||
:::
|
||||
@@ -181,7 +181,7 @@ Bu değer belirtilerek, bir araca bağlı olmasa bile toplam görev veya anket s
|
||||
|
||||
## Sorun Giderme
|
||||
|
||||
### Görev (Plan) Yükleme/İndirme Hataları {#plan\_transfer\_fail}
|
||||
### Görev (Plan) Yükleme/İndirme Hataları {#plan_transfer_fail}
|
||||
|
||||
Plan yükleme ve indirme, kötü bir iletişim bağlantısında hata verebilir (görevleri, coğrafi sınırları ve toparlanma noktalarını etkiler).
|
||||
Bir arıza meydana gelirse, QGC kullanıcı arayüzünde aşağıdakine benzer bir durum mesajı görmelisiniz:
|
||||
|
||||
@@ -80,7 +80,7 @@ This section contains a high level and _non-exhaustive_ list of new features add
|
||||
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.
|
||||
- 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.
|
||||
@@ -137,7 +137,7 @@ This section contains a high level and _non-exhaustive_ list of new features add
|
||||
- **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 HIGH_LATENCY MavLink message.
|
||||
Supports failover back/forth from high latency to normal link with dual link setup.
|
||||
|
||||
## Stable Version 3.3
|
||||
|
||||
@@ -41,7 +41,7 @@ This is now supported from the Sensors page.
|
||||
|
||||
This is now supported from the Copy Trims button on the Radio setup page.
|
||||
|
||||
## Plan View {#plan\_view}
|
||||
## Plan View {#plan_view}
|
||||
|
||||
### Plan Files
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ 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 {#plan\_view}
|
||||
### Plan View {#plan_view}
|
||||
|
||||
#### Structure Scan
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ Click the **Set Logging** button to enable/disable logging information displayed
|
||||
|
||||
The most commmonly used logging options are listed below.
|
||||
|
||||
| Option(s) | Description |
|
||||
| Option(s) | Description |
|
||||
| ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
|
||||
| `LinkManagerLog`, `MultiVehicleManagerLog` | Debug connection problems. |
|
||||
| `LinkManagerVerboseLog` | Debug serial ports not being detected. Very noisy continuous output of available serial ports. |
|
||||
|
||||
@@ -64,7 +64,7 @@ The settings are:
|
||||
|
||||
- <span id="load_save_path"></span>**Application Load/Save Path**: Default location for loading/saving application files, including: parameters, telemetry logs, and mission plans.
|
||||
|
||||
## Data Persistence {#data\_persistence}
|
||||
## Data Persistence {#data_persistence}
|
||||
|
||||
|
||||
|
||||
@@ -72,7 +72,7 @@ The settings are:
|
||||
|
||||
- **Disable all data persistence**: Check to prevent any data being saved or cached: logs, map tiles etc.
|
||||
|
||||
## Telemetry Logs from Vehicle {#telemetry\_logs}
|
||||
## Telemetry Logs from Vehicle {#telemetry_logs}
|
||||
|
||||
|
||||
|
||||
@@ -83,7 +83,7 @@ The settings are:
|
||||
Stops logging when the last vehicle disconnects.
|
||||
- [**CSV Logging**](csv.md): Log subset of telemetry data to a CSV file.
|
||||
|
||||
## Fly View {#fly\_view}
|
||||
## Fly View {#fly_view}
|
||||
|
||||
|
||||
|
||||
@@ -117,7 +117,7 @@ The settings are:
|
||||
|
||||
- **Go To Location Max Distance**: The maximum distance that a Go To location can be set from the current vehicle location (in guided mode).
|
||||
|
||||
## Plan View {#plan\_view}
|
||||
## Plan View {#plan_view}
|
||||
|
||||
|
||||
|
||||
@@ -125,7 +125,7 @@ The settings are:
|
||||
|
||||
- **Default Mission Altitude**: The default altitude used for the Mission Start Panel, and hence for the first waypoint.
|
||||
|
||||
## AutoConnect to the following devices {#auto\_connect}
|
||||
## AutoConnect to the following devices {#auto_connect}
|
||||
|
||||
This section defines the set of devices to which _QGroundControl_ will auto-connect.
|
||||
|
||||
@@ -141,7 +141,7 @@ Settings include:
|
||||
- **RTK GPS:** Autoconnect to RTK GPS device
|
||||
- **NMEA GPS Device:** Autoconnect to an external GPS device to get ground station position ([see below](#nmea_gps))
|
||||
|
||||
### Ground Station Location (NMEA GPS Device) {#nmea\_gps}
|
||||
### Ground Station Location (NMEA GPS Device) {#nmea_gps}
|
||||
|
||||
_QGroundControl_ will automatically use an internal GPS to display its own location on the map with a purple `Q` icon (if the GPS provides a heading, this will be also indicated by the icon).
|
||||
It may also use the GPS as a location source for _Follow Me Mode_ - currently supported on [PX4 Multicopters only](https://docs.px4.io/en/flight_modes/follow_me.html).
|
||||
@@ -173,7 +173,7 @@ Use the _NMEA GPS Device_ drop-down selector to manually select the GPS device a
|
||||
- **NMEA GPS Device:** _UDP Port_.
|
||||
- **NMEA Stream UDP Port**: The UDP port on which QGC will listen for NMEA data (QGC binds the port as a server)
|
||||
|
||||
## RTK GPS {#rtk\_gps}
|
||||
## RTK GPS {#rtk_gps}
|
||||
|
||||
This section allows you to specify the RTK GPS "Survey-in" settings, to save and reuse the result of a Survey-In operation, or to directly enter any other known position for the base station.
|
||||
|
||||
@@ -203,7 +203,7 @@ The settings are:
|
||||
- **Base Position Accuracy:** Accuracy of base station position information.
|
||||
- **Save Current Base Position** (button): Press to copy settings from the last Survey-In operation to the _Use Specified Base Position_ fields above.
|
||||
|
||||
## ADSB Server {#adsb\_server}
|
||||
## ADSB Server {#adsb_server}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ The screen also allows you to manage [MAVLink 2 Log Streaming](#logging) (PX4 on
|
||||
|
||||
|
||||
|
||||
## Ground Station {#ground\_station}
|
||||
## Ground Station {#ground_station}
|
||||
|
||||
This section sets the MAVLink properties and behaviour of _QGroundControl_.
|
||||
|
||||
@@ -23,7 +23,7 @@ This section sets the MAVLink properties and behaviour of _QGroundControl_.
|
||||
Note that this forwarding is one-way: from QGC to the specified host.
|
||||
Any MAVLink messages that are received from the specified host will be ignored.
|
||||
|
||||
## Link Status {#link\_status}
|
||||
## Link Status {#link_status}
|
||||
|
||||
This shows the status of MAVLink message transfer over the communications link.
|
||||
A high **Loss rate** may lead to protocol errors for things like parameter download or mission upload/download.
|
||||
|
||||
@@ -4,11 +4,11 @@ QGroundControl \*'ün \*\* masaüstü \*\* sürümleri [ PX4 Pro ](http://px4.io
|
||||
|
||||
QGroundControl \* ayrıca SiK Radyoları ve PX4 Flow cihazları için yazılımları da yükleyebilir.
|
||||
|
||||
> **Caution** Yazılım Yükleme özelliği şu anda \_ QGroundControl \_ tablet veya telefon sürümlerinde kullanılamamaktadır.
|
||||
> **Caution** Yazılım Yükleme özelliği şu anda _ QGroundControl _ tablet veya telefon sürümlerinde kullanılamamaktadır.
|
||||
|
||||
## Yazılım Güncellemesi için Cihazı Bağlayın
|
||||
|
||||
> **Caution** **Before you start installing Firmware** all USB connections to your vehicle must be _disconnected_ (both direct or through a telemetry radio). Araca bir batarya ile \_ güç verilmemelidir \_.
|
||||
> **Caution** **Before you start installing Firmware** all USB connections to your vehicle must be _disconnected_ (both direct or through a telemetry radio). Araca bir batarya ile _ güç verilmemelidir _.
|
||||
|
||||
1. İlk olarak üstteki araç çubuğundan **dişli** simgesini (_Vehicle Setup_), daha sonra kenar çubuğundan **Firmware**'i seçin.
|
||||
|
||||
@@ -22,9 +22,9 @@ QGroundControl \* ayrıca SiK Radyoları ve PX4 Flow cihazları için yazılıml
|
||||
|
||||
## Yüklenecek Yazılımı Seçin
|
||||
|
||||
Cihaz bağlandıktan sonra, hangi aygıt yazılımının yükleneceğini seçebilirsiniz (\_ QGroundControl \_, bağlı donanıma göre mantıklı seçenekler sunar).
|
||||
Cihaz bağlandıktan sonra, hangi aygıt yazılımının yükleneceğini seçebilirsiniz (_ QGroundControl _, bağlı donanıma göre mantıklı seçenekler sunar).
|
||||
|
||||
1. Pixhawk uyumlu bir anakart için \_ mevcut kararlı sürümü \_ indirmek için \*\* PX4 Flight Stack vX.X.X Stable Release \*\* veya \*\* ArduPilot Flight Stack \*\* seçeneklerinden birini seçin.
|
||||
1. Pixhawk uyumlu bir anakart için _ mevcut kararlı sürümü _ indirmek için \*\* PX4 Flight Stack vX.X.X Stable Release \*\* veya \*\* ArduPilot Flight Stack \*\* seçeneklerinden birini seçin.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -8,17 +8,17 @@ QGroundControl \*, bir aracı RC Verici yerine bir joystick veya gamepad kullana
|
||||
|
||||
:::info
|
||||
\*\* Note \*\* Joystick ve Gamepad desteği, çapraz platform [ SDL2 ](http://www.libsdl.org/index.php) kitaplığı kullanılarak etkinleştirilir.
|
||||
Belirli bir kontrolcüyle uyumluluk, SDL'ye bağlıdır (bu API tarafından gösterilen tüm düğmeler, \_ QGroundControl \_ arayüzü aracılığıyla görüntülenir).
|
||||
Belirli bir kontrolcüyle uyumluluk, SDL'ye bağlıdır (bu API tarafından gösterilen tüm düğmeler, _ QGroundControl _ arayüzü aracılığıyla görüntülenir).
|
||||
[Çok sayıda yaygın oyun çubuğu ve oyun kolunun ](#supported-joysticks) çalıştığı bilinmektedir.
|
||||
:::
|
||||
|
||||
:::info
|
||||
\*\* Note \*\* Kumanda kolu, kalibrasyon işleminin son adımı olarak \_ etkinleştirilir \_.
|
||||
\*\* Note \*\* Kumanda kolu, kalibrasyon işleminin son adımı olarak _ etkinleştirilir _.
|
||||
:::
|
||||
|
||||
## 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`](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_.
|
||||
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).
|
||||
@@ -46,7 +46,7 @@ Joystick'i ayarlamak için:
|
||||
|
||||
|
||||
|
||||
Joystick, kalibrasyon işleminin son adımı olarak \_ etkinleştirilir \_.
|
||||
Joystick, kalibrasyon işleminin son adımı olarak _ etkinleştirilir _.
|
||||
|
||||
6. Düğmelerin ve çubukların amaçlandığı gibi çalışıp çalışmadığını onlara basarak ve sonucu \*\* General \*\* sekmesindeki Axis/Buton monitöründe görüntüleyerek test edin.
|
||||
|
||||
@@ -62,12 +62,12 @@ Bu seçenekler, duyarlılığı artırmak için belirli alışılmadık kuruluml
|
||||
|
||||
|
||||
|
||||
- **Center stick is zero throttle**: Ortalanmış veya alçaltılmış gaz çubuğu [ MANUAL\_CONTROL **z** ](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) ile 0, kaldırılmış gaz çubuğu 1000 gönderir.
|
||||
- **Center stick is zero throttle**: Ortalanmış veya alçaltılmış gaz çubuğu [ MANUAL_CONTROL **z** ](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) ile 0, kaldırılmış gaz çubuğu 1000 gönderir.
|
||||
- **Spring loaded throttle smoothing**: Bu modda gazın kendisini değil, artıp / azaldığı hızı kontrol edersiniz.
|
||||
This is useful for setups where the throttle stick is spring loaded, as the user can hold the desired throttle while releasing the stick.
|
||||
- **Full down stick is zero throttle**: Bu modda, alçaltılmış çubuk [ MANUAL\_CONTROL **z** ](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) için 0, ortalanmış çubuk 500 ve kaldırılmış çubuk 1000 gönderir.
|
||||
- **Full down stick is zero throttle**: Bu modda, alçaltılmış çubuk [ MANUAL_CONTROL **z** ](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) için 0, ortalanmış çubuk 500 ve kaldırılmış çubuk 1000 gönderir.
|
||||
- **Allow negative thrust**: \*\* Center stick is zero throttle \*\* modundayken, bu mod, kullanıcının çubuğu indirerek negatif değerler göndermesini sağlar.
|
||||
Böylece, indirilen çubuk [ MANUAL\_CONTROL **z** ](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) 'de -1000 gönderir, ortalanmış çubuk 0 gönderir ve yükseltilmiş çubuk 1000 gönderir.
|
||||
Böylece, indirilen çubuk [ MANUAL_CONTROL **z** ](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) 'de -1000 gönderir, ortalanmış çubuk 0 gönderir ve yükseltilmiş çubuk 1000 gönderir.
|
||||
Bu mod sadece [ Rover ](http://ardupilot.org/rover/index.html) gibi negatif itişi destekleyen araçlar için etkinleştirilebilir.
|
||||
|
||||
### Expo
|
||||
@@ -95,11 +95,11 @@ Yanlış kullanılırlarsa beklenmeyen sonuçlara neden olabilirler.
|
||||
|
||||
- **Joystick Mode**: Joystick'in gerçekte neyi kontrol ettiğini ve araca gönderilen MAVLink mesajlarını değiştirir.
|
||||
|
||||
- **Normal**: Kullanıcı normal bir RC radyo kullanıyormuş gibi kontrol eder, MAVLink [ MANUAL\_CONTROL ](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) mesajları kullanılır.
|
||||
- **Attitude**: Kullanıcı aracın duruşunu kontrol eder, MAVLink [ SET\_ATTITUDE\_TARGET ](https://mavlink.io/en/messages/common.html#SET_ATTITUDE_TARGET) mesajları kullanılır.
|
||||
- **Position**: Kullanıcı araç konumunu kontrol eder, \*\* konumu \*\* için yalnızca bit maskeli MAVLink [ SET\_POSITION\_TARGET\_LOCAL\_NED ](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) mesajları kullanılır.
|
||||
- **Force**: Kullanıcı araca uygulanan kuvvetleri kontrol eder, \*\* kuvvet \*\* için yalnızca bit maskeli MAVLink [ SET\_POSITION\_TARGET\_LOCAL\_NED ](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) mesajları kullanılır.
|
||||
- **Velocity**: Kullanıcı araca uygulanan kuvvetleri kontrol eder, \*\* hız \*\* için yalnızca bit maskeli MAVLink [ SET\_POSITION\_TARGET\_LOCAL\_NED ](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) mesajları kullanılır.
|
||||
- **Normal**: Kullanıcı normal bir RC radyo kullanıyormuş gibi kontrol eder, MAVLink [ MANUAL_CONTROL ](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) mesajları kullanılır.
|
||||
- **Attitude**: Kullanıcı aracın duruşunu kontrol eder, MAVLink [ SET_ATTITUDE_TARGET ](https://mavlink.io/en/messages/common.html#SET_ATTITUDE_TARGET) mesajları kullanılır.
|
||||
- **Position**: Kullanıcı araç konumunu kontrol eder, \*\* konumu \*\* için yalnızca bit maskeli MAVLink [ SET_POSITION_TARGET_LOCAL_NED ](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) mesajları kullanılır.
|
||||
- **Force**: Kullanıcı araca uygulanan kuvvetleri kontrol eder, \*\* kuvvet \*\* için yalnızca bit maskeli MAVLink [ SET_POSITION_TARGET_LOCAL_NED ](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) mesajları kullanılır.
|
||||
- **Velocity**: Kullanıcı araca uygulanan kuvvetleri kontrol eder, \*\* hız \*\* için yalnızca bit maskeli MAVLink [ SET_POSITION_TARGET_LOCAL_NED ](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) mesajları kullanılır.
|
||||
|
||||
- **Axis Frequency**: Joystick boştayken (gelen veriler değişmiyorken), joystick komutları araca 5Hz'de gönderilir. Joystick kullanımdayken (giriş değerleri değişiyorken), joystick komutları araca bu ayarla yapılandırılan (daha yüksek) frekansta gönderilir. Varsayılan değer 25Hz'dir.
|
||||
|
||||
@@ -126,7 +126,7 @@ Yanlış kullanılırlarsa beklenmeyen sonuçlara neden olabilirler.
|
||||
|
||||
## Desteklenen Joystickler
|
||||
|
||||
Aşağıdaki kumanda kollarının/kontrol cihazlarının nispeten yeni \_ QGroundControl \_ versiyonlarıyla çalıştığı görülmüştür.
|
||||
Aşağıdaki kumanda kollarının/kontrol cihazlarının nispeten yeni _ QGroundControl _ versiyonlarıyla çalıştığı görülmüştür.
|
||||
|
||||
### Sony Playstation 3/4 Kontrolcüleri
|
||||
|
||||
@@ -158,8 +158,8 @@ Adımlar şunlardır:
|
||||
<span></span>
|
||||
```
|
||||
4. Kontrolcünün LED'i hızla yanıp sönmeye başlayana kadar \*\* Share \*\* düğmesini ve sonra \*\* PS \*\* düğmesini basılı tutun.
|
||||
Daha sonra \_ ds4drv \_ yeni bir aygıt algılamalıdır.
|
||||
5. Son olarak, \_ jstest-gtk \_ yardımcı programını çalıştırarak denetleyici kurulumunu kontrol etmelisiniz.
|
||||
Daha sonra _ ds4drv _ yeni bir aygıt algılamalıdır.
|
||||
5. Son olarak, _ jstest-gtk _ yardımcı programını çalıştırarak denetleyici kurulumunu kontrol etmelisiniz.
|
||||
|
||||
### FrSky Taranis XD9 plus
|
||||
|
||||
@@ -191,7 +191,7 @@ Bu oyun kumandası, QGroundControl aracılığıyla bir multirotoru manuel olara
|
||||
#### Mac OS Leopard / Lion Kurulumu
|
||||
|
||||
F710, Leopard / Lion'da algılanır, ancak otomatik olarak bir giriş cihazı olarak yapılandırılmaz.
|
||||
Çalışan bir konfigürasyon elde etmek için, F710'un \_ Rumblepad2 \_ olarak tanınması gerekir.
|
||||
Çalışan bir konfigürasyon elde etmek için, F710'un _ Rumblepad2 _ olarak tanınması gerekir.
|
||||
|
||||
Önce nasıl tanındığını kontrol edin: \*\* Apple> Bu Mac Hakkında> Ek Bilgi> Sistem Raporu> USB \*\*.
|
||||
"Logitech Cordless RumblePad 2" olarak algılanmışsa bundan sonra başka bir işlem yapılmasına gerek yoktur.
|
||||
|
||||
@@ -18,9 +18,9 @@ Motorları test etmek için:
|
||||
> \*\* Uyarı \*\* Pervaneleri, motorları etkinleştirmeden önce çıkarmalısınız!
|
||||
> :::
|
||||
|
||||
2. (\_ yalnızca PX4 \_) güvenlik anahtarını etkinleştirin - varsa.
|
||||
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. 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.
|
||||
|
||||
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.
|
||||
|
||||
|
||||
@@ -3,9 +3,9 @@
|
||||
ArduSub'un düzgün çalışması için motorların doğru şekilde kurulması gerekir.
|
||||
|
||||
ROV'nuzu yeni monte ettiyseniz, önce \*\* Manuel Test \*\* bölümünde iticilerin doğru çıkışlara bağlandığından emin olun.
|
||||
Her kaydırıcıyı sürükleyin ve görüntülenen gövdeye göre \_ doğru motorun \_ döndüğünden emin olun.
|
||||
Her kaydırıcıyı sürükleyin ve görüntülenen gövdeye göre _ doğru motorun _ döndüğünden emin olun.
|
||||
|
||||
İticilerinin uygun çıkışlara bağlandığından emin olduktan sonra,\_ doğru yönü \_ (ileri / geri) kontrol etmek için [ otomatik yön algılama ](#automatic) (ArduSub 4.0'dan iibaren tavsiye edilir) veya [ manuel test](#manual) seçeneklerinden birini kullanabilirsiniz.
|
||||
İticilerinin uygun çıkışlara bağlandığından emin olduktan sonra,_ doğru yönü _ (ileri / geri) kontrol etmek için [ otomatik yön algılama ](#automatic) (ArduSub 4.0'dan iibaren tavsiye edilir) veya [ manuel test](#manual) seçeneklerinden birini kullanabilirsiniz.
|
||||
|
||||
:::info
|
||||
\*\* Note \*\* [ Manuel Test ](#manual) ArduSub tarafından 3.5 sürümüne kadar desteklenirken, ArduSub 4.0 hem [ Manuel Testi ](#manual) hem de [ otomatik yön algılamayı ](#automatic) destekler.
|
||||
@@ -37,7 +37,7 @@ Otomatik motor yönü algılamasını gerçekleştirmek için \*\*Vehicle Setup-
|
||||
İşlemle ilgili ek çıktı, işlem gerçekleşirken düğmenin yanında gösterilecektir.
|
||||
|
||||
:::warning
|
||||
Bu prosedür hala motorların gövde görünümünde gösterildiği gibi \_ doğru çıkışlara \_ bağlanmasını gerektirir!
|
||||
Bu prosedür hala motorların gövde görünümünde gösterildiği gibi _ doğru çıkışlara _ bağlanmasını gerektirir!
|
||||
:::
|
||||
|
||||
|
||||
|
||||
@@ -10,9 +10,9 @@ PX4 Pro ve ArduPilot farklı parametre setleri kullanır, ancak her ikisi de bu
|
||||
|
||||
## Bir Parametreyi Bulma
|
||||
|
||||
Parametreler gruplar halinde düzenlenmiştir. Soldaki butonlara tıklayarak görüntülemek için bir parametre grubu seçin (yukarıdaki görüntüde \_ Pil Kalibrasyonu \_ grubu seçilir).
|
||||
Parametreler gruplar halinde düzenlenmiştir. Soldaki butonlara tıklayarak görüntülemek için bir parametre grubu seçin (yukarıdaki görüntüde _ Pil Kalibrasyonu _ grubu seçilir).
|
||||
|
||||
Ayrıca \_ Search\_ alanına bir terim girerek bir parametre için \_ arama \_ yapabilirsiniz. Bu size girilen alt diziyi içeren tüm parametre adlarının ve açıklamalarının bir listesini gösterecektir (aramayı sıfırlamak için \*\* Clear \*\* tuşuna basın).
|
||||
Ayrıca _ Search_ alanına bir terim girerek bir parametre için _ arama _ yapabilirsiniz. Bu size girilen alt diziyi içeren tüm parametre adlarının ve açıklamalarının bir listesini gösterecektir (aramayı sıfırlamak için \*\* Clear \*\* tuşuna basın).
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -22,10 +22,10 @@ Radyoyu kalibre etmek için:
|
||||
|
||||
::: info
|
||||
|
||||
Yukardaki görüntü PX4 Pro içindir. Her iki aygıt yazılımı için kalibrasyon/üst bölüm aynıdır, ancak \_ Ek Radyo Ayarları \_ bölümü farklı olacaktır.
|
||||
Yukardaki görüntü PX4 Pro içindir. Her iki aygıt yazılımı için kalibrasyon/üst bölüm aynıdır, ancak _ Ek Radyo Ayarları _ bölümü farklı olacaktır.
|
||||
:::
|
||||
|
||||
4. Verici yapılandırmanıza uyan radyo \_ verici modunu \_ seçin (bu, \_ QGroundControl \_ 'ın kalibrasyon sırasında izlemeniz için doğru çubuk pozisyonlarını görüntülemesini sağlar).
|
||||
4. Verici yapılandırmanıza uyan radyo _ verici modunu _ seçin (bu, _ QGroundControl _ 'ın kalibrasyon sırasında izlemeniz için doğru çubuk pozisyonlarını görüntülemesini sağlar).
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ The Copter safety page is shown below.
|
||||
For additional safety settings and information see: [Failsafe](http://ardupilot.org/copter/docs/failsafe-landing-page.html).
|
||||
:::
|
||||
|
||||
### Battery Failsafe {#battery\_failsafe\_copter}
|
||||
### Battery Failsafe {#battery_failsafe_copter}
|
||||
|
||||
This panel sets the [Battery Failsafe](http://ardupilot.org/copter/docs/failsafe-battery.html) parameters.
|
||||
You can set low and critical thresholds for voltage and/or remaining capacity and define the action if the failsafe value is breached.
|
||||
@@ -34,14 +34,14 @@ If there is a second battery (enabled in the [Power Setup](../setup_view/power.m
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- **Low action** ([BATT\_FS\_LOW\_ACT](http://ardupilot.org/copter/docs/parameters.html#batt-fs-low-act-low-battery-failsafe-action)) - Select one of: None, Land, RTL, SmartRTL, SmartRTL or Land, Terminate.
|
||||
- **Critical action** ([BATT\_FS\_CRT\_ACT](http://ardupilot.org/copter/docs/parameters.html#batt-fs-crt-act-critical-battery-failsafe-action)) - Select one of: None, Land, RTL, SmartRTL, SmartRTL or Land, Terminate.
|
||||
- **Low voltage threshold** ([BATT\_LOW\_VOLT](http://ardupilot.org/copter/docs/parameters.html#batt-low-volt-low-battery-voltage)) - Battery voltage that triggers the _low action_.
|
||||
- **Critical voltage threshold** ([BATT\_CRT\_VOLT](http://ardupilot.org/copter/docs/parameters.html#batt-crt-volt-critical-battery-voltage))- Battery voltage that triggers the _critical action_.
|
||||
- **Low mAh threshold** ([BATT\_LOW\_MAH](http://ardupilot.org/copter/docs/parameters.html#batt-low-mah-low-battery-capacity)) - Battery capacity that triggers the _low action_.
|
||||
- **Critical mAh threshold** ([BATT\_CRT\_MAH](http://ardupilot.org/copter/docs/parameters.html#batt-crt-mah-battery-critical-capacity)) - Battery capacity that triggers the _critical action_.
|
||||
- **Low action** ([BATT_FS_LOW_ACT](http://ardupilot.org/copter/docs/parameters.html#batt-fs-low-act-low-battery-failsafe-action)) - Select one of: None, Land, RTL, SmartRTL, SmartRTL or Land, Terminate.
|
||||
- **Critical action** ([BATT_FS_CRT_ACT](http://ardupilot.org/copter/docs/parameters.html#batt-fs-crt-act-critical-battery-failsafe-action)) - Select one of: None, Land, RTL, SmartRTL, SmartRTL or Land, Terminate.
|
||||
- **Low voltage threshold** ([BATT_LOW_VOLT](http://ardupilot.org/copter/docs/parameters.html#batt-low-volt-low-battery-voltage)) - Battery voltage that triggers the _low action_.
|
||||
- **Critical voltage threshold** ([BATT_CRT_VOLT](http://ardupilot.org/copter/docs/parameters.html#batt-crt-volt-critical-battery-voltage))- Battery voltage that triggers the _critical action_.
|
||||
- **Low mAh threshold** ([BATT_LOW_MAH](http://ardupilot.org/copter/docs/parameters.html#batt-low-mah-low-battery-capacity)) - Battery capacity that triggers the _low action_.
|
||||
- **Critical mAh threshold** ([BATT_CRT_MAH](http://ardupilot.org/copter/docs/parameters.html#batt-crt-mah-battery-critical-capacity)) - Battery capacity that triggers the _critical action_.
|
||||
|
||||
### General Failsafe Triggers {#failsafe\_triggers\_copter}
|
||||
### General Failsafe Triggers {#failsafe_triggers_copter}
|
||||
|
||||
This panel enables the [GCS Failsafe](http://ardupilot.org/copter/docs/gcs-failsafe.html) and enables/configures the throttle failsafe.
|
||||
|
||||
@@ -51,9 +51,9 @@ The configuration options are:
|
||||
|
||||
- **Ground Station failsafe** - Disabled, Enabled always RTL, Enabled Continue with Mission in Auto Mode, Enabled Always SmartRTL or RTL, Enabled Always SmartRTL or Land.
|
||||
- **Throttle failsafe** - Disabled, Always RTL, Continue with Mission in Auto Mode, Always land.
|
||||
- **PWM Threshold** ([FS\_THR\_VALUE](http://ardupilot.org/copter/docs/parameters.html#fs-thr-value-throttle-failsafe-value)) - PWM value below which throttle failsafe triggers.
|
||||
- **PWM Threshold** ([FS_THR_VALUE](http://ardupilot.org/copter/docs/parameters.html#fs-thr-value-throttle-failsafe-value)) - PWM value below which throttle failsafe triggers.
|
||||
|
||||
### Geofence {#geofence\_copter}
|
||||
### Geofence {#geofence_copter}
|
||||
|
||||
This panel sets the parameters for the cylindrical [Simple Geofence](http://ardupilot.org/copter/docs/ac2_simple_geofence.html).
|
||||
You can set whether the fence radius or height are enabled, the maximum values for causing a breach, and the action in the event of a breach.
|
||||
@@ -62,15 +62,15 @@ You can set whether the fence radius or height are enabled, the maximum values f
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- **Circle GeoFence enabled** ([FENCE\_TYPE](http://ardupilot.org/copter/docs/parameters.html#fence-type-fence-type), [FENCE\_ENABLE](http://ardupilot.org/copter/docs/parameters.html#fence-enable-fence-enable-disable)) - Enable the circular geofence.
|
||||
- **Altitude GeoFence enabled** ([FENCE\_TYPE](http://ardupilot.org/copter/docs/parameters.html#fence-type-fence-type), [FENCE\_ENABLE](http://ardupilot.org/copter/docs/parameters.html#fence-enable-fence-enable-disable)) - Enable altitude geofence.
|
||||
- Fence action ([FENCE\_ACTION](http://ardupilot.org/copter/docs/parameters.html#fence-action-fence-action)) One of:
|
||||
- **Circle GeoFence enabled** ([FENCE_TYPE](http://ardupilot.org/copter/docs/parameters.html#fence-type-fence-type), [FENCE_ENABLE](http://ardupilot.org/copter/docs/parameters.html#fence-enable-fence-enable-disable)) - Enable the circular geofence.
|
||||
- **Altitude GeoFence enabled** ([FENCE_TYPE](http://ardupilot.org/copter/docs/parameters.html#fence-type-fence-type), [FENCE_ENABLE](http://ardupilot.org/copter/docs/parameters.html#fence-enable-fence-enable-disable)) - Enable altitude geofence.
|
||||
- Fence action ([FENCE_ACTION](http://ardupilot.org/copter/docs/parameters.html#fence-action-fence-action)) One of:
|
||||
- **Report only** - Report fence breach.
|
||||
- **RTL or Land** - RTL or land on fence breach.
|
||||
- **Max radius** ([FENCE\_RADIUS](http://ardupilot.org/copter/docs/parameters.html#fence-radius-circular-fence-radius)) - Circular fence radius that when broken causes RTL.
|
||||
- **Max altitude** ([FENCE\_ALT\_MAX](http://ardupilot.org/copter/docs/parameters.html#fence-alt-max-fence-maximum-altitude))- Fence maximum altitude to trigger altitude geofence.
|
||||
- **Max radius** ([FENCE_RADIUS](http://ardupilot.org/copter/docs/parameters.html#fence-radius-circular-fence-radius)) - Circular fence radius that when broken causes RTL.
|
||||
- **Max altitude** ([FENCE_ALT_MAX](http://ardupilot.org/copter/docs/parameters.html#fence-alt-max-fence-maximum-altitude))- Fence maximum altitude to trigger altitude geofence.
|
||||
|
||||
### Return to Launch {#rtl\_copter}
|
||||
### Return to Launch {#rtl_copter}
|
||||
|
||||
This panel sets the [RTL Mode](http://ardupilot.org/copter/docs/rtl-mode.html) behaviour.
|
||||
|
||||
@@ -78,15 +78,15 @@ This panel sets the [RTL Mode](http://ardupilot.org/copter/docs/rtl-mode.html) b
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- Select RTL return altitude ([RTL\_ALT](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-rtl-altitude)):
|
||||
- Select RTL return altitude ([RTL_ALT](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-rtl-altitude)):
|
||||
- **Return at current altitude** - Return at current altitude.
|
||||
- **Return at specified altitude** - Ascend to specified altitude to return if below current altitude.
|
||||
- **Loiter above home for** ([RTL\_LOIT\_TIME](http://ardupilot.org/copter/docs/parameters.html#rtl-loit-time-rtl-loiter-time)) - Check to set a loiter time before landing.
|
||||
- **Loiter above home for** ([RTL_LOIT_TIME](http://ardupilot.org/copter/docs/parameters.html#rtl-loit-time-rtl-loiter-time)) - Check to set a loiter time before landing.
|
||||
- One of
|
||||
- **Land with descent speed** ([LAND\_SPEED](http://ardupilot.org/copter/docs/parameters.html#land-speed-land-speed)) - Select final descent speed.
|
||||
- **Final loiter altitude** ([RTL\_ALT\_FINAL](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-final-rtl-final-altitude)) - Select and set final altitude for landing after RTL or mission (set to 0 to land).
|
||||
- **Land with descent speed** ([LAND_SPEED](http://ardupilot.org/copter/docs/parameters.html#land-speed-land-speed)) - Select final descent speed.
|
||||
- **Final loiter altitude** ([RTL_ALT_FINAL](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-final-rtl-final-altitude)) - Select and set final altitude for landing after RTL or mission (set to 0 to land).
|
||||
|
||||
### Arming Checks {#arming\_checks\_copter}
|
||||
### Arming Checks {#arming_checks_copter}
|
||||
|
||||
This panel sets which [Pre-ARM Safety Checks](http://ardupilot.org/copter/docs/prearm_safety_check.html) are enabled.
|
||||
|
||||
@@ -94,7 +94,7 @@ This panel sets which [Pre-ARM Safety Checks](http://ardupilot.org/copter/docs/p
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- **Arming Checks to perform** ([ARMING\_CHECK](http://ardupilot.org/copter/docs/parameters.html#arming-check-arm-checks-to-peform-bitmask)) - Check all appropriate: Barometer, Compass, GPS lock, INS, Parameters, RC Channels, Board voltage, Battery Level, Airspeed, Logging Available, Hardware safety switch, GPS Configuration, System.
|
||||
- **Arming Checks to perform** ([ARMING_CHECK](http://ardupilot.org/copter/docs/parameters.html#arming-check-arm-checks-to-peform-bitmask)) - Check all appropriate: Barometer, Compass, GPS lock, INS, Parameters, RC Channels, Board voltage, Battery Level, Airspeed, Logging Available, Hardware safety switch, GPS Configuration, System.
|
||||
|
||||
## Plane
|
||||
|
||||
@@ -106,13 +106,13 @@ The Plane safety page is shown below.
|
||||
For additional safety settings and information see: [Plane Failsafe Function](http://ardupilot.org/plane/docs/apms-failsafe-function.html) and [Advanced Failsafe Configuration](http://ardupilot.org/plane/docs/advanced-failsafe-configuration.html).
|
||||
:::
|
||||
|
||||
### Battery Failsafe {#battery\_failsafe\_plane}
|
||||
### Battery Failsafe {#battery_failsafe_plane}
|
||||
|
||||
The plane battery failsafe is the same as for copter except there are different options for the [Low](http://ardupilot.org/plane/docs/parameters.html#batt-fs-low-act-low-battery-failsafe-action) and [Critical](http://ardupilot.org/plane/docs/parameters.html#batt-fs-crt-act-critical-battery-failsafe-action) actions: None, RTL, Land, Terminate.
|
||||
|
||||
For more information see: [battery failsafe](#battery_failsafe_copter) (copter).
|
||||
|
||||
### Failsafe Triggers {#failsafe\_triggers\_plane}
|
||||
### Failsafe Triggers {#failsafe_triggers_plane}
|
||||
|
||||
This panel enables the [GCS Failsafe](http://ardupilot.org/plane/docs/advanced-failsafe-configuration.html#ground-station-communications-loss) and enables/configures the throttle failsafe.
|
||||
|
||||
@@ -120,10 +120,10 @@ This panel enables the [GCS Failsafe](http://ardupilot.org/plane/docs/advanced-f
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- **Throttle PWM threshold** ([THR\_FS\_VALUE](http://ardupilot.org/plane/docs/parameters.html#thr-fs-value-throttle-failsafe-value)) - PWM value below which throttle failsafe triggers.
|
||||
- **GCS failsafe** ([FS\_GCS\_ENABL](http://ardupilot.org/plane/docs/parameters.html#fs-gcs-enabl-gcs-failsafe-enable)) - Check to enable GCS failsafe.
|
||||
- **Throttle PWM threshold** ([THR_FS_VALUE](http://ardupilot.org/plane/docs/parameters.html#thr-fs-value-throttle-failsafe-value)) - PWM value below which throttle failsafe triggers.
|
||||
- **GCS failsafe** ([FS_GCS_ENABL](http://ardupilot.org/plane/docs/parameters.html#fs-gcs-enabl-gcs-failsafe-enable)) - Check to enable GCS failsafe.
|
||||
|
||||
### Return to Launch {#rtl\_plane}
|
||||
### Return to Launch {#rtl_plane}
|
||||
|
||||
This panel sets the [RTL Mode](http://ardupilot.org/copter/docs/rtl-mode.html) behaviour.
|
||||
|
||||
@@ -131,11 +131,11 @@ This panel sets the [RTL Mode](http://ardupilot.org/copter/docs/rtl-mode.html) b
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- Select RTL return altitude ([RTL\_ALT](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-rtl-altitude)):
|
||||
- Select RTL return altitude ([RTL_ALT](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-rtl-altitude)):
|
||||
- **Return at current altitude** - Return at current altitude.
|
||||
- **Return at specified altitude** - Ascend to specified altitude to return if below current altitude.
|
||||
|
||||
### Arming Checks {#arming\_checks\_plane}
|
||||
### Arming Checks {#arming_checks_plane}
|
||||
|
||||
[Arming Checks](#arming_checks_copter) are the same as for copter.
|
||||
|
||||
@@ -149,11 +149,11 @@ The Rover safety page is shown below.
|
||||
For additional safety settings and information see: [Failsafes](http://ardupilot.org/rover/docs/rover-failsafes.html).
|
||||
:::
|
||||
|
||||
### Battery Failsafe {#battery\_failsafe\_rover}
|
||||
### Battery Failsafe {#battery_failsafe_rover}
|
||||
|
||||
The rover battery failsafe is the same as for [copter](#battery_failsafe_copter).
|
||||
|
||||
### Failsafe Triggers {#failsafe\_triggers\_rover}
|
||||
### Failsafe Triggers {#failsafe_triggers_rover}
|
||||
|
||||
This panel enables the rover [Failsafes](http://ardupilot.org/rover/docs/rover-failsafes.html).
|
||||
|
||||
@@ -161,12 +161,12 @@ This panel enables the rover [Failsafes](http://ardupilot.org/rover/docs/rover-f
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- **Ground Station failsafe** ([FS\_GCS\_ENABL](http://ardupilot.org/rover/docs/parameters.html#fs-gcs-enable-gcs-failsafe-enable)) - Check to enable GCS failsafe.
|
||||
- **Throttle failsafe** ([FS\_THR\_ENABLE](http://ardupilot.org/rover/docs/parameters.html#fs-thr-enable-throttle-failsafe-enable)) - Enable/disable throttle failsafe (value is _PWM threshold_ below).
|
||||
- **PWM threshold** ([FS\_THR\_VALUE](http://ardupilot.org/rover/docs/parameters.html#fs-thr-value-throttle-failsafe-value)) - PWM value below which throttle failsafe triggers.
|
||||
- **Failsafe Crash Check** ([FS\_CRASH\_CHECK](http://ardupilot.org/rover/docs/parameters.html#fs-crash-check-crash-check-action)) - What to do in the event of a crash: Disabled, Hold, HoldAndDisarm
|
||||
- **Ground Station failsafe** ([FS_GCS_ENABL](http://ardupilot.org/rover/docs/parameters.html#fs-gcs-enable-gcs-failsafe-enable)) - Check to enable GCS failsafe.
|
||||
- **Throttle failsafe** ([FS_THR_ENABLE](http://ardupilot.org/rover/docs/parameters.html#fs-thr-enable-throttle-failsafe-enable)) - Enable/disable throttle failsafe (value is _PWM threshold_ below).
|
||||
- **PWM threshold** ([FS_THR_VALUE](http://ardupilot.org/rover/docs/parameters.html#fs-thr-value-throttle-failsafe-value)) - PWM value below which throttle failsafe triggers.
|
||||
- **Failsafe Crash Check** ([FS_CRASH_CHECK](http://ardupilot.org/rover/docs/parameters.html#fs-crash-check-crash-check-action)) - What to do in the event of a crash: Disabled, Hold, HoldAndDisarm
|
||||
|
||||
### Arming Checks {#arming\_checks\_rover}
|
||||
### Arming Checks {#arming_checks_rover}
|
||||
|
||||
[Arming Checks](#arming_checks_copter) are the same as for copter.
|
||||
|
||||
@@ -180,7 +180,7 @@ The Sub safety page is shown below.
|
||||
For additional safety settings and information see: [Failsafes](https://www.ardusub.com/operators-manual/failsafes.html).
|
||||
:::
|
||||
|
||||
### Failsafe Actions {#failsafe\_actions\_sub}
|
||||
### Failsafe Actions {#failsafe_actions_sub}
|
||||
|
||||
The configuration options are:
|
||||
|
||||
@@ -194,6 +194,6 @@ The configuration options are:
|
||||
- **Internal Temperature** - Select one of: Disabled, Warn only.
|
||||
- **Internal Pressure** - Select one of: Disabled, Warn only.
|
||||
|
||||
### Arming Checks {#arming\_checks\_sub}
|
||||
### Arming Checks {#arming_checks_sub}
|
||||
|
||||
[Arming Checks](#arming_checks_copter) are the same as for copter.
|
||||
|
||||
@@ -44,7 +44,7 @@ You need to rotate the vehicle randomly around all axes until the progress bar f
|
||||
|
||||
This shows you the quality of the calibration for each compass. Using these values you can determine whether you may want to turn off usage of poorly performing compasses.
|
||||
|
||||
## Level Horizon {#level\_horizon}
|
||||
## Level Horizon {#level_horizon}
|
||||
|
||||
If the horizon (as shown in the HUD) is not level after completing accelerometer calibration you can calibrate the level horizon for your vehicle.
|
||||
You will be asked to place the vehicle in a level orientation while it captures the information.
|
||||
@@ -93,7 +93,7 @@ To perform **CompassMot** calibration:
|
||||
|
||||
|
||||
|
||||
## Sensor Settings {#sensor\_settings}
|
||||
## Sensor Settings {#sensor_settings}
|
||||
|
||||
The _Sensor Settings_ section allows you to specify the compass orientation and which compasses are enabled.
|
||||
|
||||
|
||||
@@ -132,7 +132,7 @@ To calibrate the airspeed sensor:
|
||||
|
||||
5. Wait for 2-3 seconds before removing the covering (calibration completes silently after several seconds)
|
||||
|
||||
## Set Orientations {#flight\_controller\_orientation}
|
||||
## Set Orientations {#flight_controller_orientation}
|
||||
|
||||
:::tip
|
||||
You can skip this section if the flight controller and compass are mounted upright on the vehicle and facing the front (this is the default orientation - `ROTATION_NONE`).
|
||||
|
||||
@@ -10,7 +10,7 @@ _Questions_ about how to use _QGroundControl_ should be raised in the discussion
|
||||
|
||||
These forums are also the best place to start discussions on bugs/problems you are having with _QGroundControl_ and or feature requests you would like to make. From there you may be directed to entering information in a GitHub Issue for further resolution.
|
||||
|
||||
### Developer Chat {#developer\_chat}
|
||||
### Developer Chat {#developer_chat}
|
||||
|
||||
_QGroundControl_ developers (and many regular/deeply-involved users) can be found on the [#QGroundControl Slack channel](https://px4.slack.com/).
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ Araç çubuğu, "PlanView" haricindeki tüm ekranlarda aynıdır (sizi "Fly" gö
|
||||
|
||||
## Seç-Görüntüle Simgeler
|
||||
|
||||
Aşağıdaki simgeler ana \_Views \_ arasında geçiş yapmak için kullanılır. Hiçbir araç bağlı olmasa bile bu simgeler ekranda bulunur.
|
||||
Aşağıdaki simgeler ana _Views _ arasında geçiş yapmak için kullanılır. Hiçbir araç bağlı olmasa bile bu simgeler ekranda bulunur.
|
||||
|
||||
 **[Settings](../settings_view/settings_view.md)** <br />_QGroundControl_ uygulamasını düzenleyin.
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ The solution is to set the desired _32-bit voice_ for your system:
|
||||
Additional information about the Windows speech APIs can be found [here](https://www.webbie.org.uk/blog/microsoft-speech/).
|
||||
:::
|
||||
|
||||
## Windows: UI Rendering/Video Driver Issues {#opengl\_troubleshooting}
|
||||
## Windows: UI Rendering/Video Driver Issues {#opengl_troubleshooting}
|
||||
|
||||
If you experience UI rendering issues or video driver crashes on Windows, this may be caused by "flaky" OpenGL drivers. _QGroundControl_ provides 3 shortcuts that you can use to start _QGroundControl_ in "safer" video modes (try these in order):
|
||||
|
||||
@@ -30,7 +30,7 @@ If you experience UI rendering issues or video driver crashes on Windows, this m
|
||||
- **GPU Compatibility Mode:** QGC uses ANGLE drivers, which implement OpenGL on top of DirectX.
|
||||
- **GPU Safe Mode:** QGC uses a software rasterizer for the UI (this is very slow).
|
||||
|
||||
## Windows: Doesn't connect to Vehicle over WiFi {#waiting\_for\_connection}
|
||||
## Windows: Doesn't connect to Vehicle over WiFi {#waiting_for_connection}
|
||||
|
||||
If _QGroundControl_ sits forever (for example, _Waiting For Vehicle Connection_) when trying to connect to the vehicle over Wifi, a possible cause is that IP traffic is being blocked by firewall software (e.g. Windows Defender, Norton, etc.).
|
||||
|
||||
@@ -53,7 +53,7 @@ If using _Windows Defender_:
|
||||
You'll find QGC under **O**: _Open source ground control app provided by QGroundControl dev team_
|
||||
:::
|
||||
|
||||
## Ubuntu: Video Streaming Fails (Missing Gstreamer) {#missing\_gstreamer}
|
||||
## Ubuntu: Video Streaming Fails (Missing Gstreamer) {#missing_gstreamer}
|
||||
|
||||
On Ubuntu you must install _Gstreamer_ components in order to see video streams.
|
||||
If these are not installed _QGroundControl_ is unable to create the gstreamer nodes and fails with:
|
||||
@@ -64,7 +64,7 @@ VideoReceiver::start() failed. Error with gst_element_factory_make(‘avdec_h264
|
||||
|
||||
The [download/install instructions for Ubuntu](../getting_started/download_and_install.md#ubuntu) include _GStreamer_ setup information.
|
||||
|
||||
## Ubuntu 18.04: Video Streaming Fails on Dual Video Adapter Systems {#dual\_vga}
|
||||
## Ubuntu 18.04: Video Streaming Fails on Dual Video Adapter Systems {#dual_vga}
|
||||
|
||||
|
||||
|
||||
@@ -82,7 +82,7 @@ LIBVA_DRIVER_NAME=fakedriver ./QGroundControl) will this make the
|
||||
|
||||
Other alternatives are to disable one of the VGAs, uninstall VA API components, or upgrade to GStreamer 1.16 (there is no easy way to do this on Ubuntu 18.04 - please contribute a recipe if you find one!)
|
||||
|
||||
## Ubuntu 16.04: GLIBC\_2.27 not found {#glibc\_2\_27}
|
||||
## Ubuntu 16.04: GLIBC_2.27 not found {#glibc_2_27}
|
||||
|
||||
The pre-built AppImages for QGroundControl 4.0 (and later) can only run on Ubuntu 18.04 LTS (or later).
|
||||
They do not run on Ubuntu 16.04.
|
||||
|
||||
@@ -11,7 +11,7 @@ The two main areas that are most problematic are:
|
||||
In order for the _QGroundControl_ development team to debug these issues the following information **must be supplied** in any github issue entered against _Resume Mission_.
|
||||
:::
|
||||
|
||||
## Common Steps for Resume Mission Dialog/Generation {#common\_steps}
|
||||
## Common Steps for Resume Mission Dialog/Generation {#common_steps}
|
||||
|
||||
The following steps are required for debugging both types of problems:
|
||||
|
||||
|
||||
@@ -24,4 +24,4 @@ Vehicle类所生成的对象是QGC代码与物理载具通信的主要接口。
|
||||
|
||||
The FirmwarePlugin class is the base class for firmware plugins. FirmwarePlugin类为固件插件的基类。 固件插件包含固件特定代码，因此Vehicle对象相对于它是识别的，支持UI的单个标准接口。
|
||||
|
||||
FirmwarePluginManager是一个工厂类，它根据Vehicle类的成员MAV\_AUTOPILOT / MAV\_TYPE组合创建FirmwarePlugin类的实例。
|
||||
FirmwarePluginManager是一个工厂类，它根据Vehicle类的成员MAV_AUTOPILOT / MAV_TYPE组合创建FirmwarePlugin类的实例。
|
||||
|
||||
@@ -32,12 +32,12 @@ Linux终端：
|
||||
|
||||
| 选项 | 描述 |
|
||||
| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| `--clear-settings` | Clears the app settings (reverts _QGroundControl_ back to default settings). |
|
||||
| `--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. |
|
||||
| `--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. |
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ _QGroundControl_ (QGC) contains a set of unit tests that must pass before a pull
|
||||
|
||||
要运行单元测试：
|
||||
|
||||
1. 使用UNITTEST\_BUILD定义在调试模式下构建。
|
||||
1. 使用UNITTEST_BUILD定义在调试模式下构建。
|
||||
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:
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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_.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Release Process for Custom Builds \[WIP Docs]
|
||||
# Release Process for Custom Builds [WIP Docs]
|
||||
|
||||
One of the trickier aspects of creating your own custom build is the process to keep it up to date with regular QGC. This document describes a suggested process to follow. But in reality you are welcome to use whatever branching and release strategy you want for your custom builds.
|
||||
|
||||
|
||||
@@ -20,6 +20,6 @@
|
||||
- Component-Id（参数的组件编号）
|
||||
- Name参数名称
|
||||
- Value参数值
|
||||
- 使用MAVLink MAV_PARAM\_TYPE_ \*枚举值键入参数类型
|
||||
- 使用MAVLink MAV_PARAM_TYPE_ \*枚举值键入参数类型
|
||||
|
||||
参数文件包含单个Vehicle的参数。 它可以包含该Vehicle中多个组件的参数。 It can contain parameters for multiple components within that Vehicle.
|
||||
|
||||
@@ -82,22 +82,22 @@ 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. |
|
||||
|
||||
简单和复杂项目的格式如下。
|
||||
|
||||
### SimpleItem - 简单的任务项目 {#mission\_simple\_item}
|
||||
### SimpleItem - 简单的任务项目 {#mission_simple_item}
|
||||
|
||||
一个简单的项表示单个MAVLink MISSION\_ITEM命令。
|
||||
一个简单的项表示单个MAVLink MISSION_ITEM命令。
|
||||
|
||||
```
|
||||
{
|
||||
@@ -123,25 +123,25 @@ The list may be a mix of both [SimpleItem](#mission_simple_item) and [ComplexIte
|
||||
|
||||
字段映射如下所示。
|
||||
|
||||
| 键 | 描述 |
|
||||
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| `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）。 |
|
||||
| 键 | 描述 |
|
||||
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `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）。 |
|
||||
|
||||
### 复杂任务项目 {#mission\_complex\_item}
|
||||
### 复杂任务项目 {#mission_complex_item}
|
||||
|
||||
复杂项是对作为单个实体处理的多个MISSION\_ITEM对象的更高级别封装。
|
||||
复杂项是对作为单个实体处理的多个MISSION_ITEM对象的更高级别封装。
|
||||
|
||||
目前有三种类型的复杂任务项目：
|
||||
|
||||
- 调查]\(#survey)
|
||||
- 调查](#survey)
|
||||
- [走廊扫描](#corridor_scan)
|
||||
- [结构扫描](#structure_scan)
|
||||
|
||||
@@ -187,7 +187,7 @@ The list may be a mix of both [SimpleItem](#mission_simple_item) and [ComplexIte
|
||||
| `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. |
|
||||
|
||||
#### 走廊扫描 {#corridor\_scan}
|
||||
#### 走廊扫描 {#corridor_scan}
|
||||
|
||||
CorridorScan复杂任务项的对象定义如下。
|
||||
|
||||
@@ -226,7 +226,7 @@ CorridorScan复杂任务项的对象定义如下。
|
||||
| [`TransectStyleComplexItem `](#TransectStyleComplexItem) | Survey和CorridorScan复杂项目的通用基础定义。 |
|
||||
| `polyline` | ? |
|
||||
|
||||
#### 结构扫描 {#structure\_scan}
|
||||
#### 结构扫描 {#structure_scan}
|
||||
|
||||
StructureScan复杂任务项的对象定义如下。
|
||||
|
||||
@@ -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}
|
||||
|
||||
@@ -390,7 +390,7 @@ The plan can contain an arbitrary number of geofences defined in terms of polygo
|
||||
| [`circles`](#circle_geofence) | 包含圆形地理围栏定义的列表（以逗号分隔）。 |
|
||||
| [`polygon`](#polygon_geofence) | 包含多边形地理围栏定义的列表（以逗号分隔）。 |
|
||||
|
||||
### Circle Geofence (圆形地理围栏) {#circle\_geofence}
|
||||
### Circle Geofence (圆形地理围栏) {#circle_geofence}
|
||||
|
||||
Each circular geofence is defined in a separate item, as shown below (multiple comma-separated items can be defined).
|
||||
The items define the centre and radius of the circle, and whether or not the specific geofence is activated.
|
||||
@@ -408,13 +408,13 @@ 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。 |
|
||||
| 键 | 描述 |
|
||||
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `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}
|
||||
### 多边形地理围栏 {#polygon_geofence}
|
||||
|
||||
Each polygon geofence is defined in a separate item, as shown below (multiple comma-separated items can be defined).
|
||||
The geofence includes a set of points defined with a clockwise winding (i.e. they must enclose an area).
|
||||
@@ -455,7 +455,7 @@ The geofence includes a set of points defined with a clockwise winding (i.e. the
|
||||
| `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）或已禁用。 |
|
||||
|
||||
## 团结积分 {#rally\_points}
|
||||
## 团结积分 {#rally_points}
|
||||
|
||||
Rally point information is optional.
|
||||
The plan can contain an arbitrary number of rally points, each of which has a latitude, longitude, and altitude (above home position).
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
qt_version: 5.15.2
|
||||
qt_version: 6.6.1
|
||||
---
|
||||
|
||||
# Getting Started with Source and Builds
|
||||
@@ -46,29 +46,95 @@ We support Linux builds using a container found on the source tree of the reposi
|
||||
|
||||
### Native Builds
|
||||
|
||||
_QGroundControl_ builds are supported for macOS, Linux, Windows, iOS and Android.
|
||||
_QGroundControl_ uses [Qt](http://www.qt.io) as its cross-platform support library and uses [QtCreator](http://doc.qt.io/qtcreator/index.html) as its default build environment.
|
||||
_QGroundControl_ builds are supported for macOS, Linux, Windows, and Android. Creating a version of QGC for iOS is theoretically possible but is no longer supported as a standard build.
|
||||
_QGroundControl_ uses [Qt](http://www.qt.io) as its cross-platform support library.
|
||||
|
||||
- macOS：v10.11或更高版本
|
||||
- Ubuntu：64位，gcc编译器
|
||||
- **Windows:** Vista or higher, [Visual Studio 2019 compiler](#vs) (64 bit)
|
||||
- iOS：10.0及更高版本
|
||||
- **Android:** Android 5.0 and later.
|
||||
- Standard QGC is built against ndk version 19.
|
||||
- Java JDK 11 is required.
|
||||
- **Qt version:** {{ $frontmatter.qt\_version }} **(only)** <!-- NOTE {{ $frontmatter.qt_version }} is set in the frontmatter above -->
|
||||
The required version of Qt is {{ $frontmatter.qt_version }} **(only)**.
|
||||
|
||||
:::warning
|
||||
**Do not use any other version of Qt!** QGC has been thoroughly tested with the specified version of Qt ({{ $frontmatter.qt\_version }}).
|
||||
There is a significant risk that other Qt versions will inject bugs that affect stability and safety (even if QGC compiles).
|
||||
:::
|
||||
:::warning
|
||||
**Do not use any other version of Qt!** QGC has been thoroughly tested with the specified version of Qt ({{ $frontmatter.qt_version }}).
|
||||
There is a significant risk that other Qt versions will inject bugs that affect stability and safety (even if QGC compiles).
|
||||
:::
|
||||
|
||||
For more information see: [Qt 5 supported platform list](http://doc.qt.io/qt-5/supported-platforms.html).
|
||||
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)
|
||||
- **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.
|
||||
:::
|
||||
|
||||
- - **Video Streaming/Gstreamer:** - see [Video Streaming](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoReceiver/README.md).
|
||||
- **Airmap SDK:** - TBD.
|
||||
|
||||
#### 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:
|
||||
|
||||
- **OSX:** Desktop Qt {{ $frontmatter.qt_version }} clang 64 bit
|
||||
|
||||
::: info
|
||||
iOS builds must be built using [XCode](http://doc.qt.io/qt-5/ios-support.html).
|
||||
:::
|
||||
|
||||
- **Ubuntu:** Desktop Qt {{ $frontmatter.qt_version }} GCC 64bit
|
||||
|
||||
- **Windows:** Desktop Qt {{ $frontmatter.qt_version }} MSVC2019 **64bit**
|
||||
|
||||
- **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_**.
|
||||
|
||||
3. Build using the "hammer" (or "play") icons:
|
||||
|
||||
|
||||
|
||||
#### 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)
|
||||
@@ -81,94 +147,6 @@ When installing, select _Desktop development with C++_ as shown:
|
||||
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.
|
||||
:::
|
||||
|
||||
#### 安装Qt
|
||||
|
||||
You **need to install Qt as described below** instead of using pre-built packages from say, a Linux distribution, because _QGroundControl_ needs access to private Qt headers.
|
||||
|
||||
To install Qt:
|
||||
|
||||
1. 下载并运行[Qt Online Installer](http://www.qt.io/download-open-source)
|
||||
- **Ubuntu:**
|
||||
- 使用以下命令将下载的文件设置为可执行文件：`chmod + x`
|
||||
- 请安装到默认位置, 以便与 **./qgroundcontrol-start.sh** 一起使用。如果将 Qt 安装到非默认位置, 则需要修改 **qgroundcontrol-start.sh** ，才能运行下载的组件。
|
||||
|
||||
2. In the installer _Select Components_ dialog choose: {{ $frontmatter.qt\_version }}.
|
||||
|
||||
::: info
|
||||
If the version needed is not displayed, check the archive (show archive and refresh).
|
||||
:::
|
||||
|
||||
然后，按如下向导，安装组件:
|
||||
|
||||
- **Windows**: _MSVC 2019 64 bit_
|
||||
- **MacOS**: _macOS_
|
||||
- **Linux**: _Desktop gcc 64-bit_
|
||||
- All:
|
||||
- _Qt Charts_ <!-- and *Qt Remote Objects (TP)* -->
|
||||
- _Android ARMv7_ (optional, used to build Android)
|
||||
|
||||
|
||||
|
||||
3. Install Additional Packages (Platform Specific)
|
||||
|
||||
- **Ubuntu:** `sudo apt-get install speech-dispatcher libudev-dev libsdl2-dev patchelf build-essential curl`
|
||||
- **Fedora:** `sudo dnf install speech-dispatcher SDL2-devel SDL2 systemd-devel patchelf`
|
||||
- **Arch Linux:** `pacman -Sy speech-dispatcher patchelf`
|
||||
- **Android:** [Qt Android Setup](http://doc.qt.io/qt-5/androidgs.html)
|
||||
|
||||
::: info
|
||||
JDK11 is required (install if needed)!
|
||||
:::
|
||||
|
||||
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.
|
||||
:::
|
||||
|
||||
- - **Video Streaming/Gstreamer:** - see [Video Streaming](https://github.com/mavlink/qgroundcontrol/blob/master/src/VideoReceiver/README.md).
|
||||
- **Airmap SDK:** - TBD.
|
||||
- **Airmap SDK:** - TBD.
|
||||
|
||||
5. Disable platform-specific optional features that are enabled (but not installed), by default.
|
||||
|
||||
::: info
|
||||
This currently applies to Airmap on Linux, which is optional but enabled by default.
|
||||
:::
|
||||
|
||||
- **Ubuntu:**
|
||||
|
||||
- Airmap: Create a file named **user\_config.pri** (in the repo root directory) containing the text `DEFINES += DISABLE_AIRMAP`.
|
||||
This can be done in a bash terminal using the command:
|
||||
|
||||
```sh
|
||||
This can be done in a bash terminal using the command: `echo -e "DEFINES += DISABLE_AIRMAP\r\n" | tee user_config.pri`
|
||||
```
|
||||
|
||||
#### 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:
|
||||
|
||||
- **OSX:** Desktop Qt {{ $frontmatter.qt\_version }} clang 64 bit
|
||||
|
||||
::: info
|
||||
iOS builds must be built using [XCode](http://doc.qt.io/qt-5/ios-support.html).
|
||||
:::
|
||||
|
||||
- **Ubuntu:** Desktop Qt {{ $frontmatter.qt\_version }} GCC 64bit
|
||||
|
||||
- **Windows:** Desktop Qt {{ $frontmatter.qt\_version }} MSVC2019 **64bit**
|
||||
|
||||
- **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_**.
|
||||
|
||||
3. Build using the "hammer" (or "play") icons:
|
||||
|
||||
|
||||
|
||||
#### Build using qmake on CLI {#qmake}
|
||||
|
||||
Example commands to build a default QGC and run it afterwards:
|
||||
@@ -226,7 +204,6 @@ Example commands to build a default QGC and run it afterwards:
|
||||
### Additional Build Notes for all Supported OS
|
||||
|
||||
- **Parallel builds:** For non Windows builds, you can use the `-j#` option to run parellel builds.
|
||||
- **Location of built files:** Individual build file results can be found in the `build_debug` or `build_release` directories. The built executable can be found in the `debug` or `release` directory.
|
||||
- **If you get this error when running _QGroundControl_**: `/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version 'GLIBCXX_3.4.20' not found.`, you need to either update to the latest _gcc_, or install the latest _libstdc++.6_ using: `sudo apt-get install libstdc++6`.
|
||||
- **Unit tests:** To run the [unit tests](../contribute/unit_tests.md), build in `debug` mode with `UNITTEST_BUILD` definition, and then copy `deploy/qgroundcontrol-start.sh` script into the `debug` directory before running the tests.
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ The current stable build is the highest quality build available for QGC.
|
||||
Stable builds are built from a separate branch that is named with the format: `Stable_VX.Y` (note, there is no patch number!)
|
||||
The branch has one or more git tags for each patch release (with the format `vX.Y.Z`), indicating the point in the repo source code that the associated patch release was created from.
|
||||
|
||||
### Patch Releases {#patch\_releases}
|
||||
### Patch Releases {#patch_releases}
|
||||
|
||||
A patch release contains fixes to the stable release that are important enough to _require_ an update, and are safe enough that the stable release continues to maintain high quality.
|
||||
|
||||
|
||||
@@ -49,7 +49,7 @@
|
||||
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}
|
||||
## 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.
|
||||
|
||||
@@ -81,7 +81,7 @@ The selection list on the top right is used to select a particular telemetry val
|
||||
|
||||
|
||||
|
||||
### Camera {#camera\_instrument\_page}
|
||||
### Camera {#camera_instrument_page}
|
||||
|
||||
The camera page is used to configure and control the camera.
|
||||
|
||||
@@ -103,7 +103,7 @@ Most of the settings that are displayed depend on the camera (they are defined i
|
||||
|
||||
> 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}
|
||||
### 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.
|
||||
@@ -117,7 +117,7 @@ The following sections describe how to perform common operations/tasks in the Fl
|
||||
Many of the available options depend on both the vehicle type and its current state.
|
||||
:::
|
||||
|
||||
### Pre Flight Checklist {#preflight\_checklist}
|
||||
### 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.
|
||||
|
||||
@@ -184,7 +184,7 @@ You will then need to use the disarming slider.
|
||||
|
||||
Disarming the vehicle while it is flying is called an [Emergency Stop](#emergency_stop)
|
||||
|
||||
### 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!
|
||||
@@ -235,7 +235,7 @@ 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}
|
||||
### Change Altitude {#change_altitude}
|
||||
|
||||
You can change altitude while flying, except when in a mission:
|
||||
|
||||
@@ -303,7 +303,7 @@ To pause:
|
||||
|
||||
### Missions
|
||||
|
||||
#### Start Mission {#start\_mission}
|
||||
#### Start Mission {#start_mission}
|
||||
|
||||
You can start a mission when the vehicle is landed (the start mission confirmation slider is often displayed by default).
|
||||
|
||||
@@ -321,7 +321,7 @@ To start a mission from landed:
|
||||
|
||||
|
||||
|
||||
#### Continue Mission {#continue\_mission}
|
||||
#### 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).
|
||||
|
||||
@@ -343,7 +343,7 @@ You can continue the current mission while (unless already in a mission!):
|
||||
|
||||
|
||||
|
||||
#### Resume Mission {#resume\_mission}
|
||||
#### 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).
|
||||
|
||||
@@ -368,12 +368,12 @@ A mission cannot simply resume from the last mission item that the vehicle execu
|
||||
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}
|
||||
#### 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}
|
||||
### 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).
|
||||
|
||||
@@ -36,7 +36,7 @@ It is possible to manually build 32 bit versions (this is not supported by the d
|
||||
|
||||
_QGroundControl_ can be installed on macOS 10.11 or later: <!-- match version using https://dev.qgroundcontrol.com/master/en/getting_started/#native-builds -->
|
||||
|
||||
<!-- match version using https://dev.qgroundcontrol.com/master/en/getting_started/#native-builds -->
|
||||
<!-- match version using https://docs.qgroundcontrol.com/master/en/qgc-dev-guide/getting_started/#native-builds -->
|
||||
|
||||
<!-- usually based on Qt macOS dependency -->
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ That's it! 就这么简单！ 如果设备准备飞行（无人机是飞，其
|
||||
- [Setup](../setup_view/setup_view.md)：配置和调试你的设备。
|
||||
- [Plan](../plan_view/plan_view.md)：创建自主自动执行的任务
|
||||
- [Fly](../fly_view/fly_view.md)：在飞行时监测您的车辆，包括视频流。
|
||||
- \[Analyze] \*\* Description of Analyze view is missing \*\*
|
||||
- [Analyze] \*\* Description of Analyze view is missing \*\*
|
||||
- 点击工具栏上的_Status 图标_来确认已连接设备的状态。
|
||||
|
||||
While the UI is fairly intuitive, this documentation can also be referenced to find out more.
|
||||
|
||||
@@ -5,9 +5,9 @@ The available pattern tools depend on the vehicle (and support for the vehicle-t
|
||||
|
||||
|
||||
|
||||
| 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 |
|
||||
| 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 |
|
||||
| [Fixed Wing Landing](../plan_view/pattern_fixed_wing_landing.md) | Add a landing pattern for fixed wing vehicles to a mission. | Fixed Wing |
|
||||
|
||||
@@ -77,7 +77,7 @@ The configurable options are:
|
||||
- **Relative altitude** - Check to specify a relative altitude. This is only supported for manual grids that are not using [terrain following](#terrain_following).
|
||||
- **Rotate entry point** - Press button to swap the start and end point of the corridor scan.
|
||||
|
||||
### Terrain Following {#terrain\_following}
|
||||
### Terrain Following {#terrain_following}
|
||||
|
||||
By default a flying vehicle will follow the corridor path at a fixed altitude.
|
||||
Enabling _Terrain Following_ makes the vehicle maintain a constant height relative to ground.
|
||||
|
||||
@@ -46,7 +46,7 @@ The list of available cameras (QGC 3.4) is given below.
|
||||
|
||||
|
||||
|
||||
#### Known Camera {#known\_camera}
|
||||
#### Known Camera {#known_camera}
|
||||
|
||||
Selecting a known camera from the option dropdown generates a grid pattern based on the camera capabilities.
|
||||
|
||||
@@ -61,7 +61,7 @@ The default settings can be tuned for your survey using the configuration option
|
||||
- **Altitude** - Survey altitude (ground resolution will be calculated/displayed for this altitude).
|
||||
- **Ground resolution** - Ground resolution for each image (altitude required to achieve this resolution calculated and shown).
|
||||
|
||||
#### Custom Camera {#custom\_camera}
|
||||
#### Custom Camera {#custom_camera}
|
||||
|
||||
Selecting the custom camera option allows you to specify the settings for a new camera in a similar way to a known camera.
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ It is also use to configure the [GeoFence](plan_geofence.md) and [Rally Points](
|
||||
<span id="plan_screenshot"></span>
|
||||
|
||||
|
||||
## UI Overview {#ui\_overview}
|
||||
## UI Overview {#ui_overview}
|
||||
|
||||
The [screenshot above](#plan_screenshot) shows a simple mission plan that starts with a takeoff at the [Planned Home](#planned_home) position (H), flies through three waypoints, and then lands on the last waypoint (i.e. waypoint 3).
|
||||
|
||||
@@ -24,7 +24,7 @@ The main elements of the UI are:
|
||||
|
||||
It shows you information related to the currently selected waypoint as well as statistics for the entire mission.
|
||||
|
||||
## Planning a Mission {#plan\_mission}
|
||||
## Planning a Mission {#plan_mission}
|
||||
|
||||
At very high level, the steps to create a mission are:
|
||||
|
||||
@@ -35,7 +35,7 @@ At very high level, the steps to create a mission are:
|
||||
|
||||
The following sections explain some of the details in the view.
|
||||
|
||||
## Planned Home Position {#planned\_home}
|
||||
## Planned Home Position {#planned_home}
|
||||
|
||||
The _Planned Home_ shown in _Plan View_ is used to set the approximate start point when planning a mission (i.e. when a vehicle may not even be connected to QGC).
|
||||
It is used by QGC to estimate mission times and to draw waypoint lines.
|
||||
@@ -51,7 +51,7 @@ The altitude for the planned home position is set in the [Mission Settings](#mis
|
||||
The Fly View displays the _actual_ home position set by the vehicle firmware when it arms (this is where the vehicle will return in Return/RTL mode).
|
||||
:::
|
||||
|
||||
## Plan Tools {#plan\_tools}
|
||||
## Plan Tools {#plan_tools}
|
||||
|
||||
The plan tools are used for adding individual waypoints, easing mission creation for complicated geometries, uploading/downloading/saving/restoring missions, and for navigating the map. The main tools are described below.
|
||||
|
||||
@@ -86,7 +86,7 @@ The _File tools_ provide the following functionality:
|
||||
|
||||
The [Pattern](Pattern.md) tool simplifies the creation of missions for flying complex geometries, including [surveys](../plan_view/pattern_survey.md) and [structure scans](../plan_view/pattern_structure_scan_v2.md).
|
||||
|
||||
## Mission Command List {#mission\_command\_list}
|
||||
## Mission Command List {#mission_command_list}
|
||||
|
||||
Mission commands for the current mission are listed on the right side of the view.
|
||||
At the top are a set of options to switch between editing the mission, GeoFence and rally points.
|
||||
@@ -94,7 +94,7 @@ Within the list you can select individual mission items to edit their values.
|
||||
|
||||
|
||||
|
||||
### Mission Command Editors {#mission\_command\_editors}
|
||||
### Mission Command Editors {#mission_command_editors}
|
||||
|
||||
Click on a mission command in the list to display its editor (in which you can set/change the command attributes).
|
||||
|
||||
@@ -111,7 +111,7 @@ The list of available commands will depend on firmware and vehicle type.
|
||||
Examples may include: Waypoint, Start image capture, Jump to item (to repeat mission) and other commands.
|
||||
:::
|
||||
|
||||
### Mission Settings {#mission\_settings}
|
||||
### Mission Settings {#mission_settings}
|
||||
|
||||
The _Mission Start_ panel is the first item that appears in the [mission command list](#mission_command_list).
|
||||
It may be used to specify a number default settings that may affect the start or end of the mission.
|
||||
@@ -181,7 +181,7 @@ By specifying this value, total mission or survey times can be approximated even
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Mission (Plan) Upload/Download Failures {#plan\_transfer\_fail}
|
||||
### Mission (Plan) Upload/Download Failures {#plan_transfer_fail}
|
||||
|
||||
Plan uploading and downloading can fail over a noisy communication link (affecting missions, GeoFence, and rally points).
|
||||
If a failure occurs you should see a status message in the QGC UI similar to:
|
||||
|
||||
@@ -80,7 +80,7 @@ This section contains a high level and _non-exhaustive_ list of new features add
|
||||
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.
|
||||
- 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.
|
||||
@@ -137,7 +137,7 @@ This section contains a high level and _non-exhaustive_ list of new features add
|
||||
- **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 HIGH_LATENCY MavLink message.
|
||||
Supports failover back/forth from high latency to normal link with dual link setup.
|
||||
|
||||
## Stable Version 3.3
|
||||
|
||||
@@ -41,7 +41,7 @@ This is now supported from the Sensors page.
|
||||
|
||||
This is now supported from the Copy Trims button on the Radio setup page.
|
||||
|
||||
## Plan View {#plan\_view}
|
||||
## Plan View {#plan_view}
|
||||
|
||||
### Plan Files
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ 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 {#plan\_view}
|
||||
### Plan View {#plan_view}
|
||||
|
||||
#### Structure Scan
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ Click the **Set Logging** button to enable/disable logging information displayed
|
||||
|
||||
The most commmonly used logging options are listed below.
|
||||
|
||||
| Option(s) | Description |
|
||||
| Option(s) | Description |
|
||||
| ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
|
||||
| `LinkManagerLog`, `MultiVehicleManagerLog` | Debug connection problems. |
|
||||
| `LinkManagerVerboseLog` | Debug serial ports not being detected. Very noisy continuous output of available serial ports. |
|
||||
|
||||
@@ -64,7 +64,7 @@ The settings are:
|
||||
|
||||
- <span id="load_save_path"></span>**Application Load/Save Path**: Default location for loading/saving application files, including: parameters, telemetry logs, and mission plans.
|
||||
|
||||
## Data Persistence {#data\_persistence}
|
||||
## Data Persistence {#data_persistence}
|
||||
|
||||
|
||||
|
||||
@@ -72,7 +72,7 @@ The settings are:
|
||||
|
||||
- **Disable all data persistence**: Check to prevent any data being saved or cached: logs, map tiles etc.
|
||||
|
||||
## Telemetry Logs from Vehicle {#telemetry\_logs}
|
||||
## Telemetry Logs from Vehicle {#telemetry_logs}
|
||||
|
||||
|
||||
|
||||
@@ -83,7 +83,7 @@ The settings are:
|
||||
Stops logging when the last vehicle disconnects.
|
||||
- [**CSV Logging**](csv.md): Log subset of telemetry data to a CSV file.
|
||||
|
||||
## Fly View {#fly\_view}
|
||||
## Fly View {#fly_view}
|
||||
|
||||
|
||||
|
||||
@@ -117,7 +117,7 @@ The settings are:
|
||||
|
||||
- **Go To Location Max Distance**: The maximum distance that a Go To location can be set from the current vehicle location (in guided mode).
|
||||
|
||||
## Plan View {#plan\_view}
|
||||
## Plan View {#plan_view}
|
||||
|
||||
|
||||
|
||||
@@ -125,7 +125,7 @@ The settings are:
|
||||
|
||||
- **Default Mission Altitude**: The default altitude used for the Mission Start Panel, and hence for the first waypoint.
|
||||
|
||||
## AutoConnect to the following devices {#auto\_connect}
|
||||
## AutoConnect to the following devices {#auto_connect}
|
||||
|
||||
This section defines the set of devices to which _QGroundControl_ will auto-connect.
|
||||
|
||||
@@ -141,7 +141,7 @@ Settings include:
|
||||
- **RTK GPS:** Autoconnect to RTK GPS device
|
||||
- **NMEA GPS Device:** Autoconnect to an external GPS device to get ground station position ([see below](#nmea_gps))
|
||||
|
||||
### Ground Station Location (NMEA GPS Device) {#nmea\_gps}
|
||||
### Ground Station Location (NMEA GPS Device) {#nmea_gps}
|
||||
|
||||
_QGroundControl_ will automatically use an internal GPS to display its own location on the map with a purple `Q` icon (if the GPS provides a heading, this will be also indicated by the icon).
|
||||
It may also use the GPS as a location source for _Follow Me Mode_ - currently supported on [PX4 Multicopters only](https://docs.px4.io/en/flight_modes/follow_me.html).
|
||||
@@ -173,7 +173,7 @@ Use the _NMEA GPS Device_ drop-down selector to manually select the GPS device a
|
||||
- **NMEA GPS Device:** _UDP Port_.
|
||||
- **NMEA Stream UDP Port**: The UDP port on which QGC will listen for NMEA data (QGC binds the port as a server)
|
||||
|
||||
## RTK GPS {#rtk\_gps}
|
||||
## RTK GPS {#rtk_gps}
|
||||
|
||||
This section allows you to specify the RTK GPS "Survey-in" settings, to save and reuse the result of a Survey-In operation, or to directly enter any other known position for the base station.
|
||||
|
||||
@@ -203,7 +203,7 @@ The settings are:
|
||||
- **Base Position Accuracy:** Accuracy of base station position information.
|
||||
- **Save Current Base Position** (button): Press to copy settings from the last Survey-In operation to the _Use Specified Base Position_ fields above.
|
||||
|
||||
## ADSB Server {#adsb\_server}
|
||||
## ADSB Server {#adsb_server}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ The screen also allows you to manage [MAVLink 2 Log Streaming](#logging) (PX4 on
|
||||
|
||||
|
||||
|
||||
## Ground Station {#ground\_station}
|
||||
## Ground Station {#ground_station}
|
||||
|
||||
This section sets the MAVLink properties and behaviour of _QGroundControl_.
|
||||
|
||||
@@ -23,7 +23,7 @@ This section sets the MAVLink properties and behaviour of _QGroundControl_.
|
||||
Note that this forwarding is one-way: from QGC to the specified host.
|
||||
Any MAVLink messages that are received from the specified host will be ignored.
|
||||
|
||||
## Link Status {#link\_status}
|
||||
## Link Status {#link_status}
|
||||
|
||||
This shows the status of MAVLink message transfer over the communications link.
|
||||
A high **Loss rate** may lead to protocol errors for things like parameter download or mission upload/download.
|
||||
|
||||
@@ -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`](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_.
|
||||
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).
|
||||
@@ -62,12 +62,12 @@ These options may be useful for specific, unsual setups, for increasing sensibil
|
||||
|
||||
|
||||
|
||||
- **Center stick is zero throttle**: Centered or lowered stick sends 0 in [MANUAL\_CONTROL **z**](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL), raised stick sends 1000.
|
||||
- **Center stick is zero throttle**: Centered or lowered stick sends 0 in [MANUAL_CONTROL **z**](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL), raised stick sends 1000.
|
||||
- **Spring loaded throttle smoothing**: In this mode you control not the throttle itself, but the rate at which it increases/decreases.
|
||||
This is useful for setups where the throttle stick is spring loaded, as the user can hold the desired throttle while releasing the stick.
|
||||
- **Full down stick is zero throttle**: In this mode, lowered stick sends 0 in [MANUAL\_CONTROL **z**](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL), centered stick 500, and raised 1000.
|
||||
- **Full down stick is zero throttle**: In this mode, lowered stick sends 0 in [MANUAL_CONTROL **z**](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL), centered stick 500, and raised 1000.
|
||||
- **Allow negative thrust**: When in **Center stick is zero throttle** mode, this allows the user to send negative values by lowering the stick.
|
||||
So that lowered stick sends -1000 in [MANUAL\_CONTROL **z**](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL), centered sends zero, and raised stick sends 1000.
|
||||
So that lowered stick sends -1000 in [MANUAL_CONTROL **z**](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL), centered sends zero, and raised stick sends 1000.
|
||||
This mode is only enabled for vehicles that support negative thrust, such as [Rover](http://ardupilot.org/rover/index.html).
|
||||
|
||||
### Expo
|
||||
@@ -95,11 +95,11 @@ The following settings are available:
|
||||
|
||||
- **Joystick Mode**: Changes what the joystick actually controls, and the MAVLink messages sent to the vehicle.
|
||||
|
||||
- **Normal**: User controls as if using a regular RC radio, MAVLink [MANUAL\_CONTROL](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) messages are used.
|
||||
- **Attitude**: User controls the vehicle attitude, MAVLink [SET\_ATTITUDE\_TARGET](https://mavlink.io/en/messages/common.html#SET_ATTITUDE_TARGET) messages are used.
|
||||
- **Position**: User controls the vehicle position, MAVLink [SET\_POSITION\_TARGET\_LOCAL\_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) messages with bitmask for **position** only are used.
|
||||
- **Force**: User controls the forces applied to the vehicle, MAVLink [SET\_POSITION\_TARGET\_LOCAL\_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) messages with bitmask for **force** only are used.
|
||||
- **Velocity**: User controls the forces applied to the vehicle, MAVLink [SET\_POSITION\_TARGET\_LOCAL\_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) messages with bitmask for **velocity** only are used.
|
||||
- **Normal**: User controls as if using a regular RC radio, MAVLink [MANUAL_CONTROL](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) messages are used.
|
||||
- **Attitude**: User controls the vehicle attitude, MAVLink [SET_ATTITUDE_TARGET](https://mavlink.io/en/messages/common.html#SET_ATTITUDE_TARGET) messages are used.
|
||||
- **Position**: User controls the vehicle position, MAVLink [SET_POSITION_TARGET_LOCAL_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) messages with bitmask for **position** only are used.
|
||||
- **Force**: User controls the forces applied to the vehicle, MAVLink [SET_POSITION_TARGET_LOCAL_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) messages with bitmask for **force** only are used.
|
||||
- **Velocity**: User controls the forces applied to the vehicle, MAVLink [SET_POSITION_TARGET_LOCAL_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED) messages with bitmask for **velocity** only are used.
|
||||
|
||||
- **Axis Frequency**: When the joystick is idle (inputs are not changing), the joystick commands are sent to the vehicle at 5Hz. When the joystick is in use (input values are changing), the joystick commands are sent to the vehicle at the (higher) frequency configured by this setting. The default is 25Hz.
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ The Copter safety page is shown below.
|
||||
For additional safety settings and information see: [Failsafe](http://ardupilot.org/copter/docs/failsafe-landing-page.html).
|
||||
:::
|
||||
|
||||
### Battery Failsafe {#battery\_failsafe\_copter}
|
||||
### Battery Failsafe {#battery_failsafe_copter}
|
||||
|
||||
This panel sets the [Battery Failsafe](http://ardupilot.org/copter/docs/failsafe-battery.html) parameters.
|
||||
You can set low and critical thresholds for voltage and/or remaining capacity and define the action if the failsafe value is breached.
|
||||
@@ -34,14 +34,14 @@ If there is a second battery (enabled in the [Power Setup](../setup_view/power.m
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- **Low action** ([BATT\_FS\_LOW\_ACT](http://ardupilot.org/copter/docs/parameters.html#batt-fs-low-act-low-battery-failsafe-action)) - Select one of: None, Land, RTL, SmartRTL, SmartRTL or Land, Terminate.
|
||||
- **Critical action** ([BATT\_FS\_CRT\_ACT](http://ardupilot.org/copter/docs/parameters.html#batt-fs-crt-act-critical-battery-failsafe-action)) - Select one of: None, Land, RTL, SmartRTL, SmartRTL or Land, Terminate.
|
||||
- **Low voltage threshold** ([BATT\_LOW\_VOLT](http://ardupilot.org/copter/docs/parameters.html#batt-low-volt-low-battery-voltage)) - Battery voltage that triggers the _low action_.
|
||||
- **Critical voltage threshold** ([BATT\_CRT\_VOLT](http://ardupilot.org/copter/docs/parameters.html#batt-crt-volt-critical-battery-voltage))- Battery voltage that triggers the _critical action_.
|
||||
- **Low mAh threshold** ([BATT\_LOW\_MAH](http://ardupilot.org/copter/docs/parameters.html#batt-low-mah-low-battery-capacity)) - Battery capacity that triggers the _low action_.
|
||||
- **Critical mAh threshold** ([BATT\_CRT\_MAH](http://ardupilot.org/copter/docs/parameters.html#batt-crt-mah-battery-critical-capacity)) - Battery capacity that triggers the _critical action_.
|
||||
- **Low action** ([BATT_FS_LOW_ACT](http://ardupilot.org/copter/docs/parameters.html#batt-fs-low-act-low-battery-failsafe-action)) - Select one of: None, Land, RTL, SmartRTL, SmartRTL or Land, Terminate.
|
||||
- **Critical action** ([BATT_FS_CRT_ACT](http://ardupilot.org/copter/docs/parameters.html#batt-fs-crt-act-critical-battery-failsafe-action)) - Select one of: None, Land, RTL, SmartRTL, SmartRTL or Land, Terminate.
|
||||
- **Low voltage threshold** ([BATT_LOW_VOLT](http://ardupilot.org/copter/docs/parameters.html#batt-low-volt-low-battery-voltage)) - Battery voltage that triggers the _low action_.
|
||||
- **Critical voltage threshold** ([BATT_CRT_VOLT](http://ardupilot.org/copter/docs/parameters.html#batt-crt-volt-critical-battery-voltage))- Battery voltage that triggers the _critical action_.
|
||||
- **Low mAh threshold** ([BATT_LOW_MAH](http://ardupilot.org/copter/docs/parameters.html#batt-low-mah-low-battery-capacity)) - Battery capacity that triggers the _low action_.
|
||||
- **Critical mAh threshold** ([BATT_CRT_MAH](http://ardupilot.org/copter/docs/parameters.html#batt-crt-mah-battery-critical-capacity)) - Battery capacity that triggers the _critical action_.
|
||||
|
||||
### General Failsafe Triggers {#failsafe\_triggers\_copter}
|
||||
### General Failsafe Triggers {#failsafe_triggers_copter}
|
||||
|
||||
This panel enables the [GCS Failsafe](http://ardupilot.org/copter/docs/gcs-failsafe.html) and enables/configures the throttle failsafe.
|
||||
|
||||
@@ -51,9 +51,9 @@ The configuration options are:
|
||||
|
||||
- **Ground Station failsafe** - Disabled, Enabled always RTL, Enabled Continue with Mission in Auto Mode, Enabled Always SmartRTL or RTL, Enabled Always SmartRTL or Land.
|
||||
- **Throttle failsafe** - Disabled, Always RTL, Continue with Mission in Auto Mode, Always land.
|
||||
- **PWM Threshold** ([FS\_THR\_VALUE](http://ardupilot.org/copter/docs/parameters.html#fs-thr-value-throttle-failsafe-value)) - PWM value below which throttle failsafe triggers.
|
||||
- **PWM Threshold** ([FS_THR_VALUE](http://ardupilot.org/copter/docs/parameters.html#fs-thr-value-throttle-failsafe-value)) - PWM value below which throttle failsafe triggers.
|
||||
|
||||
### Geofence {#geofence\_copter}
|
||||
### Geofence {#geofence_copter}
|
||||
|
||||
This panel sets the parameters for the cylindrical [Simple Geofence](http://ardupilot.org/copter/docs/ac2_simple_geofence.html).
|
||||
You can set whether the fence radius or height are enabled, the maximum values for causing a breach, and the action in the event of a breach.
|
||||
@@ -62,15 +62,15 @@ You can set whether the fence radius or height are enabled, the maximum values f
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- **Circle GeoFence enabled** ([FENCE\_TYPE](http://ardupilot.org/copter/docs/parameters.html#fence-type-fence-type), [FENCE\_ENABLE](http://ardupilot.org/copter/docs/parameters.html#fence-enable-fence-enable-disable)) - Enable the circular geofence.
|
||||
- **Altitude GeoFence enabled** ([FENCE\_TYPE](http://ardupilot.org/copter/docs/parameters.html#fence-type-fence-type), [FENCE\_ENABLE](http://ardupilot.org/copter/docs/parameters.html#fence-enable-fence-enable-disable)) - Enable altitude geofence.
|
||||
- Fence action ([FENCE\_ACTION](http://ardupilot.org/copter/docs/parameters.html#fence-action-fence-action)) One of:
|
||||
- **Circle GeoFence enabled** ([FENCE_TYPE](http://ardupilot.org/copter/docs/parameters.html#fence-type-fence-type), [FENCE_ENABLE](http://ardupilot.org/copter/docs/parameters.html#fence-enable-fence-enable-disable)) - Enable the circular geofence.
|
||||
- **Altitude GeoFence enabled** ([FENCE_TYPE](http://ardupilot.org/copter/docs/parameters.html#fence-type-fence-type), [FENCE_ENABLE](http://ardupilot.org/copter/docs/parameters.html#fence-enable-fence-enable-disable)) - Enable altitude geofence.
|
||||
- Fence action ([FENCE_ACTION](http://ardupilot.org/copter/docs/parameters.html#fence-action-fence-action)) One of:
|
||||
- **Report only** - Report fence breach.
|
||||
- **RTL or Land** - RTL or land on fence breach.
|
||||
- **Max radius** ([FENCE\_RADIUS](http://ardupilot.org/copter/docs/parameters.html#fence-radius-circular-fence-radius)) - Circular fence radius that when broken causes RTL.
|
||||
- **Max altitude** ([FENCE\_ALT\_MAX](http://ardupilot.org/copter/docs/parameters.html#fence-alt-max-fence-maximum-altitude))- Fence maximum altitude to trigger altitude geofence.
|
||||
- **Max radius** ([FENCE_RADIUS](http://ardupilot.org/copter/docs/parameters.html#fence-radius-circular-fence-radius)) - Circular fence radius that when broken causes RTL.
|
||||
- **Max altitude** ([FENCE_ALT_MAX](http://ardupilot.org/copter/docs/parameters.html#fence-alt-max-fence-maximum-altitude))- Fence maximum altitude to trigger altitude geofence.
|
||||
|
||||
### Return to Launch {#rtl\_copter}
|
||||
### Return to Launch {#rtl_copter}
|
||||
|
||||
This panel sets the [RTL Mode](http://ardupilot.org/copter/docs/rtl-mode.html) behaviour.
|
||||
|
||||
@@ -78,15 +78,15 @@ This panel sets the [RTL Mode](http://ardupilot.org/copter/docs/rtl-mode.html) b
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- Select RTL return altitude ([RTL\_ALT](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-rtl-altitude)):
|
||||
- Select RTL return altitude ([RTL_ALT](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-rtl-altitude)):
|
||||
- **Return at current altitude** - Return at current altitude.
|
||||
- **Return at specified altitude** - Ascend to specified altitude to return if below current altitude.
|
||||
- **Loiter above home for** ([RTL\_LOIT\_TIME](http://ardupilot.org/copter/docs/parameters.html#rtl-loit-time-rtl-loiter-time)) - Check to set a loiter time before landing.
|
||||
- **Loiter above home for** ([RTL_LOIT_TIME](http://ardupilot.org/copter/docs/parameters.html#rtl-loit-time-rtl-loiter-time)) - Check to set a loiter time before landing.
|
||||
- One of
|
||||
- **Land with descent speed** ([LAND\_SPEED](http://ardupilot.org/copter/docs/parameters.html#land-speed-land-speed)) - Select final descent speed.
|
||||
- **Final loiter altitude** ([RTL\_ALT\_FINAL](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-final-rtl-final-altitude)) - Select and set final altitude for landing after RTL or mission (set to 0 to land).
|
||||
- **Land with descent speed** ([LAND_SPEED](http://ardupilot.org/copter/docs/parameters.html#land-speed-land-speed)) - Select final descent speed.
|
||||
- **Final loiter altitude** ([RTL_ALT_FINAL](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-final-rtl-final-altitude)) - Select and set final altitude for landing after RTL or mission (set to 0 to land).
|
||||
|
||||
### Arming Checks {#arming\_checks\_copter}
|
||||
### Arming Checks {#arming_checks_copter}
|
||||
|
||||
This panel sets which [Pre-ARM Safety Checks](http://ardupilot.org/copter/docs/prearm_safety_check.html) are enabled.
|
||||
|
||||
@@ -94,7 +94,7 @@ This panel sets which [Pre-ARM Safety Checks](http://ardupilot.org/copter/docs/p
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- **Arming Checks to perform** ([ARMING\_CHECK](http://ardupilot.org/copter/docs/parameters.html#arming-check-arm-checks-to-peform-bitmask)) - Check all appropriate: Barometer, Compass, GPS lock, INS, Parameters, RC Channels, Board voltage, Battery Level, Airspeed, Logging Available, Hardware safety switch, GPS Configuration, System.
|
||||
- **Arming Checks to perform** ([ARMING_CHECK](http://ardupilot.org/copter/docs/parameters.html#arming-check-arm-checks-to-peform-bitmask)) - Check all appropriate: Barometer, Compass, GPS lock, INS, Parameters, RC Channels, Board voltage, Battery Level, Airspeed, Logging Available, Hardware safety switch, GPS Configuration, System.
|
||||
|
||||
## Plane
|
||||
|
||||
@@ -106,13 +106,13 @@ The Plane safety page is shown below.
|
||||
For additional safety settings and information see: [Plane Failsafe Function](http://ardupilot.org/plane/docs/apms-failsafe-function.html) and [Advanced Failsafe Configuration](http://ardupilot.org/plane/docs/advanced-failsafe-configuration.html).
|
||||
:::
|
||||
|
||||
### Battery Failsafe {#battery\_failsafe\_plane}
|
||||
### Battery Failsafe {#battery_failsafe_plane}
|
||||
|
||||
The plane battery failsafe is the same as for copter except there are different options for the [Low](http://ardupilot.org/plane/docs/parameters.html#batt-fs-low-act-low-battery-failsafe-action) and [Critical](http://ardupilot.org/plane/docs/parameters.html#batt-fs-crt-act-critical-battery-failsafe-action) actions: None, RTL, Land, Terminate.
|
||||
|
||||
For more information see: [battery failsafe](#battery_failsafe_copter) (copter).
|
||||
|
||||
### Failsafe Triggers {#failsafe\_triggers\_plane}
|
||||
### Failsafe Triggers {#failsafe_triggers_plane}
|
||||
|
||||
This panel enables the [GCS Failsafe](http://ardupilot.org/plane/docs/advanced-failsafe-configuration.html#ground-station-communications-loss) and enables/configures the throttle failsafe.
|
||||
|
||||
@@ -120,10 +120,10 @@ This panel enables the [GCS Failsafe](http://ardupilot.org/plane/docs/advanced-f
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- **Throttle PWM threshold** ([THR\_FS\_VALUE](http://ardupilot.org/plane/docs/parameters.html#thr-fs-value-throttle-failsafe-value)) - PWM value below which throttle failsafe triggers.
|
||||
- **GCS failsafe** ([FS\_GCS\_ENABL](http://ardupilot.org/plane/docs/parameters.html#fs-gcs-enabl-gcs-failsafe-enable)) - Check to enable GCS failsafe.
|
||||
- **Throttle PWM threshold** ([THR_FS_VALUE](http://ardupilot.org/plane/docs/parameters.html#thr-fs-value-throttle-failsafe-value)) - PWM value below which throttle failsafe triggers.
|
||||
- **GCS failsafe** ([FS_GCS_ENABL](http://ardupilot.org/plane/docs/parameters.html#fs-gcs-enabl-gcs-failsafe-enable)) - Check to enable GCS failsafe.
|
||||
|
||||
### Return to Launch {#rtl\_plane}
|
||||
### Return to Launch {#rtl_plane}
|
||||
|
||||
This panel sets the [RTL Mode](http://ardupilot.org/copter/docs/rtl-mode.html) behaviour.
|
||||
|
||||
@@ -131,11 +131,11 @@ This panel sets the [RTL Mode](http://ardupilot.org/copter/docs/rtl-mode.html) b
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- Select RTL return altitude ([RTL\_ALT](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-rtl-altitude)):
|
||||
- Select RTL return altitude ([RTL_ALT](http://ardupilot.org/copter/docs/parameters.html#rtl-alt-rtl-altitude)):
|
||||
- **Return at current altitude** - Return at current altitude.
|
||||
- **Return at specified altitude** - Ascend to specified altitude to return if below current altitude.
|
||||
|
||||
### Arming Checks {#arming\_checks\_plane}
|
||||
### Arming Checks {#arming_checks_plane}
|
||||
|
||||
[Arming Checks](#arming_checks_copter) are the same as for copter.
|
||||
|
||||
@@ -149,11 +149,11 @@ The Rover safety page is shown below.
|
||||
For additional safety settings and information see: [Failsafes](http://ardupilot.org/rover/docs/rover-failsafes.html).
|
||||
:::
|
||||
|
||||
### Battery Failsafe {#battery\_failsafe\_rover}
|
||||
### Battery Failsafe {#battery_failsafe_rover}
|
||||
|
||||
The rover battery failsafe is the same as for [copter](#battery_failsafe_copter).
|
||||
|
||||
### Failsafe Triggers {#failsafe\_triggers\_rover}
|
||||
### Failsafe Triggers {#failsafe_triggers_rover}
|
||||
|
||||
This panel enables the rover [Failsafes](http://ardupilot.org/rover/docs/rover-failsafes.html).
|
||||
|
||||
@@ -161,12 +161,12 @@ This panel enables the rover [Failsafes](http://ardupilot.org/rover/docs/rover-f
|
||||
|
||||
The configuration options are:
|
||||
|
||||
- **Ground Station failsafe** ([FS\_GCS\_ENABL](http://ardupilot.org/rover/docs/parameters.html#fs-gcs-enable-gcs-failsafe-enable)) - Check to enable GCS failsafe.
|
||||
- **Throttle failsafe** ([FS\_THR\_ENABLE](http://ardupilot.org/rover/docs/parameters.html#fs-thr-enable-throttle-failsafe-enable)) - Enable/disable throttle failsafe (value is _PWM threshold_ below).
|
||||
- **PWM threshold** ([FS\_THR\_VALUE](http://ardupilot.org/rover/docs/parameters.html#fs-thr-value-throttle-failsafe-value)) - PWM value below which throttle failsafe triggers.
|
||||
- **Failsafe Crash Check** ([FS\_CRASH\_CHECK](http://ardupilot.org/rover/docs/parameters.html#fs-crash-check-crash-check-action)) - What to do in the event of a crash: Disabled, Hold, HoldAndDisarm
|
||||
- **Ground Station failsafe** ([FS_GCS_ENABL](http://ardupilot.org/rover/docs/parameters.html#fs-gcs-enable-gcs-failsafe-enable)) - Check to enable GCS failsafe.
|
||||
- **Throttle failsafe** ([FS_THR_ENABLE](http://ardupilot.org/rover/docs/parameters.html#fs-thr-enable-throttle-failsafe-enable)) - Enable/disable throttle failsafe (value is _PWM threshold_ below).
|
||||
- **PWM threshold** ([FS_THR_VALUE](http://ardupilot.org/rover/docs/parameters.html#fs-thr-value-throttle-failsafe-value)) - PWM value below which throttle failsafe triggers.
|
||||
- **Failsafe Crash Check** ([FS_CRASH_CHECK](http://ardupilot.org/rover/docs/parameters.html#fs-crash-check-crash-check-action)) - What to do in the event of a crash: Disabled, Hold, HoldAndDisarm
|
||||
|
||||
### Arming Checks {#arming\_checks\_rover}
|
||||
### Arming Checks {#arming_checks_rover}
|
||||
|
||||
[Arming Checks](#arming_checks_copter) are the same as for copter.
|
||||
|
||||
@@ -180,7 +180,7 @@ The Sub safety page is shown below.
|
||||
For additional safety settings and information see: [Failsafes](https://www.ardusub.com/operators-manual/failsafes.html).
|
||||
:::
|
||||
|
||||
### Failsafe Actions {#failsafe\_actions\_sub}
|
||||
### Failsafe Actions {#failsafe_actions_sub}
|
||||
|
||||
The configuration options are:
|
||||
|
||||
@@ -194,6 +194,6 @@ The configuration options are:
|
||||
- **Internal Temperature** - Select one of: Disabled, Warn only.
|
||||
- **Internal Pressure** - Select one of: Disabled, Warn only.
|
||||
|
||||
### Arming Checks {#arming\_checks\_sub}
|
||||
### Arming Checks {#arming_checks_sub}
|
||||
|
||||
[Arming Checks](#arming_checks_copter) are the same as for copter.
|
||||
|
||||
@@ -44,7 +44,7 @@ You need to rotate the vehicle randomly around all axes until the progress bar f
|
||||
|
||||
This shows you the quality of the calibration for each compass. Using these values you can determine whether you may want to turn off usage of poorly performing compasses.
|
||||
|
||||
## Level Horizon {#level\_horizon}
|
||||
## Level Horizon {#level_horizon}
|
||||
|
||||
If the horizon (as shown in the HUD) is not level after completing accelerometer calibration you can calibrate the level horizon for your vehicle.
|
||||
You will be asked to place the vehicle in a level orientation while it captures the information.
|
||||
@@ -93,7 +93,7 @@ To perform **CompassMot** calibration:
|
||||
|
||||
|
||||
|
||||
## Sensor Settings {#sensor\_settings}
|
||||
## Sensor Settings {#sensor_settings}
|
||||
|
||||
The _Sensor Settings_ section allows you to specify the compass orientation and which compasses are enabled.
|
||||
|
||||
|
||||
@@ -132,7 +132,7 @@ To calibrate the airspeed sensor:
|
||||
|
||||
5. Wait for 2-3 seconds before removing the covering (calibration completes silently after several seconds)
|
||||
|
||||
## Set Orientations {#flight\_controller\_orientation}
|
||||
## Set Orientations {#flight_controller_orientation}
|
||||
|
||||
:::tip
|
||||
You can skip this section if the flight controller and compass are mounted upright on the vehicle and facing the front (this is the default orientation - `ROTATION_NONE`).
|
||||
|
||||
@@ -10,7 +10,7 @@ _Questions_ about how to use _QGroundControl_ should be raised in the discussion
|
||||
|
||||
These forums are also the best place to start discussions on bugs/problems you are having with _QGroundControl_ and or feature requests you would like to make. From there you may be directed to entering information in a GitHub Issue for further resolution.
|
||||
|
||||
### Developer Chat {#developer\_chat}
|
||||
### Developer Chat {#developer_chat}
|
||||
|
||||
_QGroundControl_ developers (and many regular/deeply-involved users) can be found on the [#QGroundControl Slack channel](https://px4.slack.com/).
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ The solution is to set the desired _32-bit voice_ for your system:
|
||||
Additional information about the Windows speech APIs can be found [here](https://www.webbie.org.uk/blog/microsoft-speech/).
|
||||
:::
|
||||
|
||||
## Windows: UI Rendering/Video Driver Issues {#opengl\_troubleshooting}
|
||||
## Windows: UI Rendering/Video Driver Issues {#opengl_troubleshooting}
|
||||
|
||||
If you experience UI rendering issues or video driver crashes on Windows, this may be caused by "flaky" OpenGL drivers. _QGroundControl_ provides 3 shortcuts that you can use to start _QGroundControl_ in "safer" video modes (try these in order):
|
||||
|
||||
@@ -30,7 +30,7 @@ If you experience UI rendering issues or video driver crashes on Windows, this m
|
||||
- **GPU Compatibility Mode:** QGC uses ANGLE drivers, which implement OpenGL on top of DirectX.
|
||||
- **GPU Safe Mode:** QGC uses a software rasterizer for the UI (this is very slow).
|
||||
|
||||
## Windows: Doesn't connect to Vehicle over WiFi {#waiting\_for\_connection}
|
||||
## Windows: Doesn't connect to Vehicle over WiFi {#waiting_for_connection}
|
||||
|
||||
If _QGroundControl_ sits forever (for example, _Waiting For Vehicle Connection_) when trying to connect to the vehicle over Wifi, a possible cause is that IP traffic is being blocked by firewall software (e.g. Windows Defender, Norton, etc.).
|
||||
|
||||
@@ -53,7 +53,7 @@ If using _Windows Defender_:
|
||||
You'll find QGC under **O**: _Open source ground control app provided by QGroundControl dev team_
|
||||
:::
|
||||
|
||||
## Ubuntu: Video Streaming Fails (Missing Gstreamer) {#missing\_gstreamer}
|
||||
## Ubuntu: Video Streaming Fails (Missing Gstreamer) {#missing_gstreamer}
|
||||
|
||||
On Ubuntu you must install _Gstreamer_ components in order to see video streams.
|
||||
If these are not installed _QGroundControl_ is unable to create the gstreamer nodes and fails with:
|
||||
@@ -64,7 +64,7 @@ VideoReceiver::start() failed. Error with gst_element_factory_make(‘avdec_h264
|
||||
|
||||
The [download/install instructions for Ubuntu](../getting_started/download_and_install.md#ubuntu) include _GStreamer_ setup information.
|
||||
|
||||
## Ubuntu 18.04: Video Streaming Fails on Dual Video Adapter Systems {#dual\_vga}
|
||||
## Ubuntu 18.04: Video Streaming Fails on Dual Video Adapter Systems {#dual_vga}
|
||||
|
||||
|
||||
|
||||
@@ -82,7 +82,7 @@ LIBVA_DRIVER_NAME=fakedriver ./QGroundControl) will this make the
|
||||
|
||||
Other alternatives are to disable one of the VGAs, uninstall VA API components, or upgrade to GStreamer 1.16 (there is no easy way to do this on Ubuntu 18.04 - please contribute a recipe if you find one!)
|
||||
|
||||
## Ubuntu 16.04: GLIBC\_2.27 not found {#glibc\_2\_27}
|
||||
## Ubuntu 16.04: GLIBC_2.27 not found {#glibc_2_27}
|
||||
|
||||
The pre-built AppImages for QGroundControl 4.0 (and later) can only run on Ubuntu 18.04 LTS (or later).
|
||||
They do not run on Ubuntu 16.04.
|
||||
|
||||
@@ -11,7 +11,7 @@ The two main areas that are most problematic are:
|
||||
In order for the _QGroundControl_ development team to debug these issues the following information **must be supplied** in any github issue entered against _Resume Mission_.
|
||||
:::
|
||||
|
||||
## Common Steps for Resume Mission Dialog/Generation {#common\_steps}
|
||||
## Common Steps for Resume Mission Dialog/Generation {#common_steps}
|
||||
|
||||
The following steps are required for debugging both types of problems:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user