-Fix incorrect formula in example section of charger method calibration
-Fix incorrect verb tense from "mAh draw" to "mAh drawn"
-Simplify instruction steps to be more direct
-Replace abstract example calculation values with rounded numbers to make formula more obvious for humans
-Make formula placeholder names to match those used in Configurator
-Cross fingers that is it so clear now that not even a grandmother would try to change it again ;)
Markdown links cannot have actual spaces in the filename. Use URL-encoded
spaces (%20) instead.
robo-fixed using:
sed -i -e 's/\(]([^ )]*\) \([^"]\)/\1%20\2/g' **/*.md
If you don't use zhell, you may need to customize the ** part of that command.
A periodic glitch happens on AUX channels when using OneShot on CC3D,
especially with faster update loops. This is caused by a race condition
while forcing timer overflows and sharing the timer for PPM capture.
It causes the craft the fall out of the sky when using a switch to arm.
* Remap PPM in from S1_IN to S6_IN
* Remap RSSI_ADC from S6_IN to S3_IN
* Block PWM12/S6_OUT from being used with Oneshot/brushed motors so
TIM2 (PPM_IN timer) doesn't change prescaler or is manually overflowed
* Allow only one feature out of SOFTSERIAL/RSSI_ADC/SONAR, since they
will now share the same pin
* Update docs to reflect port changes and restrictions
This fixescleanflight/cleanflight#1748,
fixesborisbstyle/betaflight#64, fixesborisbstyle/betaflight#127
fix BP6
Updated SPI driver (SPI3 on F3 targets)
AK8963 Mag support (part of MPU9250)
MPU9250 SPI support via MPU6500 driver
Updated LED driver for alternative LED sets
Enable gyro intterupt for AlienFlight F3 targets
Update AlienWii/AlienFlight documentation
Rename AlienWii to AlienFlight
It was a little bit hard to read with only two paragraphs, and looking at the raw .md file it was clear that having just two paragraphs was not the original intention.
It was a little bit hard to read with only two paragraphs, and looking at the raw .md file it was clear that having just two paragraphs was not the original intention.
- add two new CLI paramaters "gtune_settle_time" and
"gtune_average_cycles"
- the settle time is not depending on looptime anymore
- updated default setting to cover e wider range of copters
- remove lower limit for P value for CLI (Zero P is now posible, but
schould be used with care)
- Documentation updates
G-Tune documentation update
G-Tune will only activated and deactivated when armed.
G-Tune should deactivated while the copter is airborne.
Tuned P values will only be stored when G-Tune is enabled while disarmed
and G-Tune was used before.
Enabled for NAZE, ALIENWWIIF1 and ALIENWIIF3 targets
Implement G-Tune for all PID controllers
The G-Tune tuning results will be save if G-Tune mode will be disabled
during copter is disarmed.
Update PID controller and G-Tune documentation
