merged changes from Issue020_ThrottleWarning

based on current next branch, includes all changes from old
ThrottleWarning branch.

Solves issue 020: Throttle warning if P1-P3 is selected as Thr source.
Adds Turnigy TransmitterFix option
code savings:
120 bytes without Transmitter fix
4 bytes but 1 more data if Transmitter Fix is activated.

Added make option TURNIGY_TRANSMITTER_FIX for this purpose
TURNIGY_TRANSMITTER_FIX = NO   is default
set to YES for new Turnigy9x transmitter which transmits even no pulses
are generated.
This commit is contained in:
openfsguruh
2014-02-10 20:51:25 +01:00
parent 1a6832c83a
commit da23a624dc
3 changed files with 188 additions and 39 deletions
+16
View File
@@ -67,6 +67,14 @@ EXT = STD
# Values = YES, NO, CHOICE
FAI = NO
# the latests deliveries for Turnigy 9x transmitters (since 2 years now, 2014) do not stop sending if no pulses are generated.
# This fact totally breaks the nice throttle and switch warning concept, because even we prevent sending pulses the
# transmitter modul ignores this, and continous to send the last value or 0 at beginning. And 0 means in the middle of throttle -> 50%.
# To cope with this situation, we need a new concept how to handle throttle and switch warnings.
# if you have a 0 value (50% ) for throttle, while throttle warning is active, you should activate this switch
# Values = YES, NO
TURNIGY_TRANSMITTER_FIX = NO
# Enable heli menu
# Values = YES, NO
HELI = NO
@@ -671,6 +679,10 @@ ifeq ($(PCB), TARANIS)
CPPSRC += protocols/hubsan.cpp
CPPSRC += targets/taranis/a7105_driver.cpp
endif
ifeq ($(TURNIGY_TRANSMITTER_FIX), YES)
$(error TURNIGY_TRANSMITTER_FIX is not yet implemented for Taranis. If this is actually needed, getSwitch() needs to be modified)
endif
endif
CC = $(TRGT)gcc
@@ -743,6 +755,10 @@ ifeq ($(NAVIGATION), ROTENC)
CPPDEFS += -DROTARY_ENCODER_NAVIGATION
endif
ifeq ($(TURNIGY_TRANSMITTER_FIX), YES)
CPPDEFS += -DINPUT_WARNINGS_GENERATE_SIM_DATA
endif
ifeq ($(AUTOSWITCH), YES)
CPPDEFS += -DAUTOSWITCH
endif