Bugs: Difference between revisions

Jump to navigation Jump to search
1,165 bytes added ,  10 February 2007
ILS service volume issues
(fullscreen initialization)
(ILS service volume issues)
Line 434: Line 434:
priority.  This makes both the log and the console record hard  
priority.  This makes both the log and the console record hard  
to interpret.
to interpret.
==== Glideslope service volume. ====
The code in navradio.cxx appears to assume the glideslope
service volume is the same as the localizer service
volume.  This is quite unrealistic.
==== Extended service volume. ====
In some parts of the world, a goodly fraction of the
localizers have an expanded service volume (ESV),
often quite a bit larger than the standard service
volume you see in the AIM.  The code in navradio.cxx
was ignoring the service volume information in the
database and wrongly assuming the default values
applied everywhere.  Code to fix the range-related
part of the problem has been offered
but not yet incorporated.
==== Other service volume issues ====
The code  in navradio.cxx has no understanding of how
'''azimuth''' affects the
localizer.  There is more to the story than reception range.
It is perfectly possible to be outside the LOC service volume
for reasons having to do with azimuth, not range. 
Good ident will be heard, but false localizer courses will
cause serious trouble for the unwary pilot.
Similar remarks apply to false glide slopes.
The code would need to be significantly restructured to deal
with this.


== Missing Features and Traps for the Unwary ==
== Missing Features and Traps for the Unwary ==
70

edits

Navigation menu