Ron

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:flightgear-
> [EMAIL PROTECTED] On Behalf Of Jensen
> Sent: 03 February 2006 02:55
> To: [email protected]
> Subject: RE: [Flightgear-users] TACAN in FG 0.9.9
> 
> On Thu, 2006-02-02 at 14:52 +0000, Vivian Meazza wrote:
> > Ron Jensen
> >
> > > I noticed when I upgraded to fgfs 0.9.9 there seems to be support for
> > > TACAN now, but I can't figure out how to get it to function.  Does it
> > > work?
> > >
> > > FlightGear/Navaids$ zgrep HIF nav.dat.gz
> > > 12  41.120503 -111.963681   4806 11120   0.000 HIF  Hill TACAN
> > > 4   41.104047 -111.959581   4775 10990     152.980 IHIF KHIF 14 LLZ
> > > 6   41.137167 -111.980497   4780 10990  280151.963 ---  KHIF 14 GS
> > > 8   41.149389 -111.990497   4560     0     151.963 ---  KHIF 14 MM
> > >
> > > If I set the DME freq to 111.20 I can read the HIF TACAN DME.  Looking
> > > up that freq in TACAN_freq.dat yields channel 025Y:
> > >
> > > FlightGear/Navaids$ zgrep 11120 TACAN_freq.dat.gz
> > > 025Y    11120
> > >
> > > If I set the TACAN to 025Y near HIF /instrumentation/tacan/in-range
> > > remains "false"
> > >
> > > Web sources suggest the TACAN at HIF is channel 49.
> > >
> > > If I set the TACAN to 049(X/Y) near HIF /instrumentation/tacan/in-
> range
> > > remains "false"
> > >
> > > Found these pages:
> > > http://microvoltradio.com/tacan.htm
> > > http://www.angelfire.com/mb/amandx/vuhffreq.html
> > >
> > > I guess the numbers in TACAN_freq.dat are in 100s of KHz instead of
> 10s
> > > of KHz like in nav.dat.gz.  So channel 49X is 1,010.0 MHz not 101.00
> MHz
> > > like I was reading it at first.  It seems the 111.20 MHz DME in
> > > nav.dat.gz is correctly assosciated with TACAN channel 49X, and
> > > FlightGear treats it like any other DME, which I guess it is.
> > >
> > > Is there a way in FlightGear to pull the DME freq from a TACAN
> channel?
> > >
> > > Is there a way to get data into /instrumentation/tacan/ ?
> > >
> >
> > You have to be using an ac with TACAN fitted - Hunter or Seahawk to get
> it
> > to work, and select the TACAN channel through the pull-down menu -
> equipment
> > - radio settings. If you still aren't getting any read-outs, let me know
> and
> > I'll look into it further.
> >
> > Vivian
> 
> 
> First, sorry for the double send...  Evolution picked the wrong e-mail
> address for the first one, and I expected it to be rejected because that
> e-mail isn't subscribed to this list...
> 
> I fired up the Seahawk at KNID (China Lake) and it worked more or less
> as expected.  The TACAN channels aren't right, though.
> 
> I took the Seahawk back to KHIF (Hill TACAN) and found its TACAN worked
> on channel 25Y.  It's _supposed_ to be on channel 49X...

Are you saying that the frequency associated with 25Y is wrong or that the
database has the wrong frequency? I can fix the former, but not the latter.

> Do you have any idea what magic incantations are required to equip an
> aircraft with TACAN?  It shouldn't be too hard to equip my (OK, mostly
> David Culp's) OV-10 with a TACAN receiver once I figure out how...

Well, I ought to ... I wrote the code :-) Look in the seahawk directory.
Look in systems/ . You need to add a similar file to
seahawk-instrumentation. This provides a non-default set of instruments, and
includes the tacan. You then need to amend the -set.xml file to include
this. Finally you have to ensure that there is electrical power to the
instrument. TACAN is a normal instrument, and this procedure is the same for
any such instrument.

HTH, get back to me if you have any problems.

Vivian



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Flightgear-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-users

Reply via email to