> I've been thinking that we should start a whole new source tree, > src/Instrumentation/, to include the current steam and radio modules > together with GPS modules, weather radar, and anything else we happen > to come up with. Perhaps even autopilot could fit in here. The > environment module provides some data that the steam module can take > advantage of now, such as temperature and air pressure.
Yeah. It also has an advantage that we can 'wire' the properties together. Most of the danger due to a failure is as a result of interactions and dependency-based secondary errors and additional failures. If we can say that "altimeter[0]" and "airspeed[0]" take data from "static[0]" then when the instructor sets "static[0]/blocked" the correct side effects will occur. As another example, running the engine at idle RPM (with the instructor having specified an old but functional vacuum pump) can cause the electrical autopilot to put the aircraft into a spiral dive or a spin without warning. That follows because "vacuumpump[0]" uses "engine[0]/rpm" to decide how effective it is and (after instructor's derating) "vacuum[0]" will drop below 3 inches. The artificial horizon gyro will spin down, tilt slightly and give a continuous climb-and-turn indication to the autopilot. Since the autopilot is electrical, it is running normally and reacts. So, I think this is a good idea ... _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
