This prevents arming after connecting a battery when the throttle is in
low; when using a switch to arm and when the switch is left in the ON
position.
The previous solution was flawed because of the way rc input is handled.
This also removes an extra test of rcOptions by re-arranging the logic
that handles arming/disarming via a switch.
Each flag was previously a whole byte, now all of the flags only take up
4 bytes as they are represented by bit masks.
This is cleaner because the different kind of flags are now separated.
Additionally this changes the behaviour of arming slightly. When using
a switch to arm the aircraft will not arm unless the switch has been in
the off state once. This prevents arming if you power the aircraft with
a low throttle and the switch in the on position.
follows the pattern that HoTT and FrSky use.
Previously MSP telemetry was actually output on the MSP port, NOT the
telemetry port.
Baudrate for MSP telemetry currently fixed at 19200.
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
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.
Work in progress. In testing using bluetooth on uart2 and uart1
connected to configurator it was observed that there is corrupted
responses being sent via uart2 - ez-gui shows some garbled data for the
box names. updates appear sluggish in ez-gui but some correct data is
getting through.
Enabled with:
set serial_port_2_scenario = 8
save
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.
This has highlighted that the existing codebase is quite targeted
towards systems that use USART1 and 2. Annoyingly the inverter is on
USART1 and the sbus code requires callbacks so still won't work yet.
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
Altitude-Hold, Better PPM support. Sonar alt-hold. Current sensor
FrSky telemetry. Cli cleanup (dump profile/master). Support for SBUS
inverter. Smaller code size - using GCC Link Time Optimisation and GCC
nano specs. Updated WS281 LED Support.
screen on OpenTX) - it was disabled in baseflight commits
a753661c23c428ede8c2b72e95d3e31f6c8b894e and removed in
4ae03bb00e5616796989255d4101c4ed51162d50
Cleanup '...' strings to reduce binary size. Change version
information.
With this change it's much more obvious what is and what is not included
in a profile.
Examples:
dump
dump profile
dump master
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.
This enables the user to type "get variablename" in the CLI, which then shows the value of that variable (or a message saying "Variable 'variablename' not found").
This is easier for the user when they just want to see a single variable, instead of typing 'dump' and then having to parse a big long list of data. It is also more intuitive than typing 'set variablename', as this feels unsafe.
Dominic Clifton
dongie
Ben Hitchcock