mirror of
https://github.com/CopterExpress/clover.git
synced 2026-06-05 09:09:33 +00:00
docs: more proper-names checks!
This commit is contained in:
@@ -29,7 +29,7 @@
|
||||
* [Coordinate systems (frames)](frames.md)
|
||||
* [ROS](ros.md)
|
||||
* [MAVROS](mavros.md)
|
||||
* [Simple offboard](simple_offboard.md)
|
||||
* [Simple OFFBOARD](simple_offboard.md)
|
||||
* [Navigation using ArUco markers](aruco.md)
|
||||
* [Automatic check](selfcheck.md)
|
||||
* [Code examples](snippets.md)
|
||||
|
||||
@@ -134,7 +134,7 @@ article [remote faults](radioerrors.md).
|
||||
|
||||
1. Turn the transmitter ON
|
||||
|
||||
Make sure ppm in the RX Setup menu is disabled ([section "No communications with the flight controller"](radioerrors.md))
|
||||
Make sure PPM in the RX Setup menu is disabled ([section "No communications with the flight controller"](radioerrors.md))
|
||||
|
||||
In point 3, select “RX setup” > “PPM OUTPUT” > “Off”.
|
||||
|
||||
@@ -232,4 +232,4 @@ article [remote faults](radioerrors.md).
|
||||
|
||||
.
|
||||
|
||||
Read more about connection in [article](connection.md).
|
||||
Read more about connection in [article](connection.md).
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
Connecting Pixhawk/Pixracer to Raspberry Pi
|
||||
===
|
||||
|
||||
To program [autonomous flights] (simple_offboard.md) [work with Pixhawk (Pixracer) over Wi-Fi] (gcs_bridge.md), use [of a phone transmitter] (rc.md), and other functions, it is necessary to connect Raspberry Pi to Pixhawk (Pixracer).
|
||||
To program [autonomous flights](simple_offboard.md) [work with Pixhawk (Pixracer) over Wi-Fi](gcs_bridge.md), use [of a phone transmitter] (rc.md), and other functions, it is necessary to connect Raspberry Pi to Pixhawk (Pixracer).
|
||||
|
||||
Check operability of the connection [by running on Raspberry Pi] (ssh.md):
|
||||
Check operability of the connection [by running on Raspberry Pi](ssh.md):
|
||||
|
||||
```bash
|
||||
rostopic echo /mavros/state
|
||||
@@ -57,4 +57,4 @@ To connect locally/remotely to a running [SITL](sitl.md), set argument `fcu_conn
|
||||
```xml
|
||||
<arg name="fcu_conn" default="udp"/>
|
||||
<arg name="fcu_ip" default="127.0.0.1"/>
|
||||
```
|
||||
```
|
||||
|
||||
@@ -5,7 +5,7 @@ Upon connecting GPS, the following possibilities appear:
|
||||
|
||||
* The copter can remain at the same point when flying outside
|
||||
* Autonomous missions may be programmed in the QGroundControl application
|
||||
* Flying may be performed by global points in standalone mode using the [simple offboard] module (simple_offboard.md).
|
||||
* Flying may be performed by global points in standalone mode using the [simple_offboard](simple_offboard.md) module.
|
||||
|
||||
Useful links:
|
||||
|
||||
@@ -20,4 +20,4 @@ The GPS module is connected to "GPS" and "I2C" (compass) connectors of the fligh
|
||||
|
||||
If GPS is connected, magnetometers are to be re-calibrated in the QGroundControl application via a [Wi-Fi](Wi-Fi.md) or USB connection.
|
||||
|
||||
Next, GPS is to be enabled in parameter `EKF2_AID_MASK` (when EKF2is used) or `LPE_FUSION` (when LPE is used).
|
||||
Next, GPS is to be enabled in parameter `EKF2_AID_MASK` (when EKF2is used) or `LPE_FUSION` (when LPE is used).
|
||||
|
||||
@@ -213,7 +213,7 @@ The result of the command:
|
||||
|
||||
## Why exactly so, and is there a different way?
|
||||
|
||||
The main types of strips used for Clever 3 are WS2812, WS2812B and SK6812 \(analog to WS2812B\). They are controlled according to the same principle: for a massif of LEDs in the strip, a data packet at the rate of 24 bits per LED; each led reads the first 24 bits of received data, and sets the corresponding color, the rest of the data are sent to the next LED in the strip. Zeros and ones are determined by different combinations of the durations of high and low level in the pulse.
|
||||
The main types of strips used for Clever 3 are WS2812, WS2812B and SK6812 \(analog to WS2812B\). They are controlled according to the same principle: for a massif of LEDs in the strip, a data packet at the rate of 24 bits per LED; each LED reads the first 24 bits of received data, and sets the corresponding color, the rest of the data are sent to the next LED in the strip. Zeros and ones are determined by different combinations of the durations of high and low level in the pulse.
|
||||
|
||||
All these strips are supported for library management [rpi_ws281x](https://github.com/jgarff/rpi_ws281x), with that, the DMA module\(direct memory access \) of the Raspberri processor, and one of the data channels re used for control: PWM, PCM, or SPI, which guarantees absence of delays in control \(and everything is controlled from a multitasking OS, it's important\).
|
||||
|
||||
|
||||
@@ -148,7 +148,7 @@ Below you can read more about how RPi networking is organized.
|
||||
|
||||
## RPi network organization
|
||||
|
||||
Network operation in image **2017-11-29-raspbian-stretch-lite** is supported by two pre-installed services:
|
||||
Network operation in the [image](microsd_images.md) is supported by two pre-installed services:
|
||||
|
||||
* **networking** — the service enables all network interfaces at the moment of start [5].
|
||||
* **dhcpcd** — the service ensures configuration of addressing and routing on the interfaces obtained dynamically, or specified statically in the config file.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
Simple offboard
|
||||
Simple OFFBOARD
|
||||
===
|
||||
|
||||
> **Note** Documentation for the [image](microsd_images.md), versions, starting with **0.15**. For older versions refer to [documentation for version **0.14**](https://github.com/CopterExpress/clever/blob/v0.14/docs/ru/simple_offboard.md).
|
||||
@@ -56,8 +56,8 @@ Response format:
|
||||
* `armed` `armed` state of propellers (the propellers are armed, if true);
|
||||
* `mode` – current [flight mode](modes.md);
|
||||
* `x, y, z` — local position of the copter *(m)*;
|
||||
* `lat, lon` – latitude, longitude *(degrees)*, [GPS] is to be available (gps.md);
|
||||
* `alt` – altitude in the global system of coordinates (standard [WGS-84](https://ru.wikipedia.org/wiki/WGS_84), not <abbr title="Above Mean Sea Level">AMSL</abbr>!), [GPS] is to be available (gps.md);
|
||||
* `lat, lon` – latitude, longitude *(degrees)*, [GPS](gps.md) is to be available;
|
||||
* `alt` – altitude in the global system of coordinates (standard [WGS-84](https://ru.wikipedia.org/wiki/WGS_84), not <abbr title="Above Mean Sea Level">AMSL</abbr>!), [GPS](gps.md) is to be available ;
|
||||
* `vx, vy, vz` – copter velocity *(m/s)*;
|
||||
* `pitch` – pitch angle *(radians)*;
|
||||
* `roll` – roll angle *(radians)*;
|
||||
@@ -317,4 +317,4 @@ Additional materials
|
||||
------------------------
|
||||
|
||||
* [Flying in the field of ArUco markers](aruco.md).
|
||||
* [Samples of programs and snippets](snippets.md).
|
||||
* [Samples of programs and snippets](snippets.md).
|
||||
|
||||
Reference in New Issue
Block a user