41 minutes ago, Carmelo Hernandez said:

So now it recognizes the flight plan in the folder, but it fails to import on the GNS 530.

Can you please explain in more details?

It recognizes: does it mean you can see the list of flight plans in the device?

It fails: does it mean when you import you get an error message on the device?

Is so, what is the message, and what flight plan file did you put in the folder?

Yes, I can see the list of flight plans on the device, and I get an error message that says “failed to import” or “flight plan failed to import” something to the nature of that.
 

Also in addition to the sample flight plan, I downloaded this one from Simbrief. EDFHEDDS.FPL

Ok we're making progress! so far:

- you've managed to create the FPL folder in the correct location

- you've added flight plan files into

- the device is properly listing all the flight plan files you've added

- however it fails trying to load any of them

 

Is this happening actually with any of the flight plans you've put in the folder or only some?

Do you have any other file which are not flight plans in the folder (like icons, shortcuts, text files and notices etc...)?

If you only put the sample LFATLFRG.fpl file in your FPL folder, is this one loading correctly at least?

 

 

 

So it only works with LFATLFRG.fpl but why?  The others have the same file extension, only in caps .FPL and downloaded via Simbrief.

1 hour ago, Carmelo Hernandez said:

So it only works with LFATLFRG.fpl but why?  The others have the same file extension, only in caps .FPL and downloaded via Simbrief.

Using the "spoiler" (the eye icon) feature of this forum's posting capabilities, please in a plain text editor such as Notepad open a couple of the unsuccessful .flp files and paste in the contents so I can look at them.  Flight plan imports are screened very closely by the rules built into the trainers by Garmin. The trainer import process will reject any flight plans that contain elements the trainer cannot process. I do not know if this is the issue you are facing, but I have experience with these issues and have previously documented and written about 

Sometimes it is a nav fix whose name is duplicated somewhere else in the world in the database and Garmin's import logic will not choose among them for you.  In other cases if your flight plan includes procedures such as a departure, an arrival, or an approach, the names of those procedures may have changed.  Arrival CHICKN2 eventually becomes arrival CHICKN3.  If your flight plan calls for CHICKN3 but the trainer database still contains it as CHICKN2, then there is a mismatch during the import and Garmin rejects the file from importing.  Pretty certain Garmin has filtered it this way to protect itself from liability.

The most successful method for externally creating a flight and then importing into the Garmin Trainers it is to keep it really simple, and then add enhancements in the RXP gauge after the import.

Spoiler

KLDJ DCT CAT DCT BIGGY V3 MAZIE DCT KPHL

EDFH SID GEBDA M150 KRH STAR EDDS

 

fppilot, I have copied and pasted the flight plans into the "spoiler" section above. Thanks!

@Carmelo Hernandez

Have you actually opened the sample LFATLFRG.fpl file in a notepad to see what it looks like?

In case you didn't here is:

Spoiler

<?xml version="1.0" encoding="utf-8"?>
<flight-plan xmlns="http://www8.garmin.com/xmlschemas/FlightPlan/v1">
  <created>2017-01-15T15:20:54Z</created>
  <waypoint-table>
    <waypoint>
      <identifier>LFAT</identifier>
      <type>AIRPORT</type>
      <country-code>LF</country-code>
      <lat>50.514722</lat>
      <lon>1.627500</lon>
      <comment />
    </waypoint>
    <waypoint>
      <identifier>ABB</identifier>
      <type>VOR</type>
      <country-code>LF</country-code>
      <lat>50.135139</lat>
      <lon>1.854694</lon>
      <comment />
    </waypoint>
    <waypoint>
      <identifier>DPE</identifier>
      <type>VOR</type>
      <country-code>LF</country-code>
      <lat>49.925389</lat>
      <lon>1.170639</lon>
      <comment />
    </waypoint>
    <waypoint>
      <identifier>LFOH</identifier>
      <type>AIRPORT</type>
      <country-code>LF</country-code>
      <lat>49.533889</lat>
      <lon>0.088056</lon>
      <comment />
    </waypoint>
    <waypoint>
      <identifier>LFRG</identifier>
      <type>AIRPORT</type>
      <country-code>LF</country-code>
      <lat>49.363333</lat>
      <lon>0.160000</lon>
      <comment />
    </waypoint>
  </waypoint-table>
  <route>
    <route-name>LFAT / LFRG</route-name>
    <flight-plan-index>1</flight-plan-index>
    <route-point>
      <waypoint-identifier>LFAT</waypoint-identifier>
      <waypoint-type>AIRPORT</waypoint-type>
      <waypoint-country-code>LF</waypoint-country-code>
    </route-point>
    <route-point>
      <waypoint-identifier>ABB</waypoint-identifier>
      <waypoint-type>VOR</waypoint-type>
      <waypoint-country-code>LF</waypoint-country-code>
    </route-point>
    <route-point>
      <waypoint-identifier>DPE</waypoint-identifier>
      <waypoint-type>VOR</waypoint-type>
      <waypoint-country-code>LF</waypoint-country-code>
    </route-point>
    <route-point>
      <waypoint-identifier>LFOH</waypoint-identifier>
      <waypoint-type>AIRPORT</waypoint-type>
      <waypoint-country-code>LF</waypoint-country-code>
    </route-point>
    <route-point>
      <waypoint-identifier>LFRG</waypoint-identifier>
      <waypoint-type>AIRPORT</waypoint-type>
      <waypoint-country-code>LF</waypoint-country-code>
    </route-point>
  </route>
