... the user friendly GPS tool


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
fpl files not routing
#1
I recently produced a few fpl files in the same manner that I always have but they did not work properly in the aircraft Garmin G1000.  My usual workflow is to open my route gpx files and then save as fpl.  I then name each user waypoint and typically a nice fpl file is produced which imports seamlessly into the Garmin G1000.  For the latest batch - when importing into the aircraft Garmin it says that the user waypoints were imported but they were not added to a flight plan.  My best guess is that there is a problem with the routing file so that it doesn't know how to connect all the user waypoints into a route the way it normally does?  That is just an amateur guess though.

If someone could help, I can attach an older file that works and a recent one that doesn't to see if we can find the problem.  I attempted to attach but received an error that the type of file is not allowed.

Thanks
Reply
#2
*.zip is one of the allowed file formats for attachments.
--
Matthias
Reply
#3
I have attached a folder with 4 fpl files.  2 pairs of routes with the older files that still load just fine and newly produced files that do not load properly in the aircraft Garmin G1000.

It would be very much appreciated if anyone can find the source of the problem with the new files.

Thanks


Attached Files
.zip   FileQuestion.zip (Size: 2.99 KB / Downloads: 54)
Reply
#4
Code:
       <waypoint>
            <identifier>CO0710</identifier>
            <type>USER WAYPOINT</type>
            <country-code></country-code>
            <lat>38.351849</lat>
            <lon>-106.173459</lon>
            <comment>CO0710</comment>
            <elevation>0.0</elevation>
        </waypoint>
In the o (I suppose the older or origin) an additional element country-code is present which is missing in the newer file version. In this example in the comment the code is CO0710 (CO + 4 digits) thereas in the new one the leading zero is ommited (CO710)

route-point element in old one has a element waypoint-contry-code and the waypoint-identifier is also CO + 4 digits compared to the new version without leading zero CO + 3digits code (CO710)

HTH

Grüße,
Ilmari
Reply
#5
(20.07.2020, 22:39)Sitka21 Wrote: It would be very much appreciated if anyone can find the source of the problem with the new files.

I've had lots of interactions with a user that uses .fpl files and tried to improve them. The changes between your files are small:
The identifier is different and the country-code isn't written anymore. See the attached screenshots.
   
   

Please try the attached file c07now.fpl. Does it work for you?

.zip   CO07now.fpl.zip (Size: 814 bytes / Downloads: 45)
--
Christian
Reply
#6
(08.08.2020, 10:25)routeconverter Wrote:
(20.07.2020, 22:39)Sitka21 Wrote: It would be very much appreciated if anyone can find the source of the problem with the new files.

I've had lots of interactions with a user that uses .fpl files and tried to improve them. The changes between your files are small:
The identifier is different and the country-code isn't written anymore. See the attached screenshots.



Please try the attached file c07now.fpl. Does it work for you?

I believe this should work. I had to manually edit an .FPL today with the following to match what skyvector created and the only difference is the following in an empty value:

<country-code></country-code> vs. <country-code />

and

<waypoint-country-code></waypoint-country-code> vs. <waypoint-country-code />
Reply
#7
(08.08.2020, 10:25)routeconverter Wrote:
(20.07.2020, 22:39)Sitka21 Wrote: It would be very much appreciated if anyone can find the source of the problem with the new files.

I've had lots of interactions with a user that uses .fpl files and tried to improve them. The changes between your files are small:
The identifier is different and the country-code isn't written anymore. See the attached screenshots.

Please try the attached file c07now.fpl. Does it work for you?

I just had a pilot load this for me and it works. Can you push the change to production?

Thank you!
Reply
#8
(17.09.2020, 15:15)pilotnoel Wrote: I just had a pilot load this for me and it works. Can you push the change to production?

I don't know, what this would mean. The current prerelease writes country codes even if they're empty since the 9th of August.

Do you need more changes?
--
Christian
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)