Skip to content

Commit bdb8161

Browse files
authored
New Crowdin updates (#706)
1 parent 52def97 commit bdb8161

6 files changed

Lines changed: 82 additions & 96 deletions

File tree

ko/messages/common.md

Lines changed: 27 additions & 27 deletions
Large diffs are not rendered by default.

ko/messages/development.md

Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -113,16 +113,16 @@ Static/invariant battery information is sent in [BATTERY_INFO](#BATTERY_INFO).
113113
Note that smart batteries should set the [MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL](#MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL) bit to indicate that supplied capacity values are relative to a battery that is known to be full.
114114
Power monitors would not set this bit, indicating that capacity_consumed is relative to drone power-on, and that other values are estimated based on the assumption that the battery was full on power-on.
115115

116-
| Field Name | Type | Units | Values | Description |
117-
| --------------------------------------- | ---------- | ----- | -------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
118-
| id | `uint8_t` | | | Battery ID<br>[Instance field]: Uniquely identifies a device/subcomponent within a single source/target MAVLink component. |
119-
| temperature | `int16_t` | cdegC | invalid:INT16_MAX | Temperature of the whole battery pack (not internal electronics). INT16_MAX field not provided. |
120-
| voltage | `float` | V | invalid:NaN | Battery voltage (total). NaN: field not provided. |
121-
| current | `float` | A | invalid:NaN | Battery current (through all cells/loads). Positive value when discharging and negative if charging. NaN: field not provided. |
122-
| capacity_consumed | `float` | Ah | invalid:NaN | Consumed charge. NaN: field not provided. This is either the consumption since power-on or since the battery was full, depending on the value of [MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL](#MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL). |
123-
| capacity_remaining | `float` | Ah | invalid:NaN | Remaining charge (until empty). NaN: field not provided. Note: If [MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL](#MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL) is unset, this value is based on the assumption the battery was full when the system was powered. |
124-
| percent_remaining | `uint8_t` | % | invalid:UINT8_MAX | Remaining battery energy. Values: [0-100], UINT8_MAX: field not provided. |
125-
| status_flags | `uint32_t` | | [MAV_BATTERY_STATUS_FLAGS](#MAV_BATTERY_STATUS_FLAGS) | Fault, health, readiness, and other status indications. |
116+
| Field Name | Type | Units | Values | Description |
117+
| --------------------------------------------------------- | ---------- | ----- | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
118+
| id | `uint8_t` | | | Battery ID<br>[Instance field]: Uniquely identifies a device/subcomponent within a single source/target MAVLink component. |
119+
| temperature | `int16_t` | cdegC | invalid:INT16_MAX | Temperature of the whole battery pack (not internal electronics). INT16_MAX field not provided. |
120+
| voltage | `float` | V | invalid:NaN | Battery voltage (total). NaN: field not provided. |
121+
| current | `float` | A | invalid:NaN | Battery current (through all cells/loads). Positive value when discharging and negative if charging. NaN: field not provided. |
122+
| capacity_consumed | `float` | Ah | invalid:NaN | Consumed charge. NaN: field not provided. This is either the consumption since power-on or since the battery was full, depending on the value of [MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL](#MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL). |
123+
| capacity_remaining | `float` | Ah | invalid:NaN | Remaining charge (until empty). NaN: field not provided. Note: If [MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL](#MAV_BATTERY_STATUS_FLAGS_CAPACITY_RELATIVE_TO_FULL) is unset, this value is based on the assumption the battery was full when the system was powered. |
124+
| state_of_charge | `float` | % | invalid:NaN | State of Charge (SoC). Remaining capacity relative to current fully-charged capacity as a percentage. Values: [0-100], NaN: field not provided. Note that the value may be calculated from design_capacity if current full_charge_capacity is not known (see [BATTERY_INFO](#BATTERY_INFO)). |
125+
| status_flags | `uint32_t` | | [MAV_BATTERY_STATUS_FLAGS](#MAV_BATTERY_STATUS_FLAGS) | Fault, health, readiness, and other status indications. |
126126

127127
### GROUP_START (414) — [WIP] {#GROUP_START}
128128

@@ -652,7 +652,6 @@ See https://mavlink.io/en/services/opendroneid.html for more information.
652652
| 3 | | |
653653
| 4 | Empty | |
654654
| 5 | Empty | |
655-
| 5 | Empty | |
656655
| 6 | Empty | |
657656
| 7 | Empty | |
658657

ko/services/mission.md

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -429,10 +429,10 @@ The remaining parameters (xtrack and heading) apply only to forward flying aircr
429429

430430
Xtrack and heading define the location at which a forward flying (fixed wing) vehicle will _exit the loiter circle, and its path to the next waypoint_ (these apply only to `MAV_CMD_NAV_LOITER_TIME` and `MAV_CMD_NAV_LOITER_TURNS`).
431431

432-
| Param (:Label) | Description | Units |
433-
| ------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
434-
| 2: Heading Required | Leave loiter circle only once heading towards the next waypoint (0 = False) | min:0 max:1 increment:1 |
435-
| 4: Xtrack Location | Sets xtrack path or exit location: 0 for the vehicle to converge towards the center xtrack when it leaves the loiter (the line between the centers of the current and next waypoint), 1 to converge to the direct line between the location that the vehicle exits the loiter radius and the next waypoint. Otherwise the angle (in degrees) between the tangent of the loiter circle and the center xtrack at which the vehicle must leave the loiter (and converge to the center xtrack). NaN to use the current system default xtrack behaviour. | |
432+
| Param (:Label) | Description | Units |
433+
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------- |
434+
| 2: Heading Required | Leave loiter circle only once heading towards the next waypoint (0 = False) | min:0 max:1 increment:1 |
435+
| 4: Xtrack Location | Sets xtrack path or exit location: `0` for the vehicle to converge towards the center xtrack when it leaves the loiter (the line between the centers of the current and next waypoint), `1` to converge to the direct line between the location that the vehicle exits the loiter radius and the next waypoint. NaN to use the current system default xtrack behaviour. | |
436436

437437
The recommended values (and resulting paths) are those shown below.
438438

@@ -457,12 +457,6 @@ The Xtrack parameter independently defines the path and exit location:
457457
- `xtrack=NaN`: Exit the loiter using "system specific default behaviour".
458458
- The vehicle must still respect the heading required param.
459459
- Usually this is synonymous with `xtrack=0`
460-
- `xtrack=any other value`: Exit the loiter when the vehicle heading (tangent) makes the specified angle in degrees to the center xtrack.
461-
Converge to the center xtrack.
462-
The vehicle must still respect the `heading required` param (some xtrack values may not be possible with this condition true).
463-
This allows callers to specify how quickly the vehicle converges to the center xtrack. For example, the image below shows the vehicle exiting the loiter at 30 degrees.
464-
465-
![Loiter angle](../../assets/protocols/mission_loiter/xtrack_30.png)
466460

467461
## 구현
468462

0 commit comments

Comments
 (0)