</flight-plan>

As long as you're using a flight planning tool which is capable of exporting a GNS formatted flight plan file, it should work.

Spoiler

<?xml version="1.0" encoding="utf-8"?>
<flight-plan xmlns="http://www8.garmin.com/xmlschemas/FlightPlan/v1">
  <created>2021-09-11T15:37:46Z</created>
  <waypoint-table>
    <waypoint>
      <identifier>N12</identifier>
      <type>AIRPORT</type>
      <country-code>K6</country-code>
      <lat>40.066889</lat>
      <lon>-74.177556</lon>
      <comment />
    </waypoint>
    <waypoint>
      <identifier>WHITE</identifier>
      <type>INT</type>
      <country-code>K6</country-code>
      <lat>40.006756</lat>
      <lon>-74.251281</lon>
      <comment />
    </waypoint>
    <waypoint>
      <identifier>CYN</identifier>
      <type>VOR</type>
      <country-code>K6</country-code>
      <lat>39.817339</lat>
      <lon>-74.431625</lon>
      <comment />
    </waypoint>
    <waypoint>
      <identifier>CRESI</identifier>
      <type>INT</type>
      <country-code>K6</country-code>
      <lat>39.610922</lat>
      <lon>-74.626294</lon>
      <comment />
    </waypoint>
    <waypoint>
      <identifier>HOWIE</identifier>
      <type>INT</type>
      <country-code>K6</country-code>
      <lat>39.582728</lat>
      <lon>-74.652769</lon>
      <comment />
    </waypoint>
    <waypoint>
      <identifier>ANABL</identifier>
      <type>INT</type>
      <country-code>K6</country-code>
      <lat>39.504439</lat>
      <lon>-74.726144</lon>
      <comment />
    </waypoint>
    <waypoint>
      <identifier>LEEAH</identifier>
      <type>INT</type>
      <country-code>K6</country-code>
      <lat>39.260908</lat>
      <lon>-74.953058</lon>
      <comment />
    </waypoint>
    <waypoint>
      <identifier>KWWD</identifier>
      <type>AIRPORT</type>
      <country-code>K6</country-code>
      <lat>39.008369</lat>
      <lon>-74.908511</lon>
      <comment />
    </waypoint>
  </waypoint-table>
  <route>
    <route-name>N12 KWWD</route-name>
    <flight-plan-index>1</flight-plan-index>
    <route-point>
      <waypoint-identifier>N12</waypoint-identifier>
      <waypoint-type>AIRPORT</waypoint-type>
      <waypoint-country-code>K6</waypoint-country-code>
    </route-point>
    <route-point>
      <waypoint-identifier>WHITE</waypoint-identifier>
      <waypoint-type>INT</waypoint-type>
      <waypoint-country-code>K6</waypoint-country-code>
    </route-point>
    <route-point>
      <waypoint-identifier>CYN</waypoint-identifier>
      <waypoint-type>VOR</waypoint-type>
      <waypoint-country-code>K6</waypoint-country-code>
    </route-point>
    <route-point>
      <waypoint-identifier>CRESI</waypoint-identifier>
      <waypoint-type>INT</waypoint-type>
      <waypoint-country-code>K6</waypoint-country-code>
    </route-point>
    <route-point>
      <waypoint-identifier>HOWIE</waypoint-identifier>
      <waypoint-type>INT</waypoint-type>
      <waypoint-country-code>K6</waypoint-country-code>
    </route-point>
    <route-point>
      <waypoint-identifier>ANABL</waypoint-identifier>
      <waypoint-type>INT</waypoint-type>
      <waypoint-country-code>K6</waypoint-country-code>
    </route-point>
    <route-point>
      <waypoint-identifier>LEEAH</waypoint-identifier>
      <waypoint-type>INT</waypoint-type>
      <waypoint-country-code>K6</waypoint-country-code>
    </route-point>
    <route-point>
      <waypoint-identifier>KWWD</waypoint-identifier>
      <waypoint-type>AIRPORT</waypoint-type>
      <waypoint-country-code>K6</waypoint-country-code>
    </route-point>
  </route>
</flight-plan>
 

This is one, but others display in the way I initially sent in the spoiler. I'm just wondering why some do and some don't and it's quite frustrating.

48 minutes ago, Carmelo Hernandez said:

This is one, but others display in the way I initially sent in the spoiler. I'm just wondering why some do and some don't and it's quite frustrating.

Where are you creating your flight plan files?