> As far as I can see, there is no generic implementation possible > for turbine startup and shutdown. Everything would have to be > done specifically for each engine type. Maybe the best thing to > do would be to expose some appropriate inputs to the engine > code (running or not, current RPM, station temperatures, etc...) > and implement the details per-engine in Nasal...
It doesn't have to be that complicated. In JSBSim we just spin the engine up to about 20% with a starter (starter type doesn't matter), then you open the fuel cutoff valve and the engine starts. That's close enough, ignition modeling could be added, but I'd consider that an optional detail. To shutdown you close the fuel cutoff valve. This is generic enough for all turbines. > FWIW: why do people care about this stuff so much? Engine > startup and shutdown is a boring, algorithmic, checklist task. > It's not exactly what I'd call fun, and it certainly won't ever > be implemented at a fidelity level useful for flight training. > What's the deal? :) I agree startup is boring, which means it should always be possible to begin with the engines running. I find the shutdown useful for practicing engine-out approaches, at least I did until I got tired of using the twist-grip rudder. Once it's shut down then an airstart is nice. Dave _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
