mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-04-14 10:07:39 +08:00
New Crowdin translations - zh-CN
This commit is contained in:
Crowdin Bot
Hamish Willee
parent
5bb183afde
commit
f180cf8b03
@ -320,6 +320,7 @@
|
||||
- [数传电台](telemetry/index.md)
|
||||
- [SiK 电台](telemetry/sik_radio.md)
|
||||
- [RFD900 (SiK) 数传电台](telemetry/rfd900_telemetry.md)
|
||||
- [ThunderFly TFSIK01 Telemetry Radio](telemetry/tfsik_telemetry.md)
|
||||
- [HolyBro (SIK) 数传电台](telemetry/holybro_sik_radio.md)
|
||||
- [WiFi 数传](telemetry/telemetry_wifi.md)
|
||||
- [ESP8266 WiFi 模块](telemetry/esp8266_wifi_module.md)
|
||||
|
||||
@ -10,4 +10,4 @@
|
||||
|
||||
## See Also
|
||||
|
||||
- [外设](../peripherals/index.md) - 包括非核心执行器，如夹具， 降落伞等。
|
||||
- [外设](../peripherals/index.md) - 包括非核心执行器，如夹具， 降落伞等。
|
||||
|
||||
@ -797,4 +797,3 @@ div.frame_variant td, div.frame_variant th {
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
|
||||
|
||||
@ -4,4 +4,4 @@ frame: 垂直起降
|
||||
newEditLink: en/assembly/_assembly.md
|
||||
---
|
||||
|
||||
<!--@include: _assembly.md-->
|
||||
<!--@include: _assembly.md-->
|
||||
|
||||
@ -3,4 +3,4 @@ frame: 基本配置
|
||||
newEditLink: en/assembly/_assembly.md
|
||||
---
|
||||
|
||||
<!--@include: _assembly.md-->
|
||||
<!--@include: _assembly.md-->
|
||||
|
||||
@ -17,4 +17,4 @@ PX4 integrates with three types of cameras:
|
||||
## See Also
|
||||
|
||||
- [云台(相机支架)](../advanced/gimbal_control.md)
|
||||
- [相机集成/架构](../camera/camera_architecture.md) ( PX4 开发者)
|
||||
- [相机集成/架构](../camera/camera_architecture.md) ( PX4 开发者)
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../complete_vehicles_mc/betafpv_beta75x" />
|
||||
<Redirect to="../complete_vehicles_mc/betafpv_beta75x" />
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../complete_vehicles_mc/crazyflie2" />
|
||||
<Redirect to="../complete_vehicles_mc/crazyflie2" />
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../complete_vehicles_mc/crazyflie21" />
|
||||
<Redirect to="../complete_vehicles_mc/crazyflie21" />
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../complete_vehicles_mc/holybro_kops2" />
|
||||
<Redirect to="../complete_vehicles_mc/holybro_kops2" />
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../complete_vehicles_mc/intel_aero" />
|
||||
<Redirect to="../complete_vehicles_mc/intel_aero" />
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../complete_vehicles_mc/mindracer210" />
|
||||
<Redirect to="../complete_vehicles_mc/mindracer210" />
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../complete_vehicles_mc/mindracer_BNF_RTF" />
|
||||
<Redirect to="../complete_vehicles_mc/mindracer_BNF_RTF" />
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../complete_vehicles_mc/modalai_starling" />
|
||||
<Redirect to="../complete_vehicles_mc/modalai_starling" />
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../complete_vehicles_mc/nanomind110" />
|
||||
<Redirect to="../complete_vehicles_mc/nanomind110" />
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../complete_vehicles_mc/px4_vision_kit" />
|
||||
<Redirect to="../complete_vehicles_mc/px4_vision_kit" />
|
||||
|
||||
@ -33,4 +33,4 @@ These may or may not be updatable to run "vanilla" PX4.
|
||||
## See Also
|
||||
|
||||
- [Complete Vehicles (Fixed-Wing)](../complete_vehicles_fw/index.md)
|
||||
- [Complete Vehicles (MC)](../complete_vehicles_mc/index.md)
|
||||
- [Complete Vehicles (MC)](../complete_vehicles_mc/index.md)
|
||||
|
||||
@ -30,4 +30,3 @@ make run_failsafe_web_server
|
||||
<script setup>
|
||||
import { withBase } from 'vitepress';
|
||||
</script>
|
||||
|
||||
|
||||
@ -187,4 +187,4 @@ There are different clients that support ulog streaming:
|
||||
|
||||
## See Also
|
||||
|
||||
- [Encrypted logging](../dev_log/log_encryption.md)
|
||||
- [Encrypted logging](../dev_log/log_encryption.md)
|
||||
|
||||
@ -6,4 +6,4 @@ The QGroundControl _Daily Build_ includes development tools that are hidden in r
|
||||
|
||||
It should be used instead of the stable release when working with new code forked from the PX4 `main` branch.
|
||||
|
||||
- [Download daily builds](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/releases/daily_builds.html)
|
||||
- [Download daily builds](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/releases/daily_builds.html)
|
||||
|
||||
@ -86,5 +86,3 @@ See the documentation [Ark Electronics GitBook](https://arkelectron.gitbook.io/a
|
||||
## 针脚定义
|
||||
|
||||
See the [DS-10 Pixhawk Autopilot Bus Standard](https://arkelectron.gitbook.io/ark-documentation/flight-controllers/ark-fpv/pinout)
|
||||
|
||||
|
||||
|
||||
@ -12,4 +12,4 @@ Flight modes provide autopilot support to make it easier to manually fly the veh
|
||||
:::info
|
||||
本节中的模式子主题包含所有机体共有的信息，但可能与正常/默认设置无关。
|
||||
一般来说，你应该首先看到特定机体的章节，并在关联导航到这些通用的章节。
|
||||
:::
|
||||
:::
|
||||
|
||||
@ -56,4 +56,4 @@ Select the mode-specific sidebar topics for detailed technical information.
|
||||
- [Basic Configuration > Flight Modes](../config/flight_mode.md) - How to map RC control switches to specific flight modes
|
||||
- [Flight Modes (Multicopter)](../flight_modes_mc/index.md)
|
||||
- [Flight Modes (VTOL)](../flight_modes_vtol/index.md)
|
||||
- [Drive Modes (Rover)](../flight_modes_rover/index.md)
|
||||
- [Drive Modes (Rover)](../flight_modes_rover/index.md)
|
||||
|
||||
@ -54,4 +54,3 @@ Select the mode-specific sidebar topics for more detailed technical information.
|
||||
- [Flight Modes (Fixed-Wing)](../flight_modes_fw/index.md)
|
||||
- [Flight Modes (VTOL)](../flight_modes_vtol/index.md)
|
||||
- [Drive Modes (Rover)](../flight_modes_rover/index.md)
|
||||
|
||||
|
||||
@ -1,4 +1,3 @@
|
||||
<Redirect to="../flight_modes/offboard" />
|
||||
|
||||
# Offboard Mode (VTOL)
|
||||
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../flying/basic_flying_mc" />
|
||||
<Redirect to="../flying/basic_flying_mc" />
|
||||
|
||||
@ -28,10 +28,11 @@ The set of supported configurations can be seen in [Airframes Reference > Autogy
|
||||
|
||||
This section contains build logs/instructions for assembling and configuring a number of Autogyro frames.
|
||||
|
||||
- [ThunderFly Auto-G2 (Holybro pix32)](../frames_autogyro/thunderfly_auto_g2.md)
|
||||
- [ThunderFly Auto-G2 (Holybro pix32)](../frames_autogyro/thunderfly_auto_g2.md) - Modified Autogyro RC model
|
||||
|
||||
### Complete Frames with PX4 Preinstalled
|
||||
|
||||
This section lists vehicles that are sold fully assembled and ready to fly (RTF), with PX4 installed.
|
||||
|
||||
- [ThunderFly TF-G2](https://www.thunderfly.cz/tf-g2.html)
|
||||
- [ThunderFly TF-G2](https://docs.thunderfly.cz/instruments/TF-G2) - Unmanned Autogyro Development Kit
|
||||
- [ThunderFly TF-G250](https://docs.thunderfly.cz/instruments/TF-G250) - Atmospheric Sounding Aerological Autogyro
|
||||
|
||||
@ -6,10 +6,11 @@ Durafly™ Auto-G2 Gyrocopter RC model, with several parts of the original model
|
||||
|
||||
|
||||
:::info
|
||||
Auto-G2 autogyro’s airframe is developed and maintained by ThuderFly s.r.o. company.
|
||||
Auto-G2 autogyro’s airframe was originally developed by [ThunderFly](https://www.thunderfly.cz/) and has since evolved into the updated [TF-G2 platform](https://docs.thunderfly.cz/instruments/TF-G2).
|
||||
Check out our site for more information on the current [TF-G2 commercial airframe](https://www.thunderfly.cz/tf-g2.html).
|
||||
:::
|
||||
|
||||
All the added parts are available on [GitHub](https://github.com/ThunderFly-aerospace/TF-G2/) as an open-source project.
|
||||
All the added parts are available on [GitHub](https://github.com/ThunderFly-aerospace/Auto-G2) as an open-source project.
|
||||
Printed parts are designed in [OpenSCAD](https://www.openscad.org/).
|
||||
|
||||
## Modifications
|
||||
@ -23,7 +24,7 @@ Modification of the Durafly model are as follows:
|
||||
|
||||
- Addition of an autopilot
|
||||
- Rotor head with two axes of freedom (pitch, roll)
|
||||
- Two blade rotor with safely breakable rotor plate
|
||||
- Two-blade rotor with safely breakable rotor plate
|
||||
- Larger landing gears
|
||||
|
||||
### 飞控
|
||||
@ -31,14 +32,14 @@ Modification of the Durafly model are as follows:
|
||||
The aircraft with all of the modifications is already quite heavy.
|
||||
Therefore a low-weight flight controller is recommended (e.g. [Holybro pix32](../flight_controller/holybro_pix32.md) or [CUAV nano](../flight_controller/cuav_v5_nano.md)).
|
||||
|
||||
The autopilot should be mounted on the bottom side of the autogyro on a 3D printed damping pad.
|
||||
The autopilot should be mounted on the bottom side of the autogyro on a 3D-printed damping pad.
|
||||
We have used the damping platform found on [thingiverse](https://www.thingiverse.com/thing:160655)
|
||||
|
||||
### Rotor-head
|
||||
|
||||
The rotor head is (compared to the original autogyro) modified so it allows a motion in both roll and pitch axes.
|
||||
The rotor head is (compared to the original autogyro) modified so that it allows a motion in both roll and pitch axes.
|
||||
Thanks to this, the rotor can control turning as well climbing of the autogyro.
|
||||
Directional control of autogyro by rotor is possible even in case of low airspeed compared to the original rudder and elevator control.
|
||||
Directional control of an autogyro by the rotor is possible even in the case of low airspeed compared to the original rudder and elevator control.
|
||||
|
||||
The printed rotor head consists of three parts.
|
||||
The bottom part is screwed using an M2.5 screw to the original plywood pylon.
|
||||
@ -49,49 +50,49 @@ From the rotor side, the screw head has a large area washer.
|
||||
Rotor axis, made of M3x50 high tensile strength screw, goes through the third part.
|
||||
Bearings used are 623 2Z C3 SKF.
|
||||
At the end of this part, there are ball rods attached via M2.5 screws to servos positioned in the bottom part of the pylon.
|
||||
It is preferable to exchange these original servos for better quality ones as they are weak and in the original construction they help each other.
|
||||
It is preferable to exchange these original servos for better quality ones as they are weak and in the original construction, they help each other.
|
||||
|
||||
|
||||
|
||||
### Two-blade rotor
|
||||
|
||||
The original Durafly Auto-G2 autogyro has a three-blade rotor, which as been modified in this built to use a two-blade rotor.
|
||||
The original Durafly Auto-G2 autogyro has a three-blade rotor, which has been modified in this build to use a two-blade rotor.
|
||||
The reasons are reduced vibration and easier construction.
|
||||
Printed central parts are designed to be used both with Chinese Durafly blades or 3D printed blades.
|
||||
|
||||
The rotor's central part consists of several components which have following roles:
|
||||
The rotor's central part consists of several components, which have the following roles:
|
||||
|
||||
- They enable blade flapping.
|
||||
- They have deformation zones that break upon impact with ground.
|
||||
- They have deformation zones that break upon impact with the ground.
|
||||
Thanks to this, the rotor can usually be repaired quickly by replacing only one component.
|
||||
- Easy setup of blades angle-of-attack.
|
||||
- Easy setup of blades' angle-of-attack.
|
||||
|
||||
#### HobbyKing rotor blades
|
||||
|
||||
It is possible to use a printed central part of the rotor with the original blades.
|
||||
These blades can be bought on [HobbyKing](https://hobbyking.com/en_us/duraflytm-auto-g-gyrocopter-821mm-replacement-main-blade-1pcs-bag.html).
|
||||
Hobbyking blades differ in the position of center of gravity and it is therefore necessary to balance them properly.
|
||||
Hobbyking blades differ in the position of the center of gravity, and it is therefore necessary to balance them properly.
|
||||
|
||||
#### 3D printed rotor blades
|
||||
|
||||
It is also possible to print rotor blades.
|
||||
|
||||
The printed rotor blads are still under development, but preliminary tests show they are of better quality mostly thanks to their precise shape and absence of longitudinal grooves.
|
||||
The printed rotor blades are still under development, but preliminary tests show they are of better quality, mostly thanks to their precise shape and absence of longitudinal grooves.
|
||||
However, some of the production processes still need to be tuned.
|
||||
|
||||
|
||||
|
||||
#### Balancing
|
||||
|
||||
Proper blades balance is very important to minimize vibrations.
|
||||
Proper blade balance is very important to minimize vibrations.
|
||||
Blades have to be balanced in such a way, that the center of gravity is located in the middle of the rotor axis.
|
||||
|
||||
Printed blades are balanced in the production process and there is no need to further balance them.
|
||||
Printed blades are balanced in the production process, and there is no need to further balance them.
|
||||
|
||||
### Release device
|
||||
|
||||
If you want to launch an autogyro using a winch or if you want to launch it by towing you need to print a release device.
|
||||
It is a small box equipped with servo which pulls out the pin and releases the rope.
|
||||
If you want to launch an autogyro using a winch or if you want to launch it by towing, you need to print a release device.
|
||||
It is a small box equipped with a servo that pulls out the pin and releases the rope.
|
||||
|
||||
The whole part is glued, using a hot-melt adhesive, under the engine on the bottom part of an autogyro’s body.
|
||||
If an autogyro is towed by a rope its engine must not be turned on.
|
||||
|
||||
@ -212,4 +212,4 @@ For instructions on how, start from [Auto-tune](../config/autotune_mc.md).
|
||||
|
||||
## Acknowledgements
|
||||
|
||||
This build log was contributed by Akshata and Hamish Willee with many thanks to Holybro and Dronecode for Hardware and technical support.
|
||||
This build log was contributed by Akshata and Hamish Willee with many thanks to Holybro and Dronecode for Hardware and technical support.
|
||||
|
||||
@ -79,4 +79,3 @@ After you finish calibration the VTOL is ready to fly.
|
||||
## 技术支持
|
||||
|
||||
If you have any questions regarding your VTOL conversion or configuration please visit <https://discuss.px4.io/c/px4/vtol>.
|
||||
|
||||
|
||||
@ -117,4 +117,3 @@ Configure the frame as shown in QGroundControl below (do not forget to click **A
|
||||
## 技术支持
|
||||
|
||||
If you have any questions regarding your VTOL conversion or configuration please visit <https://discuss.px4.io/c/px4/vtol>.
|
||||
|
||||
|
||||
@ -38,4 +38,3 @@ Similarly, PX4 can also run natively Raspberry Pi (this approach is not generall
|
||||
PX4 is available on many popular commercial drone products, including some that ship with PX4 and others that can be updated with PX4 (allowing you to add mission planning and other PX4 Flight modes to your vehicle).
|
||||
|
||||
For more information see [Complete Vehicles](../complete_vehicles/index.md).
|
||||
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../getting_started/px4_basic_concepts" />
|
||||
<Redirect to="../getting_started/px4_basic_concepts" />
|
||||
|
||||
@ -9,4 +9,4 @@ The LED, tune, and GCS notifications are linked below:
|
||||
|
||||
- [LED Meanings](../getting_started/led_meanings.md)
|
||||
- [Tune/Sound Meanings](../getting_started/tunes.md)
|
||||
- [QGroundControl Flight-Readiness Status](../flying/pre_flight_checks.md)
|
||||
- [QGroundControl Flight-Readiness Status](../flying/pre_flight_checks.md)
|
||||
|
||||
@ -257,4 +257,3 @@ In order to avoid clogging communications links with messages that aren't needed
|
||||
|
||||
If you needed, a GCS or other MAVLink API can request that particular messages are streamed at a particular rate using [MAV_CMD_SET_MESSAGE_INTERVAL](https://mavlink.io/en/messages/common.html#MAV_CMD_SET_MESSAGE_INTERVAL).
|
||||
A particular message can be requested just once using [MAV_CMD_REQUEST_MESSAGE](https://mavlink.io/en/messages/common.html#MAV_CMD_REQUEST_MESSAGE).
|
||||
|
||||
|
||||
@ -28,4 +28,3 @@ The graph has the following properties:
|
||||
You can also zoom the image.
|
||||
- The _Preset_ selection list allows you to refine the list of modules that are shown.
|
||||
- The _Search_ box can be used to find particular modules/topics (topics that are not selected by the search are greyed-out).
|
||||
|
||||
|
||||
@ -69,4 +69,3 @@ PX4/PX4-Autopilot contains a template for writing a new application (module) tha
|
||||
documented [in the source code](https://github.com/PX4/PX4-Autopilot/blob/v1.8.0/src/platforms/px4_module.h#L381)):
|
||||
- They are used to print the command-line usage when entering `module help` on the console.
|
||||
- They are automatically extracted via script to generate the [Modules & Commands Reference](../modules/modules_main.md) page.
|
||||
|
||||
|
||||
@ -77,426 +77,225 @@ Graphs showing how these are used [can be found here](../middleware/uorb_graph.m
|
||||
## Unversioned Messages
|
||||
|
||||
- [ActionRequest](ActionRequest.md)
|
||||
|
||||
- [ActuatorArmed](ActuatorArmed.md)
|
||||
|
||||
- [ActuatorControlsStatus](ActuatorControlsStatus.md)
|
||||
|
||||
- [ActuatorOutputs](ActuatorOutputs.md)
|
||||
|
||||
- [ActuatorServosTrim](ActuatorServosTrim.md) — Servo trims, added as offset to servo outputs
|
||||
|
||||
- [ActuatorTest](ActuatorTest.md)
|
||||
|
||||
- [AdcReport](AdcReport.md)
|
||||
|
||||
- [Airspeed](Airspeed.md)
|
||||
|
||||
- [AirspeedWind](AirspeedWind.md)
|
||||
|
||||
- [AutotuneAttitudeControlStatus](AutotuneAttitudeControlStatus.md)
|
||||
|
||||
- [ButtonEvent](ButtonEvent.md)
|
||||
|
||||
- [CameraCapture](CameraCapture.md)
|
||||
|
||||
- [CameraStatus](CameraStatus.md)
|
||||
|
||||
- [CameraTrigger](CameraTrigger.md)
|
||||
|
||||
- [CanInterfaceStatus](CanInterfaceStatus.md)
|
||||
|
||||
- [CellularStatus](CellularStatus.md) — Cellular status
|
||||
|
||||
- [CollisionConstraints](CollisionConstraints.md) — Local setpoint constraints in NED frame
|
||||
setting something to NaN means that no limit is provided
|
||||
|
||||
- [ControlAllocatorStatus](ControlAllocatorStatus.md)
|
||||
|
||||
- [Cpuload](Cpuload.md)
|
||||
|
||||
- [DatamanRequest](DatamanRequest.md)
|
||||
|
||||
- [DatamanResponse](DatamanResponse.md)
|
||||
|
||||
- [DebugArray](DebugArray.md)
|
||||
|
||||
- [DebugKeyValue](DebugKeyValue.md)
|
||||
|
||||
- [DebugValue](DebugValue.md)
|
||||
|
||||
- [DebugVect](DebugVect.md)
|
||||
|
||||
- [DifferentialPressure](DifferentialPressure.md)
|
||||
|
||||
- [DistanceSensor](DistanceSensor.md) — DISTANCE_SENSOR message data
|
||||
|
||||
- [DistanceSensorModeChangeRequest](DistanceSensorModeChangeRequest.md)
|
||||
|
||||
- [Ekf2Timestamps](Ekf2Timestamps.md) — this message contains the (relative) timestamps of the sensor inputs used by EKF2.
|
||||
It can be used for reproducible replay.
|
||||
|
||||
- [EscReport](EscReport.md)
|
||||
|
||||
- [EscStatus](EscStatus.md)
|
||||
|
||||
- [EstimatorAidSource1d](EstimatorAidSource1d.md)
|
||||
|
||||
- [EstimatorAidSource2d](EstimatorAidSource2d.md)
|
||||
|
||||
- [EstimatorAidSource3d](EstimatorAidSource3d.md)
|
||||
|
||||
- [EstimatorBias](EstimatorBias.md)
|
||||
|
||||
- [EstimatorBias3d](EstimatorBias3d.md)
|
||||
|
||||
- [EstimatorEventFlags](EstimatorEventFlags.md)
|
||||
|
||||
- [EstimatorGpsStatus](EstimatorGpsStatus.md)
|
||||
|
||||
- [EstimatorInnovations](EstimatorInnovations.md)
|
||||
|
||||
- [EstimatorSelectorStatus](EstimatorSelectorStatus.md)
|
||||
|
||||
- [EstimatorSensorBias](EstimatorSensorBias.md) — Sensor readings and in-run biases in SI-unit form. Sensor readings are compensated for static offsets,
|
||||
scale errors, in-run bias and thermal drift (if thermal compensation is enabled and available).
|
||||
|
||||
- [EstimatorStates](EstimatorStates.md)
|
||||
|
||||
- [EstimatorStatus](EstimatorStatus.md)
|
||||
|
||||
- [EstimatorStatusFlags](EstimatorStatusFlags.md)
|
||||
|
||||
- [Event](Event.md) — Events interface
|
||||
|
||||
- [FailsafeFlags](FailsafeFlags.md) — Input flags for the failsafe state machine set by the arming & health checks.
|
||||
|
||||
- [FailureDetectorStatus](FailureDetectorStatus.md)
|
||||
|
||||
- [FigureEightStatus](FigureEightStatus.md)
|
||||
|
||||
- [FixedWingLateralGuidanceStatus](FixedWingLateralGuidanceStatus.md) — Fixed Wing Lateral Guidance Status message
|
||||
Published by fw_pos_control module to report the resultant lateral setpoints and NPFG debug outputs
|
||||
|
||||
- [FixedWingLateralStatus](FixedWingLateralStatus.md) — Fixed Wing Lateral Status message
|
||||
Published by the fw_lateral_longitudinal_control module to report the resultant lateral setpoint
|
||||
|
||||
- [FixedWingRunwayControl](FixedWingRunwayControl.md) — Auxiliary control fields for fixed-wing runway takeoff/landing
|
||||
|
||||
- [FlightPhaseEstimation](FlightPhaseEstimation.md)
|
||||
|
||||
- [FollowTarget](FollowTarget.md)
|
||||
|
||||
- [FollowTargetEstimator](FollowTargetEstimator.md)
|
||||
|
||||
- [FollowTargetStatus](FollowTargetStatus.md)
|
||||
|
||||
- [FuelTankStatus](FuelTankStatus.md)
|
||||
|
||||
- [GeneratorStatus](GeneratorStatus.md)
|
||||
|
||||
- [GeofenceResult](GeofenceResult.md)
|
||||
|
||||
- [GeofenceStatus](GeofenceStatus.md)
|
||||
|
||||
- [GimbalControls](GimbalControls.md)
|
||||
|
||||
- [GimbalDeviceAttitudeStatus](GimbalDeviceAttitudeStatus.md)
|
||||
|
||||
- [GimbalDeviceInformation](GimbalDeviceInformation.md)
|
||||
|
||||
- [GimbalDeviceSetAttitude](GimbalDeviceSetAttitude.md)
|
||||
|
||||
- [GimbalManagerInformation](GimbalManagerInformation.md)
|
||||
|
||||
- [GimbalManagerSetAttitude](GimbalManagerSetAttitude.md)
|
||||
|
||||
- [GimbalManagerSetManualControl](GimbalManagerSetManualControl.md)
|
||||
|
||||
- [GimbalManagerStatus](GimbalManagerStatus.md)
|
||||
|
||||
- [GpioConfig](GpioConfig.md) — GPIO configuration
|
||||
|
||||
- [GpioIn](GpioIn.md) — GPIO mask and state
|
||||
|
||||
- [GpioOut](GpioOut.md) — GPIO mask and state
|
||||
|
||||
- [GpioRequest](GpioRequest.md) — Request GPIO mask to be read
|
||||
|
||||
- [GpsDump](GpsDump.md) — This message is used to dump the raw gps communication to the log.
|
||||
|
||||
- [GpsInjectData](GpsInjectData.md)
|
||||
|
||||
- [Gripper](Gripper.md) — # Used to command an actuation in the gripper, which is mapped to a specific output in the control allocation module
|
||||
|
||||
- [HealthReport](HealthReport.md)
|
||||
|
||||
- [HeaterStatus](HeaterStatus.md)
|
||||
|
||||
- [HoverThrustEstimate](HoverThrustEstimate.md)
|
||||
|
||||
- [InputRc](InputRc.md)
|
||||
|
||||
- [InternalCombustionEngineControl](InternalCombustionEngineControl.md)
|
||||
|
||||
- [InternalCombustionEngineStatus](InternalCombustionEngineStatus.md)
|
||||
|
||||
- [IridiumsbdStatus](IridiumsbdStatus.md)
|
||||
|
||||
- [IrlockReport](IrlockReport.md) — IRLOCK_REPORT message data
|
||||
|
||||
- [LandingGear](LandingGear.md)
|
||||
|
||||
- [LandingGearWheel](LandingGearWheel.md)
|
||||
|
||||
- [LandingTargetInnovations](LandingTargetInnovations.md)
|
||||
|
||||
- [LandingTargetPose](LandingTargetPose.md) — Relative position of precision land target in navigation (body fixed, north aligned, NED) and inertial (world fixed, north aligned, NED) frames
|
||||
|
||||
- [LaunchDetectionStatus](LaunchDetectionStatus.md) — Status of the launch detection state machine (fixed-wing only)
|
||||
|
||||
- [LedControl](LedControl.md) — LED control: control a single or multiple LED's.
|
||||
These are the externally visible LED's, not the board LED's
|
||||
|
||||
- [LogMessage](LogMessage.md) — A logging message, output with PX4_WARN, PX4_ERR, PX4_INFO
|
||||
|
||||
- [LoggerStatus](LoggerStatus.md)
|
||||
|
||||
- [MagWorkerData](MagWorkerData.md)
|
||||
|
||||
- [MagnetometerBiasEstimate](MagnetometerBiasEstimate.md)
|
||||
|
||||
- [ManualControlSwitches](ManualControlSwitches.md)
|
||||
|
||||
- [MavlinkLog](MavlinkLog.md)
|
||||
|
||||
- [MavlinkTunnel](MavlinkTunnel.md) — MAV_TUNNEL_PAYLOAD_TYPE enum
|
||||
|
||||
- [MessageFormatRequest](MessageFormatRequest.md)
|
||||
|
||||
- [MessageFormatResponse](MessageFormatResponse.md)
|
||||
|
||||
- [Mission](Mission.md)
|
||||
|
||||
- [MissionResult](MissionResult.md)
|
||||
|
||||
- [MountOrientation](MountOrientation.md)
|
||||
|
||||
- [NavigatorMissionItem](NavigatorMissionItem.md)
|
||||
|
||||
- [NavigatorStatus](NavigatorStatus.md) — Current status of a Navigator mode
|
||||
The possible values of nav_state are defined in the VehicleStatus msg.
|
||||
|
||||
- [NormalizedUnsignedSetpoint](NormalizedUnsignedSetpoint.md)
|
||||
|
||||
- [ObstacleDistance](ObstacleDistance.md) — Obstacle distances in front of the sensor.
|
||||
|
||||
- [OffboardControlMode](OffboardControlMode.md) — Off-board control mode
|
||||
|
||||
- [OnboardComputerStatus](OnboardComputerStatus.md) — ONBOARD_COMPUTER_STATUS message data
|
||||
|
||||
- [OpenDroneIdArmStatus](OpenDroneIdArmStatus.md)
|
||||
|
||||
- [OpenDroneIdOperatorId](OpenDroneIdOperatorId.md)
|
||||
|
||||
- [OpenDroneIdSelfId](OpenDroneIdSelfId.md)
|
||||
|
||||
- [OpenDroneIdSystem](OpenDroneIdSystem.md)
|
||||
|
||||
- [OrbTest](OrbTest.md)
|
||||
|
||||
- [OrbTestLarge](OrbTestLarge.md)
|
||||
|
||||
- [OrbTestMedium](OrbTestMedium.md)
|
||||
|
||||
- [OrbitStatus](OrbitStatus.md) — ORBIT_YAW_BEHAVIOUR
|
||||
|
||||
- [ParameterResetRequest](ParameterResetRequest.md) — ParameterResetRequest : Used by the primary to reset one or all parameter value(s) on the remote
|
||||
|
||||
- [ParameterSetUsedRequest](ParameterSetUsedRequest.md) — ParameterSetUsedRequest : Used by a remote to update the used flag for a parameter on the primary
|
||||
|
||||
- [ParameterSetValueRequest](ParameterSetValueRequest.md) — ParameterSetValueRequest : Used by a remote or primary to update the value for a parameter at the other end
|
||||
|
||||
- [ParameterSetValueResponse](ParameterSetValueResponse.md) — ParameterSetValueResponse : Response to a set value request by either primary or secondary
|
||||
|
||||
- [ParameterUpdate](ParameterUpdate.md) — This message is used to notify the system about one or more parameter changes
|
||||
|
||||
- [Ping](Ping.md)
|
||||
|
||||
- [PositionControllerLandingStatus](PositionControllerLandingStatus.md)
|
||||
|
||||
- [PositionControllerStatus](PositionControllerStatus.md)
|
||||
|
||||
- [PositionSetpoint](PositionSetpoint.md) — this file is only used in the position_setpoint triple as a dependency
|
||||
|
||||
- [PositionSetpointTriplet](PositionSetpointTriplet.md) — Global position setpoint triplet in WGS84 coordinates.
|
||||
This are the three next waypoints (or just the next two or one).
|
||||
|
||||
- [PowerButtonState](PowerButtonState.md) — power button state notification message
|
||||
|
||||
- [PowerMonitor](PowerMonitor.md) — power monitor message
|
||||
|
||||
- [PpsCapture](PpsCapture.md)
|
||||
|
||||
- [PurePursuitStatus](PurePursuitStatus.md)
|
||||
|
||||
- [PwmInput](PwmInput.md)
|
||||
|
||||
- [Px4ioStatus](Px4ioStatus.md)
|
||||
|
||||
- [QshellReq](QshellReq.md)
|
||||
|
||||
- [QshellRetval](QshellRetval.md)
|
||||
|
||||
- [RadioStatus](RadioStatus.md)
|
||||
|
||||
- [RateCtrlStatus](RateCtrlStatus.md)
|
||||
|
||||
- [RcChannels](RcChannels.md)
|
||||
|
||||
- [RcParameterMap](RcParameterMap.md)
|
||||
|
||||
- [RoverAttitudeSetpoint](RoverAttitudeSetpoint.md)
|
||||
|
||||
- [RoverAttitudeStatus](RoverAttitudeStatus.md)
|
||||
|
||||
- [RoverPositionSetpoint](RoverPositionSetpoint.md)
|
||||
|
||||
- [RoverRateSetpoint](RoverRateSetpoint.md)
|
||||
|
||||
- [RoverRateStatus](RoverRateStatus.md)
|
||||
|
||||
- [RoverSteeringSetpoint](RoverSteeringSetpoint.md)
|
||||
|
||||
- [RoverThrottleSetpoint](RoverThrottleSetpoint.md)
|
||||
|
||||
- [RoverVelocitySetpoint](RoverVelocitySetpoint.md)
|
||||
|
||||
- [RoverVelocityStatus](RoverVelocityStatus.md)
|
||||
|
||||
- [Rpm](Rpm.md)
|
||||
|
||||
- [RtlStatus](RtlStatus.md)
|
||||
|
||||
- [RtlTimeEstimate](RtlTimeEstimate.md)
|
||||
|
||||
- [SatelliteInfo](SatelliteInfo.md)
|
||||
|
||||
- [SensorAccel](SensorAccel.md)
|
||||
|
||||
- [SensorAccelFifo](SensorAccelFifo.md)
|
||||
|
||||
- [SensorAirflow](SensorAirflow.md)
|
||||
|
||||
- [SensorBaro](SensorBaro.md)
|
||||
|
||||
- [SensorCombined](SensorCombined.md) — Sensor readings in SI-unit form.
|
||||
These fields are scaled and offset-compensated where possible and do not
|
||||
change with board revisions and sensor updates.
|
||||
|
||||
- [SensorCorrection](SensorCorrection.md) — Sensor corrections in SI-unit form for the voted sensor
|
||||
|
||||
- [SensorGnssRelative](SensorGnssRelative.md) — GNSS relative positioning information in NED frame. The NED frame is defined as the local topological system at the reference station.
|
||||
|
||||
- [SensorGps](SensorGps.md) — GPS position in WGS84 coordinates.
|
||||
the field 'timestamp' is for the position & velocity (microseconds)
|
||||
|
||||
- [SensorGyro](SensorGyro.md)
|
||||
|
||||
- [SensorGyroFft](SensorGyroFft.md)
|
||||
|
||||
- [SensorGyroFifo](SensorGyroFifo.md)
|
||||
|
||||
- [SensorHygrometer](SensorHygrometer.md)
|
||||
|
||||
- [SensorMag](SensorMag.md)
|
||||
|
||||
- [SensorOpticalFlow](SensorOpticalFlow.md)
|
||||
|
||||
- [SensorPreflightMag](SensorPreflightMag.md) — Pre-flight sensor check metrics.
|
||||
The topic will not be updated when the vehicle is armed
|
||||
|
||||
- [SensorSelection](SensorSelection.md) — Sensor ID's for the voted sensors output on the sensor_combined topic.
|
||||
Will be updated on startup of the sensor module and when sensor selection changes
|
||||
|
||||
- [SensorUwb](SensorUwb.md) — UWB distance contains the distance information measured by an ultra-wideband positioning system,
|
||||
such as Pozyx or NXP Rddrone.
|
||||
|
||||
- [SensorsStatus](SensorsStatus.md) — Sensor check metrics. This will be zero for a sensor that's primary or unpopulated.
|
||||
|
||||
- [SensorsStatusImu](SensorsStatusImu.md) — Sensor check metrics. This will be zero for a sensor that's primary or unpopulated.
|
||||
|
||||
- [SystemPower](SystemPower.md)
|
||||
|
||||
- [TakeoffStatus](TakeoffStatus.md) — Status of the takeoff state machine currently just available for multicopters
|
||||
|
||||
- [TaskStackInfo](TaskStackInfo.md) — stack information for a single running process
|
||||
|
||||
- [TecsStatus](TecsStatus.md)
|
||||
|
||||
- [TelemetryStatus](TelemetryStatus.md)
|
||||
|
||||
- [TiltrotorExtraControls](TiltrotorExtraControls.md)
|
||||
|
||||
- [TimesyncStatus](TimesyncStatus.md)
|
||||
|
||||
- [TrajectorySetpoint6dof](TrajectorySetpoint6dof.md) — Trajectory setpoint in NED frame
|
||||
Input to position controller.
|
||||
|
||||
- [TransponderReport](TransponderReport.md)
|
||||
|
||||
- [TuneControl](TuneControl.md) — This message is used to control the tunes, when the tune_id is set to CUSTOM
|
||||
then the frequency, duration are used otherwise those values are ignored.
|
||||
|
||||
- [UavcanParameterRequest](UavcanParameterRequest.md) — UAVCAN-MAVLink parameter bridge request type
|
||||
|
||||
- [UavcanParameterValue](UavcanParameterValue.md) — UAVCAN-MAVLink parameter bridge response type
|
||||
|
||||
- [UlogStream](UlogStream.md) — Message to stream ULog data from the logger. Corresponds to the LOGGING_DATA
|
||||
mavlink message
|
||||
|
||||
- [UlogStreamAck](UlogStreamAck.md) — Ack a previously sent ulog_stream message that had
|
||||
the NEED_ACK flag set
|
||||
|
||||
- [VehicleAcceleration](VehicleAcceleration.md)
|
||||
|
||||
- [VehicleAirData](VehicleAirData.md)
|
||||
|
||||
- [VehicleAngularAccelerationSetpoint](VehicleAngularAccelerationSetpoint.md)
|
||||
|
||||
- [VehicleConstraints](VehicleConstraints.md) — Local setpoint constraints in NED frame
|
||||
setting something to NaN means that no limit is provided
|
||||
|
||||
- [VehicleImu](VehicleImu.md) — IMU readings in SI-unit form.
|
||||
|
||||
- [VehicleImuStatus](VehicleImuStatus.md)
|
||||
|
||||
- [VehicleLocalPositionSetpoint](VehicleLocalPositionSetpoint.md) — Local position setpoint in NED frame
|
||||
Telemetry of PID position controller to monitor tracking.
|
||||
NaN means the state was not controlled
|
||||
|
||||
- [VehicleMagnetometer](VehicleMagnetometer.md)
|
||||
|
||||
- [VehicleOpticalFlow](VehicleOpticalFlow.md) — Optical flow in XYZ body frame in SI units.
|
||||
|
||||
- [VehicleOpticalFlowVel](VehicleOpticalFlowVel.md)
|
||||
|
||||
- [VehicleRoi](VehicleRoi.md) — Vehicle Region Of Interest (ROI)
|
||||
|
||||
- [VehicleThrustSetpoint](VehicleThrustSetpoint.md)
|
||||
|
||||
- [VehicleTorqueSetpoint](VehicleTorqueSetpoint.md)
|
||||
|
||||
- [VelocityLimits](VelocityLimits.md) — Velocity and yaw rate limits for a multicopter position slow mode only
|
||||
|
||||
- [WheelEncoders](WheelEncoders.md)
|
||||
|
||||
- [Wind](Wind.md)
|
||||
|
||||
- [YawEstimatorStatus](YawEstimatorStatus.md)
|
||||
|
||||
- [AirspeedValidatedV0](AirspeedValidatedV0.md)
|
||||
|
||||
- [VehicleAttitudeSetpointV0](VehicleAttitudeSetpointV0.md)
|
||||
|
||||
- [VehicleStatusV0](VehicleStatusV0.md) — Encodes the system state of the vehicle published by commander
|
||||
- [VehicleStatusV0](VehicleStatusV0.md) — Encodes the system state of the vehicle published by commander
|
||||
|
||||
@ -164,4 +164,4 @@ Payloads that are triggered by servos and other actuators, such as grippers, can
|
||||
|
||||
This is safer than testing when the vehicle is armed.
|
||||
|
||||
Camera payloads can be triggered and tested at any time.
|
||||
Camera payloads can be triggered and tested at any time.
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../camera/configuration" />
|
||||
<Redirect to="../camera/configuration" />
|
||||
|
||||
@ -1 +1 @@
|
||||
<Redirect to="../camera/camera_intel_realsense_t265_vio" />
|
||||
<Redirect to="../camera/camera_intel_realsense_t265_vio" />
|
||||
|
||||
@ -124,4 +124,3 @@ Links to setup instructions for specific MAVLink components:
|
||||
- [Serial Port Configuration](../peripherals/serial_configuration.md)
|
||||
- [PX4 Ethernet Setup > PX4 MAVLink Serial Port Configuration](../advanced_config/ethernet_setup.md#px4-mavlink-serial-port-configuration)
|
||||
- [Serial Port Mapping](../hardware/serial_port_mapping.md)
|
||||
|
||||
|
||||
@ -55,4 +55,4 @@ To get started using the library within an existing ROS 2 workspace:
|
||||
When opening a pull request to PX4, CI runs the library integration tests.
|
||||
These test that mode registration, failsafes, and mode replacement, work as expected.
|
||||
|
||||
For more information see [PX4 ROS2 Interface Library Integration Testing](../test_and_ci/integration_testing_px4_ros2_interface.md).
|
||||
For more information see [PX4 ROS2 Interface Library Integration Testing](../test_and_ci/integration_testing_px4_ros2_interface.md).
|
||||
|
||||
@ -11,25 +11,21 @@ For fixed-wing flight it is the airspeed that guarantees lift — not ground spe
|
||||
Recommended digital airspeed sensors include:
|
||||
|
||||
- Based on [Pitot tube](https://en.wikipedia.org/wiki/Pitot_tube)
|
||||
- MEAS Spec series (e.g. [MS4525DO](https://www.te.com/usa-en/product-CAT-BLPS0002.html), [MS5525](https://www.te.com/usa-en/product-CAT-BLPS0003.html))
|
||||
- [mRo I2C Airspeed Sensor JST-GH MS4525DO](https://store.mrobotics.io/mRo-I2C-Airspeed-Sensor-JST-GH-p/m10030a.htm) (mRo store)
|
||||
- [Digital Differential Airspeed Sensor Kit](https://store-drotek.com/793-digital-differential-airspeed-sensor-kit-.html) (Drotek).
|
||||
- [Holybro Digital Air Speed Sensor - MS4525DO](https://holybro.com/collections/sensors/products/digital-air-speed-sensor-ms4525do)
|
||||
- [Holybro Digital Air Speed Sensor - MS5525DSO](https://holybro.com/collections/sensors/products/digital-air-speed-sensor-ms5525dso)
|
||||
- [Holybro High Precision DroneCAN Airspeed Sensor - DLVR](https://holybro.com/collections/sensors/products/high-precision-dronecan-airspeed-sensor-dlvr)
|
||||
- [RaccoonLab Cyphal/CAN and DroneCAN Airspeed Sensor](https://raccoonlab.co/tproduct/360882105-652259850171-cyphal-and-dronecan-airspeed-v2)
|
||||
- [Sensirion SDP3x Airspeed Sensor Kit](https://store-drotek.com/793-digital-differential-airspeed-sensor-kit-.html)
|
||||
- I2C MEAS Spec series (e.g. [MS4525DO](https://www.te.com/usa-en/product-CAT-BLPS0002.html), [MS5525](https://www.te.com/usa-en/product-CAT-BLPS0003.html))
|
||||
- [mRo I2C Airspeed Sensor JST-GH MS4525DO](https://store.3dr.com/mro-i2c-airspeed-sensor-jst-gh-ms4525do/) (3DR store)
|
||||
- [Digital Differential Airspeed Sensor Kit - MS4525DO](https://store-drotek.com/793-digital-differential-airspeed-sensor-kit-.html) (Drotek).
|
||||
- [Holybro Digital Air Speed Sensor - MS4525DO](https://holybro.com/collections/sensors/products/digital-air-speed-sensor-ms4525do)
|
||||
- [Holybro Digital Air Speed Sensor - MS5525DSO](https://holybro.com/collections/sensors/products/digital-air-speed-sensor-ms5525dso)
|
||||
- I2C Sensirion series (e.g. SDP33)
|
||||
- [ThunderFly TFPITOT01 Lightweight Pitot Tube](https://docs.thunderfly.cz/avionics/TFPITOT01/)
|
||||
- [Drotek SDP3x Airspeed Sensor Kit](https://store-drotek.com/848-sdp3x-airspeed-sensor-kit-sdp33.html)
|
||||
- DroneCAN interface
|
||||
- [Holybro High Precision DroneCAN Airspeed Sensor - DLVR](https://holybro.com/collections/sensors/products/high-precision-dronecan-airspeed-sensor-dlvr)
|
||||
- [RaccoonLab Cyphal/CAN and DroneCAN Airspeed Sensor - MS4525DO](https://raccoonlab.co/tproduct/360882105-652259850171-cyphal-and-dronecan-airspeed-v2)
|
||||
- [Avionics Anonymous Air Data Computer with OAT probe](https://www.tindie.com/products/avionicsanonymous/uavcan-air-data-computer-airspeed-sensor/)
|
||||
- Based on [Venturi effect](https://en.wikipedia.org/wiki/Venturi_effect)
|
||||
- [TFSLOT](airspeed_tfslot.md) Venturi effect airspeed sensor.
|
||||
|
||||
All the above sensors are connected via the I2C bus/port.
|
||||
|
||||
::: info
|
||||
|
||||
Additionally, the [Avionics Anonymous Air Data Computer](https://www.tindie.com/products/avionicsanonymous/uavcan-air-data-computer-airspeed-sensor/) can be connected to the CAN bus to determine not only high-accuracy airspeed, but also true static pressure and air temperature via onboard barometer and an OAT probe.
|
||||
|
||||
:::
|
||||
|
||||
## 配置
|
||||
|
||||
### Enable Airspeed Sensors
|
||||
|
||||
@ -5,8 +5,9 @@ Telemetry Radios can (optionally) be used to provide a wireless MAVLink connecti
|
||||
PX4支持多种类型数传电台：
|
||||
|
||||
- [SiK Radio](../telemetry/sik_radio.md) based firmware (more generally, any radio with a UART interface should work).
|
||||
- [RFD900 Telemetry Radio](../telemetry/rfd900_telemetry.md)
|
||||
- [HolyBro SiK Telemetry Radio](../telemetry/holybro_sik_radio.md)
|
||||
- [RFD900 Telemetry Radio](../telemetry/rfd900_telemetry.md)
|
||||
- [ThunderFly TFSIK01 Telemetry Radio](../telemetry/tfsik_telemetry.md)
|
||||
- <del>_HKPilot Telemetry Radio_</del> (Discontinued)
|
||||
- <del>_3DR Telemetry Radio_</del> (Discontinued)
|
||||
- [Telemetry Wifi](../telemetry/telemetry_wifi.md)
|
||||
|
||||
@ -13,8 +13,9 @@ Hardware for the SiK radio can be obtained from various manufacturers/stores in
|
||||
|
||||
## Vendors
|
||||
|
||||
- [RFD900 Telemetry Radio](../telemetry/rfd900_telemetry.md)
|
||||
- [Holybro Telemetry Radio](../telemetry/holybro_sik_radio.md)
|
||||
- [RFD900 Telemetry Radio](../telemetry/rfd900_telemetry.md)
|
||||
- [ThunderFly TFSIK01 Telemetry Radio](../telemetry/tfsik_telemetry.md)
|
||||
- <del>_HKPilot Telemetry Radio_</del> (Discontinued)
|
||||
- <del>_3DR Telemetry Radio_</del> (Discontinued)
|
||||
|
||||
|
||||
62
docs/zh/telemetry/tfsik_telemetry.md
Normal file
62
docs/zh/telemetry/tfsik_telemetry.md
Normal file
@ -0,0 +1,62 @@
|
||||
# TFSIK01 Telemetry Modem
|
||||
|
||||
The [TFSIK01](https://docs.thunderfly.cz/avionics/TFSIK01/) is a high-performance open-source telemetry modem developed by [ThunderFly](https://www.thunderfly.cz/).
|
||||
It is designed to provide robust wireless communication between UAVs and ground stations.
|
||||
Featuring dual antenna diversity, strong interference immunity, and compatibility with MAVLink framing, it is an ideal choice for demanding UAV and robotics applications.
|
||||
|
||||
|
||||
|
||||
The modem is plug-and-play with flight controllers using a JST-GH UART interface and is available pre-configured for the 433, 868, and 915 MHz bands, (other non-standard frequencies available on request).
|
||||
|
||||
## 购买渠道
|
||||
|
||||
- [TFSIK01A on Tindie](https://www.tindie.com/products/34682/)
|
||||
- Directly from [ThunderFly](https://www.thunderfly.cz/contact-us.html) ([sale@thunderfly.cz](mailto:sale@thunderfly.cz))
|
||||
|
||||
## 特性
|
||||
|
||||
- Open-source SiK firmware
|
||||
- Dual antenna diversity with automatic switching
|
||||
- Robust against interference and out-of-band signal jamming
|
||||
- Frequency-Hopping Spread Spectrum (FHSS)
|
||||
- Adaptive TDM, LBT, and AFA support
|
||||
- MAVLink protocol support
|
||||
- Up to 250 kbps air data rate
|
||||
- Several kilometres of range
|
||||
- Plug-n-play with Pixhawk-compatible flight controllers
|
||||
|
||||
## 技术规范
|
||||
|
||||
- Frequency: 433 MHz (default), 868 MHz, 915 MHz, or custom
|
||||
- Power: up to 500 mW (27 dBm), adjustable (100mW default)
|
||||
- Interface: JST-GH 6-pin UART (3.3V)
|
||||
- Connectors: Dual MCX — snap-on connectors that reduce the risk of damage in case of crash impacts
|
||||
- Weight: 18 g
|
||||
|
||||
## LEDs Indicators Status
|
||||
|
||||
- **Green blinking** – searching for link
|
||||
- **Green solid** – link established
|
||||
- **Red flashing** – data transmission
|
||||
- **Red solid** – firmware update mode
|
||||
- **Orange** – indicates selected antenna for RX/TX
|
||||
|
||||
## Connecting to Flight Controller
|
||||
|
||||
Connect to the `TELEM1` port of your flight controller using the included JST-GH cable.
|
||||
Configuration may be required for alternative UART ports.
|
||||
|
||||
## Connecting to PC or Ground Station
|
||||
|
||||
Use the [TFUSBSERIAL01](https://docs.thunderfly.cz/avionics/TFUSBSERIAL01/) USB-C to UART adapter to connect the modem to your PC, tablet, or Raspberry Pi.
|
||||
|
||||
## Package Includes
|
||||
|
||||
- 2× TFSIK01 Modems (with housing)
|
||||
- 2× JST-GH serial cables
|
||||
- 1× TFUSBSERIAL01 USB-C to UART converter
|
||||
- 2× MCX Antenna kit (optional)
|
||||
|
||||
## More Information
|
||||
|
||||
For detailed specifications, configuration options, firmware updates, and advanced usage, visit the full [TFSIK01 documentation](https://docs.thunderfly.cz/avionics/TFSIK01/)
|
||||
@ -26,4 +26,4 @@ You can list the available test cases with:
|
||||
|
||||
```sh
|
||||
./test/ros_test_runner.py --list-cases
|
||||
```
|
||||
```
|
||||
|
||||
@ -152,4 +152,4 @@ To write a new test:
|
||||
@"$(SRC_DIR)"/test/rostest_px4_run.sh mavros_posix_tests_<new_test>.test
|
||||
```
|
||||
|
||||
Run the tests as described above.
|
||||
Run the tests as described above.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user