fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-10-23 06:53:34 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs(i18n): PX4 guide translations (Crowdin) - ko (#26898)

Browse Source 
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
2026-04-01 17:29:31 +11:00
committed by GitHub
co-authored by Crowdin Bot
parent 757be36ac2
commit 2e0000c8fa
34 changed files with 1524 additions and 750 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ko/can/index.md
+2 -2
View File
@@ -38,7 +38,7 @@ Devices within a network are connected in a _daisy-chain_ in any order (this dif
:::warning
Don't connect each CAN peripheral to a separate CAN port!
Unlike UARTs, CAN peripherals are designed to be daisy chained, with additional ports such as `CAN2` used for [redundancy](redundancy).
Unlike UARTs, CAN peripherals are designed to be daisy chained, with additional ports such as `CAN2` used for [redundancy](#redundancy).
:::
At either end of the chain, a 120Ω termination resistor should be connected between the two data lines.
@@ -84,7 +84,7 @@ You only _need_ one CAN port to support an arbitrary number of CAN devices using
Don't connect each CAN peripheral to a separate CAN port!
:::
Generally you'll daisy all CAN peripherals off a single port, and if there is more than one CAN port, use the second one for [redundancy](redundancy).
Generally you'll daisy all CAN peripherals off a single port, and if there is more than one CAN port, use the second one for [redundancy](#redundancy).
If three are three ports, you might use the remaining network for devices that support another CAN protocol.
The documentation for your flight controller should indicate which ports are supported/enabled.