Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FDM issues #7

Open
jan-hudec opened this issue Sep 1, 2015 · 4 comments
Open

FDM issues #7

jan-hudec opened this issue Sep 1, 2015 · 4 comments

Comments

@jan-hudec
Copy link

The FDM is really not very good.

The most obvious problem is that the engines generate way too much thrust at speed, because they use the default thrust function which is valid for turbojets with supersonic intake and not high-bypass turbofans. But that is also the easiest problem to fix; I already asked what the table should look like and can create one that will still be a guess, but at least a sensible one.

However there are other problems. The second obvious issue is that the aircraft tends to cruise with nose about 2° below horizon while in reality it should be about 2° above horizon, indicating that the lift table needs some tweaking. The lift function is not the hard part either.

The hard bits are not immediately obvious when testing the model out, only by either reading the model or disabling the FBW and taking the aircraft out of the flight envelope:

  • The moment of inertia tensor is diagonal and I don't really know how good the numbers are (calculating moments of inertia is hard).
  • The lift table does not include values for negative angle of attack nor for deep stall.
  • While A320 does tend to stall straight (which I suppose is due to the good yaw damper) there should be some wing drop tendency and it should be possible to get the aircraft in a spin, especially when yaw damper is disabled, but AFAICT the model is not capable of simulating either.
  • Aileron reversal in stall and stall of horizontal stabilizer with loss of elevator efficiency don't seem to be simulated either.
  • There is no simulation of critical Mach number.

Now these problems should be actually fixable, but a really big amount of work.

On the other hand I already tried (for the old A320family) replacing the FDM with a Yasim one. This has the advantage that it calculates the inertia tensor, uses saneish lift and drag for all attitudes and angles of attack and simulates asymmetric stall.

But I was never really satisfied with that, because some of the deficiencies apply to Yasim and they are not easily fixable there. Yasim also does not provide many properties JSBSim exports that are useful for the FBW though I didn't look at the current implementation how much it actually needs them.

So I am not sure how to best improve the situation. I am opening this as tracking issue and to collect ideas.

@xcvb85
Copy link

xcvb85 commented Sep 2, 2015

Calculating moments of inertia is not that hard (depending on the accuracy) but the question is how to get detailed data of the mass distribution. If you already have a Yasim FDM and if you are happy with the results you could use its inertia tensor for the JSBSim FDM as well. If the mixed terms such as Ixy are zero it means that your axis are principal axis.

@jan-hudec
Copy link
Author

@xcvb85, indeed, it should be possible to copy the values calculated by Yasim except one would have to be careful about the different axis definitions. I'll probably do that. Or I'll copy the calculations from Yasim to a separate tool; there are many JSBSim models for FlightGear that could use this kind of updates.

Regarding principal axis, well, the thing is that no aircraft has the normal longitudinal axis as principal axis of its moment of inertia at least because the vertical stabilizer only extends up.

jan-hudec added a commit that referenced this issue Oct 13, 2015
Ok, so I created first version of tool for calculating bits of FDM and
generated the engines with it. And hit two problems:

 - The engines now generate not much more than the expected ~5000 lbf
   at 35000 ft and M0.78, so the climb rate is no longer insane, but
   the plane still only needs ~2×3200 lbf at that altitude and speed
   (weight was ~130,000 lb), so the operating ceiling is still too high.
 - http://www.jet-engine.net/civtfspec.html has TSFC at take-off and at
   cruise and they are _significantly_ different, but I can only give
   one value to JSBSim. So I used a value that “should” give correct
   value at cruise (but without correct drag the resulting fuel burn is
   not right anyway), but gives too high value at take-off. I suspect
   the TSFC increases with speed, but I don't even have that confirmed
   yet.

Concerns #7.
@jan-hudec
Copy link
Author

Ok, so I've started a tool for generating model bits, https://github.com/jan-hudec/yaamatic, and generated new engine configurations with it.

The climb rate is no longer so absurdly huge, but the drag at altitude seems to me to be a little bit on the low side and correspondingly the operating ceiling a bit high. A320s usually cruise relatively low (say, FL320 rather than, say, FL380) and while neo has slightly more powerful engines in the base configuration, I believe it is because with higher bypass ratio the thrust declines faster with speed, so at cruise they probably don't have higher thrust any more (unfortunately http://www.cfmaeroengines.com/ only gives approximate cruise thrust for CFM56s, but not CFM Leaps).

The other thing is that JSBSim (nor YASim for that matter) does not simulate the increase of TSFC at cruise, which I suspect, but don't have confirmed, is with speed and which is rather huge. http://www.jet-engine.net/civtfspec.html gives 0.330 lb/lbf/h at SLS and 0.596 lb/lbf/h at cruise for CFM56-5A1 (used on A320-211; no data for Leap yet, so I just deduce 15% from those numbers). I am contemplating whether to adjust the fuel amounts when moving it to the feed tanks, create my own model or contribute change to JSBSim that would allow full <function>s in the engine parameters. It is probably the least pressing problem of the FDM right now though.

@legoboyvdlp
Copy link
Member

By the way, if you need manuals or anything, they are available on Google. Like, charts for MAX alt.

jan-hudec referenced this issue in FGMEMBERS/A320-family Jul 4, 2016
Changes to the AP, now it's more stable.
tyresmoke.nas file added.
Pilot view position updated.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants