mirror of
https://github.com/iNavFlight/inav.git
synced 2025-07-15 12:25:17 +03:00
Merge branch 'master' into abo_waypoint_tracking
This commit is contained in:
breadoven
GitHub
commit
67adc42e75
61 changed files with 922 additions and 644 deletions
|
|
@ -36,6 +36,12 @@ Or using the speed to change profiles. In this example:
|
|||
|
||||
[](https://i.imgur.com/WjkuhhW.png)
|
||||
|
||||
#### Configurator use with profile changing logic.
|
||||
|
||||
If you have logic conditions that change the profiles. You may find that if you manually change the profile using the drop down boxes in the top right of Configurator; that they switch back to a different profile. This is because the logic conditions are still running in the background. If this is the case, the simplest solutuion is to temporarily disable the switches that trigger the `set profile` operations. Remember to re-enable these switches after you have made your changes.
|
||||
|
||||
[](https://i.imgur.com/AeH9ll7.png)
|
||||
|
||||
## Profile Contents
|
||||
The values contained within a profile can be seen by using the CLI `dump profile` command.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,6 +9,8 @@ There are 2 basic types of receivers:
|
|||
|
||||
## PPM Receivers
|
||||
|
||||
**Only supported in inav 3.x and below**
|
||||
|
||||
PPM is sometimes known as PPM SUM or CPPM.
|
||||
|
||||
12 channels via a single input pin, not as accurate or jitter free as methods that use serial communications, but readily available.
|
||||
|
|
|
|||
|
|
@ -362,16 +362,6 @@ Selection of baro hardware. See Wiki Sensor auto detect and hardware failure det
|
|||
|
||||
---
|
||||
|
||||
### baro_median_filter
|
||||
|
||||
3-point median filtering for barometer readouts. No reason to change this setting
|
||||
|
||||
| Default | Min | Max |
|
||||
| --- | --- | --- |
|
||||
| ON | OFF | ON |
|
||||
|
||||
---
|
||||
|
||||
### bat_cells
|
||||
|
||||
Number of cells of the battery (0 = auto-detect), see battery documentation. 7S, 9S and 11S batteries cannot be auto-detected.
|
||||
|
|
@ -762,6 +752,16 @@ Defines the type of stage 1 D-term LPF filter. Possible values: `PT1`, `BIQUAD`,
|
|||
|
||||
---
|
||||
|
||||
### dynamic_gyro_notch_3d_q
|
||||
|
||||
Q factor for 3D dynamic notches
|
||||
|
||||
| Default | Min | Max |
|
||||
| --- | --- | --- |
|
||||
| 200 | 1 | 1000 |
|
||||
|
||||
---
|
||||
|
||||
### dynamic_gyro_notch_enabled
|
||||
|
||||
Enable/disable dynamic gyro notch also known as Matrix Filter
|
||||
|
|
@ -782,6 +782,16 @@ Minimum frequency for dynamic notches. Default value of `150` works best with 5"
|
|||
|
||||
---
|
||||
|
||||
### dynamic_gyro_notch_mode
|
||||
|
||||
Gyro dynamic notch type
|
||||
|
||||
| Default | Min | Max |
|
||||
| --- | --- | --- |
|
||||
| 2D | | |
|
||||
|
||||
---
|
||||
|
||||
### dynamic_gyro_notch_q
|
||||
|
||||
Q factor for dynamic notches
|
||||
|
|
@ -2952,6 +2962,16 @@ Dive angle that airplane will use during final landing phase. During dive phase,
|
|||
|
||||
---
|
||||
|
||||
### nav_fw_launch_abort_deadband
|
||||
|
||||
Launch abort stick deadband in [r/c points], applied after r/c deadband and expo. The Roll/Pitch stick needs to be deflected beyond this deadband to abort the launch.
|
||||
|
||||
| Default | Min | Max |
|
||||
| --- | --- | --- |
|
||||
| 100 | 2 | 250 |
|
||||
|
||||
---
|
||||
|
||||
### nav_fw_launch_accel
|
||||
|
||||
Forward acceleration threshold for bungee launch of throw launch [cm/s/s], 1G = 981 cm/s/s
|
||||
|
|
@ -3012,6 +3032,16 @@ Launch idle throttle - throttle to be set before launch sequence is initiated. I
|
|||
|
||||
---
|
||||
|
||||
### nav_fw_launch_manual_throttle
|
||||
|
||||
Allows launch with manually controlled throttle. INAV only levels wings and controls climb pitch during launch. Throttle is controlled directly by throttle stick movement. IF USED WITHOUT A GPS LOCK plane must be launched immediately after throttle is increased to avoid issues with climb out stabilisation and the launch ending sooner than expected (launch end timer starts as soon as the throttle stick is raised).
|
||||
|
||||
| Default | Min | Max |
|
||||
| --- | --- | --- |
|
||||
| OFF | OFF | ON |
|
||||
|
||||
---
|
||||
|
||||
### nav_fw_launch_max_altitude
|
||||
|
||||
Altitude (centimeters) at which LAUNCH mode will be turned off and regular flight mode will take over [0-60000].
|
||||
|
|
@ -5052,13 +5082,33 @@ Exposition value used for the PITCH/ROLL axes by all the stabilized flights mode
|
|||
|
||||
---
|
||||
|
||||
### rc_filter_frequency
|
||||
### rc_filter_auto
|
||||
|
||||
When enabled, INAV will set RC filtering based on refresh rate and smoothing factor.
|
||||
|
||||
| Default | Min | Max |
|
||||
| --- | --- | --- |
|
||||
| OFF | OFF | ON |
|
||||
|
||||
---
|
||||
|
||||
### rc_filter_lpf_hz
|
||||
|
||||
RC data biquad filter cutoff frequency. Lower cutoff frequencies result in smoother response at expense of command control delay. Practical values are 20-50. Set to zero to disable entirely and use unsmoothed RC stick values
|
||||
|
||||
| Default | Min | Max |
|
||||
| --- | --- | --- |
|
||||
| 50 | 0 | 100 |
|
||||
| 50 | 15 | 250 |
|
||||
|
||||
---
|
||||
|
||||
### rc_filter_smoothing_factor
|
||||
|
||||
The RC filter smoothing factor. The higher the value, the more smoothing but also the more delay in response. Value 1 sets the filter at half the refresh rate. Value 100 sets the filter to aprox. 10% of the RC refresh rate
|
||||
|
||||
| Default | Min | Max |
|
||||
| --- | --- | --- |
|
||||
| 30 | 1 | 100 |
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -148,7 +148,7 @@ It is unlikely that the typical user will need to employ these options, other th
|
|||
* Configure `cmake` to use `ninja` as the build system
|
||||
|
||||
```
|
||||
cd buid
|
||||
cd build
|
||||
# add other cmake options as required.
|
||||
cmake -GNinja ..
|
||||
```
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# General Info
|
||||
|
||||
This is a guide on how to use Windows MSYS2 distribution and building platform to build iNav firmware. This environment is very simple to manage and does not require installing docker for Windows which may get in the way of VMWare or any other virtualization software you already have running for other reasons. Another benefit of this approach is that the compiler runs natively on Windows, so performance is much better than compiling in a virtual environment or a container. You can also integrate with whatever IDE you are using to make code edits and work with github, which makes the entire development and testing workflow a lot more efficient. In addition to MSYS2, this build environment also uses Arm Embedded GCC tolkit from The xPack Project, which provides many benefits over the toolkits maintained by arm.com
|
||||
This is a guide on how to use Windows MSYS2 distribution and building platform to build INAV firmware. This environment is very simple to manage and does not require installing docker for Windows which may get in the way of VMWare or any other virtualization software you already have running for other reasons. Another benefit of this approach is that the compiler runs natively on Windows, so performance is much better than compiling in a virtual environment or a container. You can also integrate with whatever IDE you are using to make code edits and work with github, which makes the entire development and testing workflow a lot more efficient. In addition to MSYS2, this build environment also uses Arm Embedded GCC tolkit from The xPack Project, which provides many benefits over the toolkits maintained by arm.com
|
||||
|
||||
Some of those benefits are described here:
|
||||
|
||||
|
|
@ -38,11 +38,18 @@ cd /c/Workspace
|
|||
# you can also check out your own fork here which makes contributing easier
|
||||
git clone https://github.com/iNavFlight/inav
|
||||
cd inav
|
||||
# switch to release you want or skip next 2 lines if you want latest
|
||||
git fetch origin
|
||||
git checkout -b release_2.6.1 origin/release_2.6.1
|
||||
```
|
||||
Now create the build and xpack directories and get the toolkit version you need for your inav version
|
||||
|
||||
(Optional) Switch to a release instead of master
|
||||
```
|
||||
git fetch origin
|
||||
# on the next line, tags/5.0.0 is the release's tag, and local_5.0.0 is the name of a local branch you will create.
|
||||
# tags can be found on https://github.com/iNavFlight/inav/tags as well as the releases page
|
||||
git checkout tags/5.0.0 -b local_5.0.0
|
||||
# you can also checkout with a branch if applicable:
|
||||
# git checkout -b release_5.1.0 origin/release_5.1.0
|
||||
```
|
||||
Now create the build and xpack directories and get the toolkit version you need for your INAV version
|
||||
```
|
||||
mkdir build
|
||||
cd build
|
||||
|
|
@ -54,13 +61,13 @@ This will give you the version you need for any given release or master branch.
|
|||
|
||||
https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/releases/
|
||||
```
|
||||
# for version 2.6.1, version needed is 9.2.1
|
||||
wget https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/releases/download/v9.2.1-1.1/xpack-arm-none-eabi-gcc-9.2.1-1.1-win32-x64.zip
|
||||
unzip xpack-arm-none-eabi-gcc-9.2.1-1.1-win32-x64.zip
|
||||
# for INAV version 5.0.0, toolchain version needed is 10.2.1
|
||||
wget https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/releases/download/v10.2.1-1.1/xpack-arm-none-eabi-gcc-10.2.1-1.1-win32-x64.zip
|
||||
unzip xpack-arm-none-eabi-gcc-10.2.1-1.1-win32-x64.zip
|
||||
```
|
||||
This is important, put the toolkit first before your path so that it is picked up ahead of any other versions that may be present on your system
|
||||
```
|
||||
export PATH=/c/Workspace/xpack/xpack-arm-none-eabi-gcc-9.2.1-1.1/bin:$PATH
|
||||
export PATH=/c/Workspace/xpack/xpack-arm-none-eabi-gcc-10.2.1-1.1/bin:$PATH
|
||||
cd /c/Workspace/inav/build
|
||||
```
|
||||
You may need to run rm -rf * in build directory if you had any failed previous runs now run cmake
|
||||
|
|
@ -68,13 +75,13 @@ You may need to run rm -rf * in build directory if you had any failed previous r
|
|||
# while inside the build directory
|
||||
cmake ..
|
||||
```
|
||||
Once that's done you can compile the firmware for your controller
|
||||
Once that's done you can compile the firmware for your flight controller
|
||||
```
|
||||
make DALRCF405
|
||||
```
|
||||
To get a list of available targets in iNav, see the target src folder
|
||||
https://github.com/tednv/inav/tree/master/src/main/target
|
||||
To get a list of available targets in INAV, see the target src folder
|
||||
[https://github.com/tednv/inav/tree/master/src/main/target](https://github.com/inavflight/inav/tree/master/src/main/target)
|
||||
|
||||
The generated hex file will be in /c/Workspace/inav/build folder
|
||||
|
||||
At the time of writting this document, I believe this is the fastest, easiest, and most efficient Windows build environment that is available. I have used this approach several years ago and was very happy with it building iNav 2.1 and 2.2, and now I'm getting back into it so figured I would share my method
|
||||
At the time of writting this document, I believe this is the fastest, easiest, and most efficient Windows build environment that is available. I have used this approach several years ago and was very happy with it building INAV 2.1 and 2.2, and now I'm getting back into it so figured I would share my method
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue