* Renamed several methods and variables so they make more sense.
* Move more altitude hold related code out of imu.c/h into
altitudehold.c/h.
* Fixed a unsigned integer being using instead of an signed integer in
the throttle calculation code.
series development board.
These boards can be picked up for less than $11, coupled with a 10DOF
sensor board they make a great development platform or cheap expandable
FC.
Pretty much all pins are available to be used, unlike on the less
capable and more expensive OLIMEXINO.
just use it in-place. This saves ~308bytes of memory.
Prior to this there were 4 profiles in ram all the time, the 3 main
profiles and a copy of one of them.
This commit was aided by a side effect of the work done to clean up the
output of the cli dump command since it is now easy to conditionally
apply the changes to the memory addressed used to read/write cli
variables. See 8c3a869251.
Conflicts:
src/main/io/serial_msp.c
This allows sonar to be used at the same time as parallel PWM for the receiver. If the RX_PARALLEL_PWM feature is enabled, then the sonar system uses motor ports 5 and 6, otherwise it uses receiver pins 7 and 8.
gps.c now only has code that deals with gps hardware, state and
messaging.
navigation.c now only has code dealing with flight
navigation/waypoints/home/hold/etc
When changing profiles with the sticks, CleanFlight was beeping 0 times for profile
1, once for profile 2, and twice for profile 3. This wasn't intuitive, and was
different to how Baseflight beeps when changing profiles.
This change makes baseflight give the same number of beeps as the profile number
that you change into.
set the variable accz_lpf_cutoff to the desired cutoff frequency
this can help to make althold smoother on copters with lots of
vibrations
Conflicts:
src/cli.c
src/config.c
src/imu.c
src/mw.h
Added documentation.
Added LED_STRIP feature, can only be enabled under certain circumstances
depending on target due to pin/timer mappings - see documentation.
using different values in different.
The cause was the IMU init code which triggered calculation was never
called after switching profiles - it couldn't be called twice because it
also initialised the compass.
The solution was to decouple compass initialisation from IMU
initialisation and extract the code to recalculate throttle angle scale
to a new method.
The MSP is changed in a way that might provide some backwards
compatibility. The first 4 channels are sent/read as before followed by
the next 4 channels.
If I client ignores extra data received it should be backwards
compatible.
Clients can looks for the new capability bit which indicates the MSP
protocol supports AUX 1-8.
It was noticed that GPS startup time increased when the change was made
from using EGNOS by default to using AUTO by default.
The default is still AUTO but faster GPS startup times may be achieved
by telling the GPS receiver what region you are in.
This also removes more unfinished MTK gps provider support.
