> > Message: 2 > > I just tried to practice the ILS RWY 30 approach into KLBF (Lee Bird > Field at North Platte, Nebraska) since I plan to be there this week. > When I tune nav1 to 111.5, no response. So I gunzip nav.dat.gz, and > search on ILBF and sure enough the LLZ record is there with the right > frequency and runway, etc. Here is the record. > > > 4 41.134508 -100.694367 2775 11150 305.990 ILBF KLBF 30 LLZ > > Here is the glideslope record. > > > 6 41.121867 -100.668792 2768 11150 300305.235 --- KLBF 30 GS > > So why is FG not finding this ILS? > > I did note that there are other locations with ILBF as the code for > their localisers. Is the search algorithm getting confused? I am > running yesterday's CVS.
I have no specific knowledge of your problem however I have been battling with the ILS code this last week and have found and fixed a problem. Also in your case the ILS only operate on RWY 30 there is no record for RWY 12 so you won't have this problem. The problem I was having was that on an approach bearing 092 to EGLC (London City Airport) using the ILS on 111.15 there are two localisers one at each end of the runway. The code in navlist.cxx (findByFreq) is picking up the nearest transmitter which is not facing the approach. (It's direction held in ...->multiuse() is 180 wrong). There are two consequences of this 1) CDI instrumentation is reversed. 2) because of the above an autopilot approach will turn the aircraft around and flay away from the airport. I'm not sure of the protocol in this matter is it good etiquette to post code fragments here? If it is I'll post a modified version which gets (appears to get) it right. We select the ILS/LOC transmitter that is nearest to the aircraft and if the plane is also within the +/- 30 degs of the required approach radial. -- Ed Sirett <[EMAIL PROTECTED]> _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
