docs:config.h
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
docs:config.h [2017/10/21 01:45] silverxxx |
docs:config.h [2017/10/31 11:50] (current) silverxxx |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== Config.h settings ==== | + | ====== Config.h settings |
| - | Settings found in config.h are used for customizing quadcopter flight settings and a number of software settings. | + | Settings found in config.h are used for customizing |
| - | ==== Flight control settings | + | ==== Rate ==== |
| - | + | ||
| - | This settings comprise of rate control, high and low, expo, if needed to be performed by quad itself ( for stock tx) and switch config, mainly for level mode switching. | + | |
| - | + | ||
| - | === Rate === | + | |
| The rate is changed by the following lines in config.h file. The unit is degrees / second. The number is the rotation rate at max stick deflection, for example 360 would perform a full turn in 1 second. | The rate is changed by the following lines in config.h file. The unit is degrees / second. The number is the rotation rate at max stick deflection, for example 360 would perform a full turn in 1 second. | ||
| Line 24: | Line 20: | ||
| </ | </ | ||
| - | === Switches (auxiliary channels) === | + | ==== Expo ==== |
| + | |||
| + | Normally, expo would be set in the transmitter, | ||
| + | |||
| + | < | ||
| + | //#define DISABLE_EXPO | ||
| + | |||
| + | #define EXPO_XY 0.3 | ||
| + | #define EXPO_YAW 0.3 | ||
| + | </ | ||
| + | |||
| + | Range is 0.0 - 1.0, where zero is linear. Higher numbers are less sensitive near center, values 0.6 - 0.8 are commonly used ( 60% - 80% ) | ||
| + | |||
| + | ==== Switches (auxiliary channels) | ||
| Switches/ | Switches/ | ||
| Line 35: | Line 44: | ||
| // level / acro mode switch | // level / acro mode switch | ||
| - | // CH_FLIP | + | // CH_FLIP - flip |
| - | // CH_EXPERT | + | // CH_EXPERT - expert |
| - | // CH_HEADFREE | + | // CH_HEADFREE - headfree |
| - | // CH_RTH | + | // CH_RTH - headingreturn |
| - | // CH_AUX1 | + | // CH_AUX1 - AUX1 ( gestures <<v and>> |
| - | // CH_PIT_TRIM | + | // CH_PIT_TRIM - Pitch trims ***1** |
| - | // CH_RLL_TRIM | + | // CH_RLL_TRIM - Roll trims ***1** |
| - | // CH_THR_TRIM | + | // CH_THR_TRIM - Throttle trims ***1** |
| - | // CH_YAW_TRIM | + | // CH_YAW_TRIM - Yaw trims ***1** |
| - | // CH_INV | + | // CH_INV - Inverted mode |
| - | // CH_VID | + | // CH_VID |
| - | // CH_PIC | + | // CH_PIC |
| - | // CH_ON - 10 - on always | + | // CH_ON - on always |
| - | // CH_OFF | + | // CH_OFF - off always |
| - | // | + | |
| // devo can use DEVO_CHAN_5 - DEVO_CHAN_10 | // devo can use DEVO_CHAN_5 - DEVO_CHAN_10 | ||
| #define RATES CH_EXPERT | #define RATES CH_EXPERT | ||
| - | |||
| #define LEVELMODE CH_AUX1 | #define LEVELMODE CH_AUX1 | ||
| - | |||
| #define STARTFLIP CH_OFF | #define STARTFLIP CH_OFF | ||
| + | #define LEDS_ON CH_FLIP | ||
| - | # | + | // ***1** |
| </ | </ | ||
| Line 64: | Line 72: | ||
| Available channels depend on the //radio protocol// selected, the ones described are for Bayang protocol ( recomended ) | Available channels depend on the //radio protocol// selected, the ones described are for Bayang protocol ( recomended ) | ||
| - | + | === Stock tx === | |
| - | **Stock tx** | + | |
| The trim buttons do not do anything in the stock tx. To use the trims for controlling a function, set the function channel to the trim (such as CH_PIT_TRIM - pitch trims) and enable "# | The trim buttons do not do anything in the stock tx. To use the trims for controlling a function, set the function channel to the trim (such as CH_PIT_TRIM - pitch trims) and enable "# | ||
| //Do not enable " | //Do not enable " | ||
| + | === Devo tx === | ||
| - | **Devo tx** | + | Silverware supports setting |
| - | + | ||
| - | In the above code the level function is set to " | + | |
| - | + | ||
| - | The devo channels are assigned | + | |
| < | < | ||
| - | CHANNEL1 | + | #define LEDS_ON |
| - | CHANNEL2, | + | |
| - | CHANNEL3, | + | |
| - | CHANNEL4, | + | |
| - | DEVO_CHAN_5 | + | |
| - | DEVO_CHAN_6 | + | |
| - | DEVO_CHAN_7 | + | |
| - | DEVO_CHAN_8 | + | |
| - | | + | |
| - | DEVO_CHAN_10 | + | |
| - | CHANNEL11 | + | |
| </ | </ | ||
| - | |||
| - | Silverware also supports to set simply a channel number as numbered in DeviationTX:< | ||
| For the multimodule, | For the multimodule, | ||
| - | ==== Other settings | + | ==== Auto throttle feature |
| - | + | ||
| - | **Auto throttle feature:** | + | |
| The auto throttle will keep a constant upwards thrust as the quad leans in one direction. Used in level mode, usually. | The auto throttle will keep a constant upwards thrust as the quad leans in one direction. Used in level mode, usually. | ||
| Line 107: | Line 97: | ||
| </ | </ | ||
| - | **Lower throttle feature** | + | ==== Lower throttle feature |
| - | With this option enabled, the quadcopter will lower the throttle in order to maintain better control near full throttle. Without it (default) the quadcopter will usually lean slightly in one direction at full throttle, as there may not be enough control ability. (the motors can't increase over maximum) | + | With this option enabled, the quadcopter will lower the throttle in order to maintain better control near full throttle. Without it (default) the quadcopter will usually lean slightly in one direction at full throttle, as there may not be enough control ability. ( at least one motor is producing |
| - | < | + | Usually, other firmwares have this option enabled, but in silverware it is optional, because it results in a loss of thrust at full throttle, which small brushed quads most certainly can do without. |
| - | #define MIX_LOWER_THROTTLE | + | |
| - | //#define MIX_INCREASE_THROTTLE | + | |
| - | </ | + | |
| - | **Motor filter feature** | + | An opposite option, increase thrust, is of use when throttle is near zero, and will improve control in such situations. The increase throttle option should be used with care while tuning quadcopters, |
| - | The motor filter is a 3 tap hanning fir filter that is applied to the motor output. Enabled by default, as it uses little resources. | + | The " |
| < | < | ||
| - | # | + | # |
| + | //#define MIX_INCREASE_THROTTLE | ||
| + | |||
| + | //#define MIX_LOWER_THROTTLE_3 | ||
| + | //#define MIX_INCREASE_THROTTLE_3 | ||
| </ | </ | ||
| - | **Throttle transient compensation | + | ==== Throttle transient compensation |
| - | The TTCF feature improves throttle response of the quadcopter. The curve has been measured for 6mm motors, and it may not work the same with other motors. With this feature on, the quadcopter will react faster to throttle changes. | + | The TTCF feature improves throttle response of the quadcopter. The curve has been measured for 6mm motors, and it may not work the same with other motors. The factor can be adjusted also by adding the line to config.h. With this feature on, the quadcopter will react faster to throttle changes. |
| - | This feature only works on the throttle stick, it does not affect controls in any other way. | + | This feature only works on the throttle stick, it does not affect controls in any other way. However, the increase motor use may reduce flight time. |
| < | < | ||
| #define THROTTLE_TRANSIENT_COMPENSATION | #define THROTTLE_TRANSIENT_COMPENSATION | ||
| + | |||
| + | // this line may be added | ||
| + | #define THROTTLE_TRANSIENT_COMPENSATION_FACTOR 7.0 | ||
| </ | </ | ||
| - | **Gyro lpf filter (software)** | + | ==== Gyro lpf filter (software) |
| The software lpf filter is a custom gyro filter, additional to the hardware filter which is present in the gyro device. The hardware filter is set around 43Hz by default, but for additional vibration removal, a software filter can be added. | The software lpf filter is a custom gyro filter, additional to the hardware filter which is present in the gyro device. The hardware filter is set around 43Hz by default, but for additional vibration removal, a software filter can be added. | ||
| Changing the filters affects the tuning of the pids, it's a good idea to consider the filter before tuning. | Changing the filters affects the tuning of the pids, it's a good idea to consider the filter before tuning. | ||
| + | |||
| + | The last 2 filters have custom frequency, and they also account for variable sample rate, or different from default. They are recommended with gcc as the loop time is exceeded there. All other filters are calculated for a loop time of 1Khz ( 1000 uS). | ||
| < | < | ||
| Line 150: | Line 146: | ||
| //#define SOFT_LPF_4TH_160HZ | //#define SOFT_LPF_4TH_160HZ | ||
| //#define SOFT_LPF_4TH_250HZ | //#define SOFT_LPF_4TH_250HZ | ||
| + | //#define SOFT_LPF_1ST_HZ 100 | ||
| + | //#define SOFT_LPF_2ST_HZ 100 | ||
| //#define SOFT_LPF_NONE | //#define SOFT_LPF_NONE | ||
| </ | </ | ||
| - | **Gyro lpf filter (hardware)** | + | ==== Gyro lpf filter (hardware) |
| - | The hardware gyro lpf filter is part of the gyro integrated circuit. It's setting changes the frequency of the internal filter. The internal filter also has a latency which may affect pid P and D terms. A lower latency may be better, however vibration will limit the usefulness of higher gyro frequencies. | + | The hardware gyro lpf filter is part of the gyro integrated circuit. It's setting changes the frequency of the internal filter. The internal filter also has a latency which may affect pid P and D terms. A lower latency may be better, however vibration will limit the usefulness of higher gyro frequencies. The " |
| < | < | ||
| Line 162: | Line 160: | ||
| // gyro filter 2 = 92hz delay 3.9mS | // gyro filter 2 = 92hz delay 3.9mS | ||
| // gyro filter 3 = 41hz delay 5.9mS (Default) | // gyro filter 3 = 41hz delay 5.9mS (Default) | ||
| - | // gyro filter 4 = 20hz | ||
| - | // gyro filter 5 = 10hz | ||
| - | // gyro filter 6 = 5hz | ||
| - | // gyro filter 7 = 3600hz delay 0.17mS | ||
| #define GYRO_LOW_PASS_FILTER 3 | #define GYRO_LOW_PASS_FILTER 3 | ||
| </ | </ | ||
| + | |||
| + | ==== Motor filter feature ==== | ||
| + | |||
| + | There are 2 motor filtering options, a hanning 3 tap filter which reduces very high frequencies only, and a 1st order low pass filter that uses a coefficient as a setting. The motor filter has effects on pid tuning similar to those of the gyro low pass filters. | ||
| + | |||
| + | < | ||
| + | // enable motor filter - select one | ||
| + | // motorfilter1: | ||
| + | // motorfilter2: | ||
| + | //#define MOTOR_FILTER | ||
| + | #define MOTOR_FILTER2_ALPHA 0.3 | ||
| + | </ | ||
| + | |||
| + | ==== Motor curve ==== | ||
| + | |||
| + | In silverware, the motors are linearized so that the resulting thrust is linear. the curves are obtained by measuring the motors and propellor combination. Although it's not necessary to know the curve, using a curve allows the pids to be consistent across the throttle range. | ||
| + | |||
| + | Motor linearity changes somewhat with pwm frequency, and for this reason each curve also has a frequency at which it was measured. | ||
| + | |||
| + | < | ||
| + | // pwm frequency for motor control | ||
| + | #define PWMFREQ 24000 | ||
| + | |||
| + | // motor curve to use | ||
| + | // the pwm frequency has to be set independently | ||
| + | //#define MOTOR_CURVE_NONE | ||
| + | //#define MOTOR_CURVE_85MM_32KHZ | ||
| + | //#define BOLDCLASH_716MM_8K | ||
| + | #define BOLDCLASH_716MM_24K | ||
| + | </ | ||
| + | |||
| + | ==== Other settings ==== | ||
| + | |||
| + | There are a number of other settings in config.h, as well as in some other files. They are less common, and not described in this document. Additionally, | ||
docs/config.h.1508543150.txt.gz · Last modified: 2017/10/21 01:45 by silverxxx
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
