While 1501 is obselte, setting it sets the [TurbineEngineData] in the A/C config. It seems you can take your pick as to which to set. I set it only on the .air file and then I guess FS automatically updated my .cfg file.
I haven't gotten around to testing all the wonderful advice you guys have given me. But I have been able to get my changes into the air file as I wanted. However they - as usually happens on a first attempt - did not do what I wanted.
My problem is that the engine seems to be starting at the wrong N2. Also N1 is not responding correctly. I want it to respond more like a
real jet engine startup.
What table sets the actual ignition of the engine (i.e. what N2 equals ignition)? Also how do I determine what the engine does right after ignition? From my understanding table 1505 takes affect right after ignition. Now I assume if I can set the proper N2 = ignition value and N1 respective of N2 value then I can get something more realistic here.
I am far more versed in coding gauges and panels than air files. I know that I can control these things through the use of gauge logic and stuff but why can't I just have a corrected air file that makes the engines work as they are supposed to?
The FS jet light-off RPM is above 17%CN2 and limited to starter max RPM of 25% CN2 (ISA MSL).
To model a realistic start up process you will need:
1) gauge code to control ignition scenarios
2) table 1505 set to a good start
3) adjust %CN to match your startup RPM range
1) gauge code to control ignition scenarios
If you are trying to get into the complexities of hotstarts, hungstarts, and deadstarts, you will need to code the conditions for each and manipulate fuel and ignition accordingly.
Those scenarios aside, you need a start button and ignition button that inputs the user's intention, and a line of code to trigger the FS starter on each gauge cycle until the start is successful or the start button is released manually (or automatically for FADEC protected systems); and set the FS master ignition as outlined below.
The starters should remain triggered until idle, and master ignition off until RPM reaches the optimal light-off RPM. If the user opens the fuel too early, you will have to code the temperature buildup and fuel burn into the display while keeping the ignition locked out until the appropriate RPM. The starter should continue to fire every cycle throughout.
If you want the start to hang you must toggle the fuel cutoff every cycle, while the starter is still firing after ignition was already achieved. Again TGT changes will need to be encoded. The fuel toggle would normally occur at some higher RPM than light-off.
For normal starts the ignition should be coded to energize at the optimal light-off RPM, even while user has selected 'ignition on' mode.
2) table 1505 set to a good start
The zero value of table 1505 should be set to the optimal light-off RPM. The slope and additional settings are addressed here:
http://fsdeveloper.com/forum/showthread.php?t=389153
From that discussion it is important to emphasis "The distance between each line is the time the engine will take to reach the next CN2. Perfectly horizontal lines will never reach the next line, while vertical lines will reach the next CN2 instantly. To slow the spool rate down, simply add more time (x value) between two lines."
If your engines surge, the angle of the line to the left of idle CN2 is too steep. (as displayed in AirEd)
3) adjust %CN to match your startup RPM range
If your engine has a wider or narrower start range than a typical commercial jet, you may need to mathematically adjust your CN2 & CN1 to fit that range, then re-calibrate the displays to show the correct value. For example, if you have a ultralight jet which has a light-off RPM of 15%CN2, you could scale down your displayed RPM by 40%, and realign your tables accordingly. This would move the starter range to within a useable range for your engine.