Josh Babcock

 
> > As it turns out, the B-29's turboregulator control was a little bit
> > different from what I described.  The "Volume Control"  governed off
> > total system MAP.  If you set the potentiometer to , say, '*8", it
> > maintained the overall MAP until the turbo reached its limits.  So,
> > for example, you set the engines to Max Continuous, you wouldn't need
> > to twiddle the turbos as you climbed from Sea Level to 25,000'+.
> > Sorry if I cased some confusion, there.
> >
> > "Zeno's Warbirds" has, IIRC, a Realplayer movie on flying the B-29.
> > That's a pretty good resource.
> 
> True, though for some reason I have not checked it out. I do have the
> .ram file that points to the stream though. Also, note that to go past 8
> on the turbo dial required opening a safety latch and per the pilot's
> handbook was not to be done for more than 2 min. which I think is the
> equivalent of the RAF WEP. I'm not sure what bearing this has on the
> engine modeling but at some point I should put in a nasal script to blow
> up the turbos after some extended period at settings above 8. I'll have
> to figure out what conditions would actually cause a failure though.
> 

Thanks to Peter's input, I think that:

a. I now understand the operation of the turbo regulator

b. Have the numbers to proceed. 

If we assume the critical altitude to be 25,000 ft with the boost at 0.8 (#8
on the dial), everything should fall into place. WEP (or combat power)
should fall naturally out of this calculation.

Failure - don't worry about the conditions :-). After about 5 mins or so,
according to OAT, the rear row of the cylinders would overheat, leading to
an engine fire which burnt through the firewall, causing catastrophic
failure of the wing main spar. Should be easy enough to model! Apparently,
this was not really cured until the up-engined version which was the B50.

V.





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

Reply via email to