JonathanRichardson
12-19-2008, 12:43 PM
Hi
I thought this might be a useful general post re ILS as I bumped into this problem...
We have a function in the CDU for Autotune of the NAV radios (added for 747 originally) but as I have found out it needs to be used with consideration in FS and with the new navdata updates. The ILS signal itself is sent from FS, but the new navdata may have updated frequencies, as such it is possible for the CDU to set a ILS frequency that does not exist in FS automatically.
I have recently been flying (for the first time) into Dublin for various tests runway 28. And here there is one such miss-match. The problem is, you can override the correct (real world frequency) to the FS old frequency, and thus perfrom an approach with this old FS signal/frequency *but* the CDU will eventually look at the real world data again (its primary source) and re auto tune, overiding what it thinks is an error on the manual selection by the pilot to the correct real world frequency in knows from the navcycle update, so when this happens in CATIII at 500ft you suddenly find yourself with no ILS.
My suggestion is unless you are 100% sure frequencies match, switch off autotune navs. That is unless you change the FS sceneries themselves to match the real world ones. This might be a rare thing to happen - but it obviously can....
I think this might explain some peoples loss of autoland in the past. Also, make sure you set the runway heading always in the MCP heading window.
Regards
Jonathan Richardson
Project Magenta
I thought this might be a useful general post re ILS as I bumped into this problem...
We have a function in the CDU for Autotune of the NAV radios (added for 747 originally) but as I have found out it needs to be used with consideration in FS and with the new navdata updates. The ILS signal itself is sent from FS, but the new navdata may have updated frequencies, as such it is possible for the CDU to set a ILS frequency that does not exist in FS automatically.
I have recently been flying (for the first time) into Dublin for various tests runway 28. And here there is one such miss-match. The problem is, you can override the correct (real world frequency) to the FS old frequency, and thus perfrom an approach with this old FS signal/frequency *but* the CDU will eventually look at the real world data again (its primary source) and re auto tune, overiding what it thinks is an error on the manual selection by the pilot to the correct real world frequency in knows from the navcycle update, so when this happens in CATIII at 500ft you suddenly find yourself with no ILS.
My suggestion is unless you are 100% sure frequencies match, switch off autotune navs. That is unless you change the FS sceneries themselves to match the real world ones. This might be a rare thing to happen - but it obviously can....
I think this might explain some peoples loss of autoland in the past. Also, make sure you set the runway heading always in the MCP heading window.
Regards
Jonathan Richardson
Project Magenta