Board index FlightGear Support Flying Autopilot

B777 ILS Autoland Problem

Using the autopilot is an important thing when flying airliners.

Re: B777 ILS Autoland Problem

Postby V12 » Wed Jan 08, 2020 3:47 pm

wkitty42 :
I obtained new awy.dat, nav.dat and fix.dat cycle 2001. Where should I copy that files, if I don't want overwrite default files ?
Fly high, fly fast - fly Concorde !
User avatar
V12
 
Posts: 1739
Joined: Thu Jan 12, 2017 4:27 pm
Location: LZIB
Callsign: BAWV12

Re: B777 ILS Autoland Problem

Postby wkitty42 » Wed Jan 08, 2020 4:43 pm

fredsie wrote in Wed Jan 08, 2020 11:10 am:That does sound like a better idea, but I don't think I have such a directory. Do I have to create it? If so, where?

yes, you have to create your custom scenery directory and then create the two directories i name in there... you can put it where ever you like as long as you point FG to it so it will use it... you do this in the launcher's scenery paths section...

fredsie wrote in Wed Jan 08, 2020 11:10 am:Also, when you say "copy the section for the airport in question", I didn't find a "section" for the airport in nav.dat. It was in alphabetic order and I searched for the specific ILS identifier and just deleted that row. I'm not sure how I would go about replicating the absence of that row in an override file.

i currently have one file for LIRN (LIRN.dat) and one for LTFM (LTFM.dat) that i created...
the file i have for LIRN has the required header and then one line for RWY 06 that adds the ILS-cat-I entry that is missing...
the file i have for LTFM adds all of the entries for LTFM but i do not recall what adjustments, additions, or removals i may have made for that airport... it has 16 entries plus the required header...

fredsie wrote in Wed Jan 08, 2020 11:10 am:Would the override file simply be the whole nav.dat as amended?

it could be but i find it better to use one file per airport and to use the ICAO code as the file name... the file contains only the required header and lines needed for that ICAO... the key is that the entries here will override those in the database that is built from the default nav.dat file...

i'm also making a huge eWAG that having the override file and leaving out a line will remove that line from the database but i've never tried to remove one to see...

here's an example of my NavData overrides...

example:
Code: Select all
/home/myuser/myflightgear/mySceneryOverrides/NavData/nav/LIRN.dat
/home/myuser/myflightgear/mySceneryOverrides/NavData/nav/LTFM.dat


i've only pointed FG to "/home/myuser/myflightgear/mySceneryOverrides/" and it picks up NavData and all scenery folders in there on its own... my scenery overrides directory contains these directories...
Code: Select all
/home/myuser/myflightgear/mySceneryOverrides/AI/
/home/myuser/myflightgear/mySceneryOverrides/Terrain/
/home/myuser/myflightgear/mySceneryOverrides/Objects/
/home/myuser/myflightgear/mySceneryOverrides/Airports/
/home/myuser/myflightgear/mySceneryOverrides/Models/
/home/myuser/myflightgear/mySceneryOverrides/NavData/
/home/myuser/myflightgear/mySceneryOverrides/Roads/
/home/myuser/myflightgear/mySceneryOverrides/Pylons/
/home/myuser/myflightgear/mySceneryOverrides/Buildings/


here's my override for LIRN's runway(s)...

LIRN.dat
Code: Select all

810 Version - data cycle 2013.10, build 20131334, metadata NavXP810.  Copyright (c) 2013, Robin A. Peel (robin@x-plane.com).   This data is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.  This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details.  You should have received a copy of the GNU General Public License along with this program ("AptNavGNULicence.txt"); if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.

4  40.88688900  014.28988900    294 11015  18      52.736 NPC  LIRN 06  ILS-cat-I



here's my override for LTFM's runway(s)...

LTFM.dat
Code: Select all

810 Version - data cycle 2013.10, build 20131334, metadata NavXP810.  Copyright © 2013, Robin A. Peel (robin@x-plane.com).   This data is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.  This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details.  You should have received a copy of the GNU General Public License along with this program ("AptNavGNULicence.txt"); if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.

3  41.31222222  028.70750000    325 11000 200        5.60 UHL   LTFM  VOR
3  41.30944400  028.72556000    325 10825 200        5.60 UHM   LTFM  VOR
4  41.29799701  028.70674572    262 11035  18     179.300 IUCB  LTFM  16R  ILS-cat-I
4  41.29815057  028.72710782    347 11195  18     179.300 IUCF  LTFM  17L  ILS-cat-I
4  41.26554110  028.70739027    358 10810  18     359.300 IUCA  LTFM  34L  ILS-cat-I
4  41.26274041  028.72779674    347 10955  18     359.300 IUCE  LTFM  35R  ILS-cat-I
6  41.29799701  028.70674572    303 11035  12  300179.300 IUCB  LTFM  16R  GS
6  41.29815057  028.72710782    277 11195  12  300179.300 IUCF  LTFM  17L  GS
6  41.26554110  028.70739027    402 10810  12  300359.300 IUCA  LTFM  34L  GS
6  41.26274041  028.72779674    392 10955  12  300359.300 IUCE  LTFM  35R  GS
12  41.31222222  028.70750000   325 11000 200       0.0   UHL   LTFM  VOR-DME
12  41.30944400  028.72556000   325 10825 200       0.0   UHM   LTFM  VOR-DME
12  41.29799701  028.70674572   262 11035  18       0.000 IUCB  LTFM  16R  DME-ILS
12  41.29815057  028.72710782   349 11195  18       0.000 IUCF  LTFM  17L  DME-ILS
12  41.26554110  028.70739027   358 10810  18       0.000 IUCA  LTFM  34L  DME-ILS
12  41.26274041  028.72779674   347 10955  18       0.000 IUCE  LTFM  35R  DME-ILS



that should give you a better idea of how this works and what you need to do to override your nav data for the airport in question... you do not need all of those override directories if you only need to override nav data... you only need the NavData directory and the nav directory inside it...

there may also be an apt directory inside NavData to override airport definitions from the default apt.dat file... that's a similar thing to do like this situation but it applies only to the airport layout...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 6135
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: B777 ILS Autoland Problem

Postby wkitty42 » Wed Jan 08, 2020 4:47 pm

V12 wrote in Wed Jan 08, 2020 3:47 pm:wkitty42 :
I obtained new awy.dat, nav.dat and fix.dat cycle 2001. Where should I copy that files, if I don't want overwrite default files ?

i have no idea about awy.dat and fix.dat but that nav.dat may possibly be placed into the NavData/nav directory as described... it should override identical entries in the default and add new ones... it may also remove no-longer-existing ones but that is a guess that i'm trying to assist the OP in figuring out and if this NavData/nav override method is how to do it...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 6135
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: B777 ILS Autoland Problem

Postby fredsie » Wed Jan 08, 2020 5:26 pm

Many thanks @wkitty42 for this comprehensive explanation. I can now make the limited changes I need without corrupting the main nav.dat.
fredsie
 
Posts: 43
Joined: Sun Apr 24, 2011 2:55 pm
Location: Liverpool, UK
OS: Linux o/Suse 15

Re: B777 ILS Autoland Problem

Postby V12 » Wed Jan 08, 2020 5:47 pm

Thank You. I will try it.
Fly high, fly fast - fly Concorde !
User avatar
V12
 
Posts: 1739
Joined: Thu Jan 12, 2017 4:27 pm
Location: LZIB
Callsign: BAWV12

Previous

Return to Autopilot

Who is online

Users browsing this forum: No registered users and 1 guest