> I've been looking at the Bendix/King KT 70/71 (transponder) manual and > plan to start implimenting this instrument. Other than tuning in a > freq and having it report flight level is there anything else that I > need to think about? We don't have much in the way of ATC at the > moment so I'm guessing this instrument will be more cosmetic than > anything. But, if you are training with an instructor who is playing > the role of ATC, you can at least go through the motions ...
(a) Have the little light flicker every five or ten seconds if the simulator thinks it might be high enough, or near class B/C airspace, or near another aircraft with TCAS, or near a military airport/aircraft, or ... (etc). For example, in San Diego, it flickers several times a second. (b) Internally track how long the unit has been turned on (as opposed to whether it is in standby). If less than ten minutes, requests for Mode C are silently internally performed as Mode A. (c) Remember that it reports pressure altitude and not any other altitude. (d) Implement the lamp test function, since some people who don't start their flights near radar service will use it before going near a radar unit. (e) Unlike a certain proprietary simulator, don't put the digits 8 and 9 on. (f) Place the transponder data, if any and according to mode selected, on the property system and ideally expose it in the multiplayer stuff. That will subsequently make it easy to integrate a D-BRITE simulation. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
