------------------------------------------------------------------------
Subject: Re: [Flightgear-devel] Radio Ranges (A-N beams) From: James Turner <[EMAIL PROTECTED]> Date: Sun, 17 Aug 2008 19:11:51 +0100 To: FlightGear developers discussions <flightgear-devel@lists.sourceforge.net> Hi James No instruments (other than a radio panel) are required as this navigation is based upon just listening to the "A" or "N" code signals sent from the (low freq) transmitter. The biggest problem would likely be getting the data as to the locations, freqs, and beam orientations of the transmitter stations, and setting up the transmitters in the sim. Several good articles on this are avail if you do a google search for radio range stations. One such is: http://www.oldbeacon.com/beacon/radio_range_stations.htm jj http://kingmont.com <snip> - assemble the data in some format - get it into FG, alongside the existing navaids (there's also the potential to attach service dates to the existing navaids, so they could be disabled prior to a certain date) - write a new kind of instrument (probably copying or subclassing navradio.cxx or adf.cxx) which does the range / detection math, and drives the appropriate output props (needle deflections or audio generation or whatever) - write the GUI for such an instrument. Each of those is a pretty straightforward step, that I can see - not trivial, but fairly self-contained. James ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
