- Messages
- 63
- Country
Hey everyone,
When I though I had a reasonable understanding of how the engines are being modeled, I find myself bumping against a wall once and again. As has been discussed in several posts, the engines.cfg file now includes the 150x tables from legacy .air files, some variables from the legacy aircraft.cfg file and some other new variables/ parameters.
Having those tables, I though made it possible for us to use the theory and techniques we've all being working with for the past few years. But I was wrong. Not only the models do not behave at all with respect to those tables; if you delete all of them, the model behaves the same as if you have them (with whatever values). It also seems that the new curves are being characterized from the new low-high parameters within engines.cfg (i.e. low_idle_n1. high_n1, idle_FF, etc.).
All in all, I have been testing the A320Neo model at ISA conditions and a Sea Level airport.
Thanks!
When I though I had a reasonable understanding of how the engines are being modeled, I find myself bumping against a wall once and again. As has been discussed in several posts, the engines.cfg file now includes the 150x tables from legacy .air files, some variables from the legacy aircraft.cfg file and some other new variables/ parameters.
Having those tables, I though made it possible for us to use the theory and techniques we've all being working with for the past few years. But I was wrong. Not only the models do not behave at all with respect to those tables; if you delete all of them, the model behaves the same as if you have them (with whatever values). It also seems that the new curves are being characterized from the new low-high parameters within engines.cfg (i.e. low_idle_n1. high_n1, idle_FF, etc.).
All in all, I have been testing the A320Neo model at ISA conditions and a Sea Level airport.
- Idle and Max TO (TOGA) values for N1, N2 and FF are taken from the new low-high variables within engines.cfg, not the table related variables.
- One thing I tried was to tweak the tables to have idle and maximum n1, n2 and FF values just like the variables in engines.cfg. No joy. At different throttle levels the different parameters do not follow the tables.
- Taking out ALL table related variables, but maintaining low-high variables, gives exactly the same output as with the Tables. Exception: Thrust is always 0. If we maintain ONLY the table that relates CN1 to Thrust, then we get thrust values back again (although the values do not follow the table).
- Maintaining Tables, but deleting ALL low-high variables (N1, N2 and FF), actually messes up everything and engine parameters do not follow Tables:
- N1 idles at 50%
- N2 idles at 50%
- FF idles at 16 Kg/h
- Tables do not seem to be needed for engine modeling
- Low-high variables seem to be the ones being used to characterize engine behavior
- This would mean engine characterization is hardcoded and we are only allowed to give minimum and maximum values for them
Thanks!