March 27, 20215 yr Does this one work?https://www.magentacloud.de/lnk/rllxUKeb#file Alex Alex' Projects: Little Navmap
March 27, 20215 yr Author Thanks for the file although it didn't work. FMS says "Load Error" and nothing loads. No departure, destination, cruise level, legs etc.
March 28, 20215 yr Thanks for testing. I adapted the export to the changed keywords (why?) between CRJ and Airbus. I wish there would be better error messages than "Load Error" or maybe even a log file.😒 One might even load the plan partially if the procedures do not match.🙄 I'm sure this needs more work and will contact you guys for testing. For now I'd like to get the update out to fix the wind download issue. Alex Alex' Projects: Little Navmap
May 10, 20215 yr On 3/18/2021 at 8:00 PM, Steve4256 said: Airway1=T202 Airway for first leg Airway1From=GOLAT First waypoint on the airway Airway1To=ALOSO Last waypoint on the airway Below example If first leg waypoint is after SID Direct from SID GISD1W to RANAX waypoint. airway1=DIRECT airway1from=GISDI // last SID waypoint airway1to=RANAX //Direct to RANAX from GISDY waypoint. @albar965 Export options AIRAC 2104 // MSFS + LNM 2.6.11 + CRJ Route: EDLP RWY24 GISD1W GISDI DCT RANAX Z85 ANANO UL126 DINKU M867 WLD T104 ROKIL ROKI1A EDDM RWY8R Below flighplan exported via LNM .lnmpln file format EDLP Paderborn Lippstadt.lnmpln Below flighplan exported via LNM MSFS CRJ .flp file format EDLPEDDM.flp And smth went wrong after load into FMS There is only EDLP RWY/STAR ---discontinuity--- SID/RWY EDDM There is no direct to RANAX from SID thats why smth went wrong Below flightplan generated via CRJ FMS and no problems with direct, airways, waypoints. TESTFMS1.flp @albar965 If you want more info feel free to DM me anytime. Edited May 10, 20215 yr by TENPATROL
May 12, 20215 yr @TENPATROLThank you very much for the files! This aircraft is more and more a riddle to me.😞 Never seen this before: Quote airway1=DIRECT Give me some time. I already changed a lot for the CRJ export based on all the examples and can send you some files for testing. Alex Alex' Projects: Little Navmap
May 30, 20215 yr Author I just came back to the CRJ to do another flight (patch update 2 just released), and the new LNM multi-export function for the MFS CRJ exported a flight plan that imported correctly into the aircraft MCDU in terms of departure, destination, legs and cruise level. Those are the main flight plan details that I'm after, so that is great. Thanks! FYI - I did notice that the flight plan file had transition altitude & level of 18000 when the flight was in Australia which has transition alt 10000 and transition level FL110. And then after import the aircraft transition altitude (climb) in the MCDU was 0 and the transition level (descent) was FL110. Don't know whether the MCDU is supposed to import the flight plan transition alt/lvl or not.
May 30, 20215 yr 10 hours ago, Steve4256 said: I just came back to the CRJ to do another flight (patch update 2 just released), and the new LNM multi-export function for the MFS CRJ exported a flight plan that imported correctly into the aircraft MCDU in terms of departure, destination, legs and cruise level. Those are the main flight plan details that I'm after, so that is great. Thanks! Good to hear. I get reports of all kind of issues when exporting for the MSFS CRJ. Maybe it imported without issues because you did not export procedures? I tried several improvements for the CRJ export which can be tested with the next release. 10 hours ago, Steve4256 said: FYI - I did notice that the flight plan file had transition altitude & level of 18000 when the flight was in Australia which has transition alt 10000 and transition level FL110. And then after import the aircraft transition altitude (climb) in the MCDU was 0 and the transition level (descent) was FL110. Don't know whether the MCDU is supposed to import the flight plan transition alt/lvl or not. LNM simply exports a default value for the transition altitude. You have to set it manually in the aircraft. Same applies to aircraft weights and other features LNM is not aware of. Alex Alex' Projects: Little Navmap
May 30, 20215 yr Author Quote 8 hours ago, albar965 said: Maybe it imported without issues because you did not export procedures? Yeah I didn't export any procedures. I believe those are meant to be entered manually in the aircraft. Quote 8 hours ago, albar965 said: LNM simply exports a default value for the transition altitude No worries
June 5, 20215 yr Here is a beta with a attempt to fix the CRJ issues: https://www.magentacloud.de/lnk/8ALAgaXn If all is going well I'll convert this right to a release without announcing and publishing the beta. Let me know how its going. Alex Alex' Projects: Little Navmap
June 5, 20215 yr Author Thanks for the beta version. Tried a few flight plans and they imported correctly in terms of dept, arrival and cruise level but some plans imported leg waypoints correctly and some didn't. Also tested with the current LNM released version and was the same. Seemed to be that some intersection waypoints didn't import. But others in the same flight plan did. Only a guess, but might be something to do with airways. For example, the below flight plan correctly imported the OKW, NENRE and GCV waypoints but didn't import WEONE and JAMMR FltNo= Airway1=J239 Airway1FROM=WEONE Airway1TO=JAMMR DctWpt2=OKW DctWpt2Coordinates=33.237885,-87.249870 DctWpt3=NENRE DctWpt3Coordinates=31.670856,-87.760864 DctWpt4=GCV DctWpt4Coordinates=31.097961,-88.486130 Can anyone else give any further feedback?
June 5, 20215 yr Author I tried the Simbrief export with the same flight plan and it worked and looks like it's due to it not using airways and just using the waypoints. Even though the airway was in the flight plan description. FltNo= DctWpt1=WEONE DctWpt1Coordinates=33.525689,-85.122247 DctWpt2=JAMMR DctWpt2Coordinates=33.232136,-86.942319 DctWpt3=OKW DctWpt3Coordinates=33.237886,-87.249867 DctWpt4=NENRE DctWpt4Coordinates=31.670856,-87.760867 DctWpt5=GCV DctWpt5Coordinates=31.097961,-88.486128
June 5, 20215 yr Author And now just manually entered the flight plan in the CRJ FMC and saved it. And it saved the legs as follows fltno= dctwpt1=WEONE dctwpt1coordinates=33.525690,-85.122250 airway2=J239 airway2from=WEONE airway2to=JAMMR dctwpt3=OKW dctwpt3coordinates=33.237860,-87.249870 dctwpt4=NENRE dctwpt4coordinates=31.670860,-87.760870 dctwpt5=GCV dctwpt5coordinates=31.097960,-88.486130
June 7, 20215 yr Hi Steve, thank you very much for all your help! I 'm afraid I have to remove the airways like SimBrief does since the aircraft does not seem to be able to consistently load complex plans. No idea what's going on there. I'd like to keep at least the procedures. Can you load the plan below? Edit: The forum messes up the formatting: Here is the file as is: https://www.magentacloud.de/lnk/porAA0ny#file Quote [CoRte] ArptDep=EDDF RwyDep=EDDF07R ArptArr=LIRF RwyArr= ArptAltn= SID=ANEK2D SIDEnrTrans= STAR=RITE2K EnrSTARTrans= STARApprTrans= Appr_Trans= RwyArrFinal= CoRoute= FltNo= DctWpt1=ANEKI DctWpt1Coordinates=49.317272,8.480428 DctWpt2=NEKLO DctWpt2Coordinates=49.286110,8.476389 DctWpt3=BADLI DctWpt3Coordinates=49.063610,8.447500 DctWpt4=PABLA DctWpt4Coordinates=48.788586,8.351970 DctWpt5=HERBI DctWpt5Coordinates=48.490833,8.243611 DctWpt6=NATOR DctWpt6Coordinates=48.169998,8.321261 DctWpt7=TITIX DctWpt7Coordinates=47.858334,8.396667 DctWpt8=TRA DctWpt8Coordinates=47.689499,8.436973 DctWpt9=ARGAX DctWpt9Coordinates=47.049999,9.298056 DctWpt10=RESIA DctWpt10Coordinates=46.478333,10.043333 DctWpt11=IDREK DctWpt11Coordinates=45.646111,10.819445 DctWpt12=BAGNO DctWpt12Coordinates=43.890556,11.802222 DctWpt13=GAVRA DctWpt13Coordinates=43.776112,11.824722 [PerfData] CrzAlt=25000 CrzAltAltn=-1 PaxCnt=-1 PaxWeight=-1 CargoWeight=-1 FuelWeight=-1 WindDirClb=0 WindSpdClb=0 WindDirCrz=0 WindSpdCrz=0 WindDirDes=0 WindSpdDes=0 ISADev=-1 ResFuel=-1 TaxiFuel=-1 [VNAVData] TransAlt=18000 TransLvl=18000 Edited June 7, 20215 yr by albar965 Alex' Projects: Little Navmap
June 7, 20215 yr This might fix some of the issues: https://www.magentacloud.de/lnk/KPrAAeng Note that the version number is the same. You can distinguish the builds by the revision in about LNM. Alex Alex' Projects: Little Navmap
Archived
This topic is now archived and is closed to further replies.