fly/A320-family
1
0
Fork 0
Code Activity
A320-family/Nasal/Systems/FADEC/engines-common.nas

140 lines
6.2 KiB
Text
Raw Normal View History

A320-family fork
2019-10-14 16:48:35 +00:00
# A3XX Engine Control
# Joshua Davidson (Octal450)
GIT: Update 2019 to 2020
2020-04-18 05:36:46 +00:00
# Copyright (c) 2020 Josh Davidson (Octal450)
A320-family fork
2019-10-14 16:48:35 +00:00
Update engine nasal files to pts / getValue()
2020-11-22 22:00:21 +00:00
var manStart = [props.globals.initNode("/controls/engines/engine[0]/man-start", 0, "BOOL"),props.globals.initNode("/controls/engines/engine[1]/man-start", 0, "BOOL")];
var lastIgniter = [props.globals.getNode("/controls/engines/engine[0]/last-igniter"),props.globals.initNode("/controls/engines/engine[1]/last-igniter")];
var igniterA = [props.globals.initNode("/controls/engines/engine[0]/igniter-a", 0, "BOOL"),props.globals.initNode("/controls/engines/engine[1]/igniter-a", 0, "BOOL")];
var igniterB = [props.globals.initNode("/controls/engines/engine[0]/igniter-b", 0, "BOOL"),props.globals.initNode("/controls/engines/engine[1]/igniter-b", 0, "BOOL")];
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
if (pts.Options.eng.getValue() == "IAE") {
A320-family fork
2019-10-14 16:48:35 +00:00
io.include("engines-iae.nas");
} else {
io.include("engines-cfm.nas");
}
var eng_common_init = func {
Update engine nasal files to pts / getValue()
2020-11-22 22:00:21 +00:00
manStart[0].setValue(0);
manStart[1].setValue(0);
A320-family fork
2019-10-14 16:48:35 +00:00
}
Refactor more legacy
2020-07-26 12:43:14 +00:00
# Engine thrust commands
A320-family fork
2019-10-14 16:48:35 +00:00
var doIdleThrust = func {
Make the thrust detent bindings respect selected engines Now that PgUp/PgDn respect selected engines respects selected engines, make the TOGA, MCT/FLX and CL shortcuts do so as well. Idle binding is an exception, because both thrust levers must be set to idle for spoilers to deploy while one is enough to disengage the A/THR and you don't want to repeat TAM3054 just because you forgot the re-select both engines.
2020-02-15 21:30:45 +00:00
# Idle does not respect selected engines, because it is used to respond
# to "Retard" and both engines must be idle for spoilers to deploy
Refactor more legacy
2020-07-26 12:43:14 +00:00
pts.Controls.Engines.Engine.throttle[0].setValue(0.0);
pts.Controls.Engines.Engine.throttle[1].setValue(0.0);
A320-family fork
2019-10-14 16:48:35 +00:00
}
var doCLThrust = func {
Refactor more legacy
2020-07-26 12:43:14 +00:00
if (pts.Sim.Input.Selected.engine[0].getBoolValue()) {
pts.Controls.Engines.Engine.throttle[0].setValue(0.63);
Make the thrust detent bindings respect selected engines Now that PgUp/PgDn respect selected engines respects selected engines, make the TOGA, MCT/FLX and CL shortcuts do so as well. Idle binding is an exception, because both thrust levers must be set to idle for spoilers to deploy while one is enough to disengage the A/THR and you don't want to repeat TAM3054 just because you forgot the re-select both engines.
2020-02-15 21:30:45 +00:00
}
Refactor more legacy
2020-07-26 12:43:14 +00:00
if (pts.Sim.Input.Selected.engine[1].getBoolValue()) {
pts.Controls.Engines.Engine.throttle[1].setValue(0.63);
Make the thrust detent bindings respect selected engines Now that PgUp/PgDn respect selected engines respects selected engines, make the TOGA, MCT/FLX and CL shortcuts do so as well. Idle binding is an exception, because both thrust levers must be set to idle for spoilers to deploy while one is enough to disengage the A/THR and you don't want to repeat TAM3054 just because you forgot the re-select both engines.
2020-02-15 21:30:45 +00:00
}
A320-family fork
2019-10-14 16:48:35 +00:00
}
var doMCTThrust = func {
Refactor more legacy
2020-07-26 12:43:14 +00:00
if (pts.Sim.Input.Selected.engine[0].getBoolValue()) {
pts.Controls.Engines.Engine.throttle[0].setValue(0.80);
Make the thrust detent bindings respect selected engines Now that PgUp/PgDn respect selected engines respects selected engines, make the TOGA, MCT/FLX and CL shortcuts do so as well. Idle binding is an exception, because both thrust levers must be set to idle for spoilers to deploy while one is enough to disengage the A/THR and you don't want to repeat TAM3054 just because you forgot the re-select both engines.
2020-02-15 21:30:45 +00:00
}
Refactor more legacy
2020-07-26 12:43:14 +00:00
if (pts.Sim.Input.Selected.engine[1].getBoolValue()) {
pts.Controls.Engines.Engine.throttle[1].setValue(0.80);
Make the thrust detent bindings respect selected engines Now that PgUp/PgDn respect selected engines respects selected engines, make the TOGA, MCT/FLX and CL shortcuts do so as well. Idle binding is an exception, because both thrust levers must be set to idle for spoilers to deploy while one is enough to disengage the A/THR and you don't want to repeat TAM3054 just because you forgot the re-select both engines.
2020-02-15 21:30:45 +00:00
}
A320-family fork
2019-10-14 16:48:35 +00:00
}
var doTOGAThrust = func {
Refactor more legacy
2020-07-26 12:43:14 +00:00
if (pts.Sim.Input.Selected.engine[0].getBoolValue()) {
pts.Controls.Engines.Engine.throttle[0].setValue(1.00);
Make the thrust detent bindings respect selected engines Now that PgUp/PgDn respect selected engines respects selected engines, make the TOGA, MCT/FLX and CL shortcuts do so as well. Idle binding is an exception, because both thrust levers must be set to idle for spoilers to deploy while one is enough to disengage the A/THR and you don't want to repeat TAM3054 just because you forgot the re-select both engines.
2020-02-15 21:30:45 +00:00
}
Refactor more legacy
2020-07-26 12:43:14 +00:00
if (pts.Sim.Input.Selected.engine[1].getBoolValue()) {
pts.Controls.Engines.Engine.throttle[1].setValue(1.00);
Make the thrust detent bindings respect selected engines Now that PgUp/PgDn respect selected engines respects selected engines, make the TOGA, MCT/FLX and CL shortcuts do so as well. Idle binding is an exception, because both thrust levers must be set to idle for spoilers to deploy while one is enough to disengage the A/THR and you don't want to repeat TAM3054 just because you forgot the re-select both engines.
2020-02-15 21:30:45 +00:00
}
A320-family fork
2019-10-14 16:48:35 +00:00
}
# Reverse Thrust System
var toggleFastRevThrust = func {
Nasal fixup
2020-09-15 17:22:35 +00:00
if (pts.Systems.Thrust.state[0].getValue() == "IDLE" and pts.Systems.Thrust.state[1].getValue() == "IDLE" and pts.Controls.Engines.Engine.reverser[0].getValue() == 0 and pts.Controls.Engines.Engine.reverser[1].getValue() == 0 and pts.Gear.wow[1].getValue() == 1 and pts.Gear.wow[2].getValue() == 1) {
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
if (pts.Sim.Input.Selected.engine[0].getBoolValue()) {
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
interpolate("/engines/engine[0]/reverser-pos-norm", 1, 1.4);
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
pts.Controls.Engines.Engine.reverser[0].setValue(1);
pts.Controls.Engines.Engine.throttleRev[0].setValue(0.65);
pts.Fdm.JSBsim.Propulsion.Engine.reverserAngle[0].setValue(3.14);
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
}
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
if (pts.Sim.Input.Selected.engine[1].getBoolValue()) {
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
interpolate("/engines/engine[1]/reverser-pos-norm", 1, 1.4);
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
pts.Controls.Engines.Engine.reverser[1].setValue(1);
pts.Controls.Engines.Engine.throttleRev[1].setValue(0.65);
pts.Fdm.JSBsim.Propulsion.Engine.reverserAngle[1].setValue(3.14);
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
}
Nasal fixup
2020-09-15 17:22:35 +00:00
} else if (pts.Controls.Engines.Engine.reverser[0].getValue() == 1 or pts.Controls.Engines.Engine.reverser[1].getValue() == 1) {
A320-family fork
2019-10-14 16:48:35 +00:00
interpolate("/engines/engine[0]/reverser-pos-norm", 0, 1.0);
interpolate("/engines/engine[1]/reverser-pos-norm", 0, 1.0);
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
pts.Controls.Engines.Engine.throttleRev[0].setValue(0);
pts.Controls.Engines.Engine.throttleRev[1].setValue(0);
pts.Fdm.JSBsim.Propulsion.Engine.reverserAngle[0].setValue(0);
pts.Fdm.JSBsim.Propulsion.Engine.reverserAngle[1].setValue(0);
pts.Controls.Engines.Engine.reverser[0].setValue(0);
pts.Controls.Engines.Engine.reverser[1].setValue(0);
A320-family fork
2019-10-14 16:48:35 +00:00
}
}
var doRevThrust = func {
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
if (pts.Gear.wow[1].getValue() != 1 and pts.Gear.wow[2].getValue() != 1) {
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
# Can't select reverse if not on the ground
return;
}
Nasal fixup
2020-09-15 17:22:35 +00:00
if (pts.Sim.Input.Selected.engine[0].getBoolValue() and pts.Controls.Engines.Engine.reverser[0].getValue() == 1) {
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
var pos = pts.Controls.Engines.Engine.throttleRev[0].getValue();
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
if (pos < 0.649) {
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
pts.Controls.Engines.Engine.throttleRev[0].setValue(pos + 0.15);
A320-family fork
2019-10-14 16:48:35 +00:00
}
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
}
Nasal fixup
2020-09-15 17:22:35 +00:00
if (pts.Sim.Input.Selected.engine[1].getBoolValue() and pts.Controls.Engines.Engine.reverser[1].getValue() == 1) {
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
var pos = pts.Controls.Engines.Engine.throttleRev[1].getValue();
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
if (pos < 0.649) {
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
pts.Controls.Engines.Engine.throttleRev[1].setValue(pos + 0.15);
A320-family fork
2019-10-14 16:48:35 +00:00
}
}
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
Nasal fixup
2020-09-15 17:22:35 +00:00
if (pts.Sim.Input.Selected.engine[0].getBoolValue() and pts.Systems.Thrust.state[0].getValue() == "IDLE" and pts.Controls.Engines.Engine.reverser[0].getValue() == 0) {
A320-family fork
2019-10-14 16:48:35 +00:00
interpolate("/engines/engine[0]/reverser-pos-norm", 1, 1.4);
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
pts.Controls.Engines.Engine.throttleRev[0].setValue(0.05);
pts.Controls.Engines.Engine.reverser[0].setValue(1);
pts.Fdm.JSBsim.Propulsion.Engine.reverserAngle[0].setValue(3.14);
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
}
Nasal fixup
2020-09-15 17:22:35 +00:00
if (pts.Sim.Input.Selected.engine[1].getBoolValue() and pts.Systems.Thrust.state[1].getValue() == "IDLE" and pts.Controls.Engines.Engine.reverser[1].getValue() == 0) {
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
interpolate("/engines/engine[1]/reverser-pos-norm", 1, 1.4);
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
pts.Controls.Engines.Engine.throttleRev[1].setValue(0.05);
pts.Controls.Engines.Engine.reverser[1].setValue(1);
pts.Fdm.JSBsim.Propulsion.Engine.reverserAngle[1].setValue(3.14);
A320-family fork
2019-10-14 16:48:35 +00:00
}
}
var unRevThrust = func {
Nasal fixup
2020-09-15 17:22:35 +00:00
if (pts.Sim.Input.Selected.engine[0].getBoolValue() and pts.Controls.Engines.Engine.reverser[0].getValue() == 1) {
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
var pos = pts.Controls.Engines.Engine.throttleRev[0].getValue();
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
if (pos > 0.051) {
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
pts.Controls.Engines.Engine.throttleRev[0].setValue(pos - 0.15);
A320-family fork
2019-10-14 16:48:35 +00:00
} else {
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
interpolate("/engines/engine[0]/reverser-pos-norm", 0, 1.0);
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
pts.Controls.Engines.Engine.throttleRev[0].setValue(0);
pts.Controls.Engines.Engine.reverser[0].setValue(0);
pts.Fdm.JSBsim.Propulsion.Engine.reverserAngle[0].setValue(0);
A320-family fork
2019-10-14 16:48:35 +00:00
}
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
}
Nasal fixup
2020-09-15 17:22:35 +00:00
if (pts.Sim.Input.Selected.engine[1].getBoolValue() and pts.Controls.Engines.Engine.reverser[1].getValue() == 1) {
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
var pos = pts.Controls.Engines.Engine.throttleRev[1].getValue();
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
if (pos > 0.051) {
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
pts.Controls.Engines.Engine.throttleRev[1].setValue(pos - 0.15);
A320-family fork
2019-10-14 16:48:35 +00:00
} else {
Make reverse thrust also respect selected engines The simple toggle, bound to Del, engages reverse on the selected engine, but if it is engaged on either, disengages it on both, so you don't get stuck in reverse when selecting engine. I also removed the check of weight-on-wheels from the disengage case, so you don't get stuck if somehow the aircraft still becomes airborne after selecting reverse on the ground. The finer control, bound to F1 and F2, only controls the selected engines now. Previous version disengaged reverse for both engines when either reached zero throttle-rev, which does not seem to be founded in reality and does not make much sense. You can always use Del to disengage reverse on both engines.
2020-02-15 22:34:12 +00:00
interpolate("/engines/engine[1]/reverser-pos-norm", 0, 1.0);
Reverser control code to PTS
2020-09-15 17:17:06 +00:00
pts.Controls.Engines.Engine.throttleRev[1].setValue(0);
pts.Controls.Engines.Engine.reverser[1].setValue(0);
Correction
2020-09-15 17:18:34 +00:00
pts.Fdm.JSBsim.Propulsion.Engine.reverserAngle[1].setValue(0);
A320-family fork
2019-10-14 16:48:35 +00:00
}
}
}
Copy permalink