#473 Localizer deviation signal is not correct.

[Anonymous]

Originally created by: h... (code.google.com)@hyde-tech.com

*What steps will reproduce the problem?*
1.Approach localizer from just outside of length of marker in the map.
2.
3.

*What is the expected output? What do you see instead?*
Fly continue until localizer capture.

*Any output in the console (black window)?*
Ship capture before reach the localizer.

*What FlightGear version are you using (when using GIT version, please
mention date)?*
GIT 20111024.

*What operating system and graphics card?*
Fedora14, 6500GT

*Please provide any additional information below or as attachment
Line#566 of flightgear/src/Instrumentation/navradio.cxx
_cdiDeflection *= signal_quality_norm;
should be deleted or commented out.
Signal weakness is already judged by inrange variable. We don't need this calculation. This causes localizer capture when signal is weak.

[Anonymous]

Originally posted by: bre... (code.google.com)@gmail.com

The localizer capture itself could also be fixed by adding a check for signal strength, i.e. don't capture unless signal-quality-norm is >= 0.95 (to make that work reliably, another fix was necessary though - otherwise reported signal strength could be even 1.0 though no station was in range: https://www.gitorious.org/fg/flightgear/commit/6fbb5aaf99636ea9918a863581ee6f25747bdae4).

The remaining question is whether it is realistic that the deflection fades with the distance - and especially whether it should fade to 0 (no deflection) or converge against some maximum (full deflection etc). I'll leave that to you, cumulunimbustorstusmaximus :).

Labels: Instrumentation Nav
Cc: cumuluni...@gmail.com

[Anonymous]

Originally posted by: cumuluni... (code.google.com)@gmail.com

There will be another (better?) implementation for the next release, so I set this to WontFix

Status: WontFix