There is a great mod for Garmin GNS530 for MFS2020:

https://github.com/pimarc/pms50-gns530

https://forums.flightsimulator.com/t/gns530-mod/296598

However I'm unable to import to the modded GNS530, the FPL exported from P2ATC in the MSFS202 - .pln format, with SID/STAR/APPR. I have the "Export SID/STAR/Approach checked in P2ATC export dialog. The GNS530 is not able to interpret the SIDs/STARs properly. I have the same Navigraph DB (AIRAC 2104) installed in P2ATC and the sim.

Any hints?

 

I suspect the GNS530 does not load .pln format plans.  It has its own formats.

Check the GNS documentation for what it can load.

Dave

The documentation says:
If the PLN file comes from MSFS2020 (save option in world map) the MOD will recognize SID, STARS and APPR. If your PLN file comes from another software, the result may differ from the original flight plan because the producer software may not use the same database so SID, STAR or APPROACH may be not recognized.

I compared the .pln files generated by P2ATC and MFS2020 and discovered some differences:

MFS2020 export (much more detail, e.g. runway specifed, different fields naming):

<?xml version="1.0" encoding="UTF-8"?>
<DepartureFP>XIDN1B</DepartureFP>
<RunwayNumberFP>28</RunwayNumberFP>
<ArrivalFP>XIDN1U</ArrivalFP>
<RunwayNumberFP>29</RunwayNumberFP>
<ApproachTypeFP>RNAV</ApproachTypeFP>
<RunwayNumberFP>29</RunwayNumberFP>

 

P2ATC export:

<?xml version="1.0" encoding="ISO-8859-1"?>
<ATCAirway>XIDN1B</ATCAirway>
<ATCAirway>XIDN1U</ATCAirway>
no approach information, just the waypoints

Edited August 10, 20214 yr by Steku

For .pln plans, you need to check the option "Export SID/STAR/Appr Waypoints" on the FltPln tab of config to get the procedures to export.  

If you email me the saved .vbf file from P2A and the .pln of the same plan from MSFS, I will see if I can tweak the program to output a plan more like MSFS.

Regards,

Dave

I verified various settings for exporting in P2ATC:

Config -> Flt Pln -> Import-Export SID/STAR/APPR Waypts

Config -> Flt Pln -> Use XPlane 11 format

No matter how these options are set, the MSFS 2020 - .pln  export (I mean the export generated in P2ATC) is always the same (I used Notepad++ to compare the files). The rar file with the P2ATC files and MFS2020 .pln file was e-mailed to you (mail subject the same as the title of this thread).

Also the file generated by P2ATC in the export window is the same no matter if I export:

P3D (All Versions) - .pln

MSFS 2020 - . pln

FSX - .pln

Could it be a bug invoking wrong .pln export routine, no matter what the settings are? Or choosing different sim utilizing .pln format impacts only the destination folder, not the file format itself?

The export of the same route from MFS2020 itself is different, much more detailed, with different field naming for departure, arrival, approach.

 

 

Edited August 11, 20214 yr by Steku

I have not received the email with the plans.  Please try resending them to [email protected]   

There's a possibility they are too large for email, in which case you could upload them to dropbox or other cloud storage and send me a link.

Thanks,

Dave

The file is 6 KB rar. Here you are: https://www.dropbox.com/sh/uv1r94ml7d3endv/AADzgaO38vtr20sbB2PvaMkHa?dl=0

The file exported from MFS2020 is definitely different (much more detail, individual field names for DepartureFP, ArrivalFP,  ApproachTypeFP) than the files exported from P2ATC.

 ________________________________________________________________________________

 File exported from MFS2020 (just parts of it to show the main differences):

 EPPO EPWR MFS2020.pln

 <?xml version="1.0" encoding="UTF-8"?>

 <ATCWaypoint id="PO801">

            <ATCWaypointType>Intersection</ATCWaypointType>

            <WorldPosition>N52° 29' 5.00",E16° 29' 38.70",+002850.00</WorldPosition>

            <Alt1FP>5400</Alt1FP>

            <AltDescFP>AT_OR_ABOVE</AltDescFP>

            <SpeedMaxFP>240</SpeedMaxFP>

            <DepartureFP>XIDN1B</DepartureFP>

            <RunwayNumberFP>28</RunwayNumberFP>

         <ATCWaypoint id="WR707">

            <ATCWaypointType>Intersection</ATCWaypointType>

            <WorldPosition>N51° 25' 21.30",E17° 9' 41.50",+009850.00</WorldPosition>

            <Alt1FP>12000</Alt1FP>

            <AltDescFP>AT_OR_BELOW</AltDescFP>

            <SpeedMaxFP>-1</SpeedMaxFP>

            <ArrivalFP>XIDN1U</ArrivalFP>

            <RunwayNumberFP>29</RunwayNumberFP>

            <ICAO>

                <ICAORegion>EP</ICAORegion>

                <ICAOIdent>WR707</ICAOIdent>

                <ICAOAirport>EPWR</ICAOAirport>

 <ATCWaypoint id="EPWR">

            <ATCWaypointType>Airport</ATCWaypointType>

            <WorldPosition>N51° 6' 10.00",E16° 53' 9.00",+000400.00</WorldPosition>

            <SpeedMaxFP>-1</SpeedMaxFP>

            <ApproachTypeFP>RNAV</ApproachTypeFP>

            <RunwayNumberFP>29</RunwayNumberFP>

            <ICAO>

                <ICAOIdent>EPWR</ICAOIdent>

            </ICAO>

        </ATCWaypoint>

 ________________________________________________________________________________

File exported from P2ATC (just parts of it to show the main differences):

 EPPO-EPWR.pln

 <?xml version="1.0" encoding="ISO-8859-1"?>

 <ATCWaypoint id="PO801">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N52° 29' 5",E16° 29' 38.7",+000000.00</WorldPosition>

<ATCAirway>XIDN1B</ATCAirway>

<ICAO>

<ICAOIdent>PO801</ICAOIdent>

</ICAO>

</ATCWaypoint>

 <ATCWaypoint id="XIDNA">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N51° 42' 0",E16° 59' 51",+000000.00</WorldPosition>

<ATCAirway>XIDN1U</ATCAirway>

 

Edited August 12, 20214 yr by Steku

If you could please email  the entire file that you saved/exported from MSFS, I can work on getting an exported file to look like it.

Thanks,

Dave

Edit:  Just received the files.  Thanks!

Edited August 12, 20214 yr by Dave-Pilot2ATC