2.9.1 upgrade, add ranger, churn

Keeping global vars bound to dials in flight modes has downside
of resulting in change to model yaml that presists and produces
more churn
This commit is contained in:
Bryce Allen
2023-10-19 10:56:16 -04:00
parent 637c2daf9b
commit 933894db05
6 changed files with 5329 additions and 5396 deletions
+1233 -1281
View File
File diff suppressed because it is too large Load Diff
+1251 -1299
View File
File diff suppressed because it is too large Load Diff
+30 -1
View File
@@ -1,4 +1,4 @@
semver: 2.9.0
semver: 2.9.1
header:
name: "iNav"
modelId:
@@ -184,6 +184,21 @@ mixData:
speedUp: 0
speedDown: 0
name: ""
-
weight: 100
destCh: 13
srcRaw: I13
carryTrim: 0
mixWarn: 0
mltpx: ADD
offset: 0
swtch: "NONE"
flightModes: 000000000
delayUp: 0
delayDown: 0
speedUp: 0
speedDown: 0
name: ""
-
weight: 100
destCh: 19
@@ -665,6 +680,20 @@ expoData:
weight: 100
name: ""
offset: 0
-
mode: 3
scale: 0
trimSource: 0
srcRaw: POT1
chn: 13
swtch: "NONE"
flightModes: 000000000
weight: 100
name: ""
offset: 0
curve:
type: 1
value: 0
customFn:
0:
swtch: "SD0"
+4 -4
View File
@@ -1,4 +1,4 @@
semver: 2.9.0
semver: 2.9.1
header:
name: "DFlyByme"
modelId:
@@ -984,13 +984,13 @@ flightModeData:
0:
val: -100
1:
val: 75
val: 56
2:
val: 25
val: 24
3:
val: 0
4:
val: 70
val: 100
5:
val: 0
6: