mnieuwhof 2 Posted April 20, 2014 Share Posted April 20, 2014 When I export a route with PFPX 1.14 for the Airbus X (donwloaded yesterday, 19-04-2014) I get a BAD FORMAT error when I want to activate it in the MCDU via co-route. What is, or what am I doing wrong here? Thank you, Marc Nieuwhof Link to comment Share on other sites More sharing options...
Deputy Sheriffs mopperle 4162 Posted April 20, 2014 Deputy Sheriffs Share Posted April 20, 2014 How did you export the route in PFPX? What Navdata (provider and cycle) are you using in the Airbus X and in PFPX? Link to comment Share on other sites More sharing options...
mnieuwhof 2 Posted April 21, 2014 Author Share Posted April 21, 2014 How did you export the route in PFPX? What Navdata (provider and cycle) are you using in the Airbus X and in PFPX? I use cycle 1404 from Navigraph for the Airbus and PFPX. I have chosen this provider too in the Airbus configuration tool. I checked in PFPX that I want to export for the Airbus too. Below is the exported flightplan: [CoRte] ArptDep=EHAM ArptArr=LPPT RwyDep=EHAM09 RwyArr=LPPT35 Airway1=UN872 Airway1FROM=LEKKO Airway1TO=PON Airway2=UT300 Airway2FROM=PON Airway2TO=EVX Airway3=UT176 Airway3FROM=EVX Airway3TO=TERPO Airway4=UN872 Airway4FROM=TERPO Airway4TO=ERIGA Airway5=UT460 Airway5FROM=ERIGA Airway5TO=NOVAN Airway6=UN741 Airway6FROM=NOVAN Airway6TO=STG Airway7=UN726 Airway7FROM=STG Airway7TO=NARBO Airway8=R72 Airway8FROM=NARBO Airway8TO=VIS Airway9=G41 Airway9FROM=VIS Airway9TO=FTM Link to comment Share on other sites More sharing options...
Deputy Sheriffs mopperle 4162 Posted April 21, 2014 Deputy Sheriffs Share Posted April 21, 2014 The problem could be the plan from Airway8 onmwords, as R72 is a low level route (FL105 to 195). If your cruiselevel doesn't match it might cause a problem. When I use PFPX (with NavdataPro) it gives me a different route: [CoRte] ArptDep=EHAM ArptArr=LPPT RwyDep=EHAM09 RwyArr=LPPT35 Airway1=UN872 Airway1FROM=LEKKO Airway1TO=PON Airway2=UT300 Airway2FROM=PON Airway2TO=EVX Airway3=UT176 Airway3FROM=EVX Airway3TO=TERPO Airway4=UN872 Airway4FROM=TERPO Airway4TO=ERIGA Airway5=UZ218 Airway5FROM=ERIGA Airway5TO=BABEX Airway6=UN976 Airway6FROM=BABEX Airway6TO=VIS Airway7=UN872 Airway7FROM=VIS Airway7TO=FTM Link to comment Share on other sites More sharing options...
mnieuwhof 2 Posted April 21, 2014 Author Share Posted April 21, 2014 The problem could be the plan from Airway8 onmwords, as R72 is a low level route (FL105 to 195). If your cruiselevel doesn't match it might cause a problem. When I use PFPX (with NavdataPro) it gives me a different route: [CoRte] ArptDep=EHAM ArptArr=LPPT RwyDep=EHAM09 RwyArr=LPPT35 Airway1=UN872 Airway1FROM=LEKKO Airway1TO=PON Airway2=UT300 Airway2FROM=PON Airway2TO=EVX Airway3=UT176 Airway3FROM=EVX Airway3TO=TERPO Airway4=UN872 Airway4FROM=TERPO Airway4TO=ERIGA Airway5=UZ218 Airway5FROM=ERIGA Airway5TO=BABEX Airway6=UN976 Airway6FROM=BABEX Airway6TO=VIS Airway7=UN872 Airway7FROM=VIS Airway7TO=FTM Thanx, I have the same flightplan now but I still get a BAD FORMAT [CoRte] ArptDep=EHAM ArptArr=LPPT RwyDep=EHAM09 RwyArr=LPPT35 Airway1=UN872 Airway1FROM=LEKKO Airway1TO=PON Airway2=UT300 Airway2FROM=PON Airway2TO=EVX Airway3=UT176 Airway3FROM=EVX Airway3TO=TERPO Airway4=UN872 Airway4FROM=TERPO Airway4TO=ERIGA Airway5=UZ218 Airway5FROM=ERIGA Airway5TO=BABEX Airway6=UN976 Airway6FROM=BABEX Airway6TO=VIS Airway7=UN872 Airway7FROM=VIS Airway7TO=FTM In PFPX I let PFPX auto build a route, but I guess it took my first one from it's database. After that I did Find->Upper Airspace and the it came with your FP. But it did not help solve my problem Thanx, Marc Link to comment Share on other sites More sharing options...
mnieuwhof 2 Posted April 21, 2014 Author Share Posted April 21, 2014 It's getting stranger... When I enter EHAM/LPPT on the INIT page then the MCDU goes to the available flightplans menu. When I click on the EHAMLPPT.fl name I get a NOT IN DATABASE error... Hmmm... Link to comment Share on other sites More sharing options...
Deputy Sheriffs mopperle 4162 Posted April 21, 2014 Deputy Sheriffs Share Posted April 21, 2014 OK, just checked it and I can load the flightplan without any problems. Could it be that you are using the wrong navdatabase from Navigraph. There are two versions: one for AXE ver. 1.15 and older and one for ver. 1.15 and later? Link to comment Share on other sites More sharing options...
mnieuwhof 2 Posted April 22, 2014 Author Share Posted April 22, 2014 I checked and double checked but all are in the correct format.... but.... When I export a flightplan as EHAMLSZH01.FL (as PFPX suggests) then the MCDU accepts it. When I change the name in PFPX in EHAMLSZH (thus exporting a EHAMLSZH.FL) then the MCDU gives an error! (either BAD FORMAT or NOT IN DATABASE). Marc Link to comment Share on other sites More sharing options...
Deputy Sheriffs mopperle 4162 Posted April 22, 2014 Deputy Sheriffs Share Posted April 22, 2014 OK, that's the problem. The filename of the saved plan must have the format xxxxyyyy##: xxxx = departure, yyyy arrival, ## 2 digit number, so EHAMLSZH01 is correct, where EHAMLSZH is wrong. That's why PFPX is suggesting the correct format. Link to comment Share on other sites More sharing options...
mnieuwhof 2 Posted April 22, 2014 Author Share Posted April 22, 2014 OK, that's the problem. The filename of the saved plan must have the format xxxxyyyy##: xxxx = departure, yyyy arrival, ## 2 digit number, so EHAMLSZH01 is correct, where EHAMLSZH is wrong. That's why PFPX is suggesting the correct format. All my other addons accept this change in PFPX but the AXE not... but I don't mind, I know now what the problem is and the AXE lists the flightplans in a nice manner so consider this issue as solved! Thank you for your patience and helpfull replies @mopperle Marc Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.