On Mon, 2006-04-03 at 19:18 +0100, Vivian Meazza wrote: > Curtis L. Olson > > > Ron Jensen wrote: > > > > >At the risk of repeating myself, TACAN is broken for everything but the > > >carriers. Replacing the two files below makes it work perfectly. > > > > > >Can someone submit them to CVS before the 0.9.10 release _please!_ > > > > > >Last month I suggested a change[1] to TACAN_freq.dat and carrier_nav.dat > > >to enable TACAN to work on the proper channels. > > > > > >I'd like to see this go in so the F4E I'm working on can use the TACAN. > > > > > >Since it seems the sourceforge list stripped the attachments they are on > > >my webserver: http://www.jentronics.com/fgfs/TACAN_freq.dat.gz and > > >http://www.jentronics.com/fgfs/carrier_nav.dat.gz > > > > > > > > >[1] > > >http://sourceforge.net/mailarchive/forum.php?thread_id=9643858&forum_id=1 > > 919 > > > > > > > > I don't know anything about the TACAN's, hopefully someone who does know > > something about these can take a look today. > > > > TACAN is not actually broken. Due to the way the nav.dat file is > constructed, if you want to use TACAN in conjunction with Atlas, then the > existing TACAN data works. If you want to use TACAN with real maps, then you > need the data provided by Ron. Since most people do not have access to real > maps, but do have access to Atlas, then I propose we leave it the way it is, > but make Ron's data available for those that want it. > > > Regards, > > Vivian
Hi Vivian, Atlas works with TACAN? How? A "grep -R -i TACAN *" in my Atlas source tree yields no hits. Is there a patch somewhere to add it in? I don't have any physical 'real' maps, just the data I get from the Internet at places like http://www.airnav.com/ or http://www.myafd.com . Here's how it works, go to our main airport KSFO http://www.airnav.com/airport/KSFO Look down to "Nearby radio navigation aids," Oakland VORTAC is only 9.6 miles away, click its link: http://www.airnav.com/cgi-bin/navaid-info?id=OAK&type=VORTAC&name=OAKLAND Look at the Operational Characteristics: Frequency: 116.80 TACAN channel: 115X The way the current TACAN_freq.dat is built Oakland VORTAC works on FGFS 'TACAN' channel 081X. The same exercise can be ran on any of the VORTACs around KSFO http://www.airnav.com/cgi-bin/navaid-info?id=OSI&type=VORTAC&name=WOODSIDE WOODSIDE VORTAC Operational Characteristics Frequency: 113.90 TACAN channel: 086X *FGFS* 'TACAN' channel: 052Y And with different web services: http://www.myafd.com/NavAid/SAU_VORTAC_SAUSALITO NavAid Facility ID: SAU Type: VORTAC Name: SAUSALITO Freqency: 116.20 TACAN Channel: 109X *FGFS* 'TACAN' channel: 075X Are you really suggesting we ignore the real-world, freely available navigation aid data in favor of incorrect data out of Atlas? Thanks, Ron ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
