Re: [Flightgear-devel] TACANs (was DAFIFT progress)
James Turner writes: > That said, the UPP TACAN is not listed in NAV.TXT, if you know of any > others, please let me know and I'll check. (Or did you mean UUP, > 'Uplands'?) That's it -- I was giving the ident from memory. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] TACANs (was DAFIFT progress)
On Monday, February 3, 2003, at 07:40 pm, David Megginson wrote: It's more complicated than that. DME receivers (which are UHF) can use TACANs to get distance information -- usually, you do that by tuning in a fake paired VOR frequency. For example, if I tune my DME to 108.8, or slave it to a NAV radio tuned to 108.8, I get distance readings from the UPP TACAN at CYOW, even though there's no VOR. Can the paired frequency be deduced from the channel? Right now, I think the answer is no. I was hoping that such TACANs simply listed the fake frequency in their FREQ column, but I've got checks for that in place and I'm not hitting them (just got that code working). That said, the UPP TACAN is not listed in NAV.TXT, if you know of any others, please let me know and I'll check. (Or did you mean UUP, 'Uplands'?) H&H James -- Whenever a friend succeeds, a little something in me dies. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] TACANs (was DAFIFT progress)
On Mon, 3 Feb 2003, David Megginson wrote: > It's more complicated than that. DME receivers (which are UHF) can > use TACANs to get distance information -- usually, you do that by > tuning in a fake paired VOR frequency. For example, if I tune my DME > to 108.8, or slave it to a NAV radio tuned to 108.8, I get distance > readings from the UPP TACAN at CYOW, even though there's no VOR. Can > the paired frequency be deduced from the channel? ISTR there being a lookup table for this in the back of the british isles/north atlantic en route supplement - I'll have a look when I get home. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] TACANs (was DAFIFT progress)
James Turner writes: > So, armed with the knowledge that TACANs are UHF, not VHF, and that > they use military channel codes, I went and looked at the DAFIF fields > again ... and guess what the field two after FREQ is? Yeah, it's the > channel. Boy do I feel silly. It's more complicated than that. DME receivers (which are UHF) can use TACANs to get distance information -- usually, you do that by tuning in a fake paired VOR frequency. For example, if I tune my DME to 108.8, or slave it to a NAV radio tuned to 108.8, I get distance readings from the UPP TACAN at CYOW, even though there's no VOR. Can the paired frequency be deduced from the channel? All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] TACANs (was DAFIFT progress)
On Monday, February 3, 2003, at 05:30 pm, Mally wrote: The UK ones appear to be TACANs at Odiham and St Athan: http://www.nightstop.freeola.com/beacon%20decodes/beacon%20decodes.htm Thanks for this, I've now done a bit more background reading on TACANs.. In the netherlands: TWN SSB At least the UK ones all have the 'TAC' prefix on my SimCharts. So ... You are right, its TACAN. They will be replaced by ILS this year. So, armed with the knowledge that TACANs are UHF, not VHF, and that they use military channel codes, I went and looked at the DAFIF fields again ... and guess what the field two after FREQ is? Yeah, it's the channel. Boy do I feel silly. Of course, this leaves one problem / task (especially for the A4 and harrier pilots): does anyone fancy adding a TACAN receiver to the radio-stack? I'll add in another field on the FGNav class, and do the right thing for VORTACs, now that the light-bulbs have switched on in my addled head. Actually, it'll be two fields: an unsigned int channel ID and a flag for X / Y band, whatever they are. Oh, and these things can be mobile, for example on a carrier. If anyone fancies doing that, FGNav list is going to need some work, it's not quite set up for navids that don't stay put. H&H James -- The lack of planning on your part does not constitute to an emergency on mine ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
