Vivian Meazza wrote:
> I do use the cruise value - based on the full throttle
> altitude. It's fine.  YASim provides a good solution. Very
> impressive.

Clearly I'm very confused then.  You were asking for the boost
control to work during solution earlier.  Is that not a
requirement?  The cutout lever will not be used during cruise, so
I can't see why that is an issue.

> > As I read it, though, your patch is currently a noop.  All it
> > does is add a new configuration option and adjust the
> > handling of the wastegate in a way that will never make a
> > difference in practice (skipping the wastegate handling for
> > superchargers is irrelevant -- supercharged engines already
> > have a very high wastegate setting that cannot be reached by
> > an engine, running or not).
>
> I'm afraid that you are quite, quite wrong here. Supercharged
> engines do not have a high wastegate setting, and it is readily
> reached by the running engine over much of its operating range.

Blargh.  I'm talking about *code* here, not aircraft.  A YASim
engine without a wastegate setting has a _maxMP value of 1.0e06.
I assure you this is correct.  I wrote it.  The point being that
your patch just implements current behavior in a different way.

> Actually it means that the magnetos are > O and engine rpm >
> 60, but of course you know that. But I'm going to revisit this.

And now, yet again, you're getting snippy.  Stop it.  That's the
*condition* for the _running boolean, not the effect.  Read the
code more carefully.

> a. ensures that the manifold pressure is ambient when the
> engine is not turning.

OK, that's an easy fix.

> b. allows a windmilling engine to develop supercharger/turbo
> pressure

But not in a realistic way.  Like I said earlier, I'm going to
skip this until we get a sane model worked out.

> c. skips the wastegate if the parameter 'supercharger' is true
> so that the Boost Control function which _you_ suggested be
> written (in Nasal), and which Melchior and I spent several days
> writing and tuning, can operate instead of the wastegate
> function.

And here is where you've gotten confused.  You shouldn't have a
wastegate=xxx setting on your engine any more.  If this is
missing, like it should be, then it is automatically set to
1.0e06 and your patch, like I said, is a noop.  You might like
this code, but it does not behave any differently from what is in
CVS.

> d. It allows accurate data to be used in the wastegate
> parameter. While the wastegate function is skipped, the
> wastegate parameter still has to be entered accurately to allow
> YASim to solve properly.

But you said earlier that you are using a *cruise* configuration
in the solver.  The cutout lever is not used during cruise.  So I
simply don't see how this is a problem.

We're about to go in circles again, and my blood pressure is
rising.  So try this: DON'T reply to my message paragraph by
paragraph.  Start from scratch, post a configuration file that
you want to use that does not work.  Explain why.  Use numbers.
Ask for suggestions.  Don't touch the C++ code until you have
convinced me of what you want to do.

Andy


_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to