AV80R GPS Flight plan import format
Thread Starter
Join Date: Nov 2008
Location: Cambridge, UK
Posts: 56
Likes: 0
Received 0 Likes
on
0 Posts
AV80R GPS Flight plan import format
I have a Bendix King AV80R, and I usually use the excellent SkyDemon to plan flights, but have yet to work out the format of the flight plan import for the AV80R.
The only info I can glean is the location and name of the import file, and that it accepts files from Jeppesen FliteStar.
Has anybody managed this, or any suggestions as to the Jeppesen FliteStar Export as Text file format - I probably have enough programming skills to reformat the SkyDemon output
TIA
The only info I can glean is the location and name of the import file, and that it accepts files from Jeppesen FliteStar.
Has anybody managed this, or any suggestions as to the Jeppesen FliteStar Export as Text file format - I probably have enough programming skills to reformat the SkyDemon output
TIA
Join Date: Mar 2008
Location: Bingley
Age: 71
Posts: 5
Likes: 0
Received 0 Likes
on
0 Posts
I have done it.
I will need to remember the details of what I did. Skydemon does not support the file format. I did agree to document it for them but havn't had the time yet. Flitestar will produce files that nearly work but lack some of the detail.
I will check what I did a let you know.
I will need to remember the details of what I did. Skydemon does not support the file format. I did agree to document it for them but havn't had the time yet. Flitestar will produce files that nearly work but lack some of the detail.
I will check what I did a let you know.
Thread Starter
Join Date: Nov 2008
Location: Cambridge, UK
Posts: 56
Likes: 0
Received 0 Likes
on
0 Posts
Any further comment?
If anybody has Flitestar, I would be happy to receive an example or two - I might be able to suss it out from there
PM for my e-mail
If anybody has Flitestar, I would be happy to receive an example or two - I might be able to suss it out from there
PM for my e-mail
Join Date: Mar 2008
Location: Bingley
Age: 71
Posts: 5
Likes: 0
Received 0 Likes
on
0 Posts
This is a very quick explanation which should enable you to load a simple plan.
The process is very simple. Create a file called route.txt and copy it to the \GoFly\Data\User directory on the AV80R as documented in the user manual. What the manual does not give you is the format of this file.
This example data was created by FliteStar as a simple flight from Sherburn to Fenlands, however Fenlands is represented as a user waypoint. It was saved as a generic text file called route.txt and copied to the unit.
After copying the file onto the unit restart the GoFly program. The flight plan will then appear in the list as either EGCJ-WP1 or SHERBURN-IN-ELMENT-WP1 depending on the settings in the AV80R. You should also be aware that the user waypoint WP1 and the flight plan in this example will be copied into the AV80R database and will remain there even if route.txt is deleted.
# FliteStar/FliteMap generated flight plan.
WPT S WP1 N 52 45.09 W 0 02.80
FPL 00
FWP P A EGCJ N 53 47.05 W 1 13.07 3500
FWP P V GAM N 53 16.88 W 0 56.83 3500
FWP U S WP1 N 52 45.09 W 0 02.80 20
To use with SkyDemon at this stage you will have to hand enter the data.
The file format used internally is a modified version of the data created by Flitestar. There are extra fields used to store information. On the AV80R this data becomes:-
WPT S WP1 N 52 45.09 W 000 02.80
# WP1 [Waypoint]
# User flight plan
# ----------------
FPL 00
# FPL NAME "EGCJ-WP1"
FWP P A EGCJ N 53 47.05 W 001 13.07
FWP P V GAM N 53 16.88 W 000 56.83
FWP U S WP1
An extra line has been added with the name of the plan. The FPL number will change and depends on the number of plans already loaded. The last field generated by FliteStar is height information which is not required by the AV80R. On the FWP lines column five indicates ‘P’ for a name already in the database or ‘U’ for a user waypoint and column seven indicates the type of waypoint – ‘A’ for airfield, ‘V’ for VOR, S for user site.
If you are hand coding a flight plan use the format used by the unit. I would also add any waypoints required directly into the unit.
Hope this helps
The process is very simple. Create a file called route.txt and copy it to the \GoFly\Data\User directory on the AV80R as documented in the user manual. What the manual does not give you is the format of this file.
This example data was created by FliteStar as a simple flight from Sherburn to Fenlands, however Fenlands is represented as a user waypoint. It was saved as a generic text file called route.txt and copied to the unit.
After copying the file onto the unit restart the GoFly program. The flight plan will then appear in the list as either EGCJ-WP1 or SHERBURN-IN-ELMENT-WP1 depending on the settings in the AV80R. You should also be aware that the user waypoint WP1 and the flight plan in this example will be copied into the AV80R database and will remain there even if route.txt is deleted.
# FliteStar/FliteMap generated flight plan.
WPT S WP1 N 52 45.09 W 0 02.80
FPL 00
FWP P A EGCJ N 53 47.05 W 1 13.07 3500
FWP P V GAM N 53 16.88 W 0 56.83 3500
FWP U S WP1 N 52 45.09 W 0 02.80 20
To use with SkyDemon at this stage you will have to hand enter the data.
The file format used internally is a modified version of the data created by Flitestar. There are extra fields used to store information. On the AV80R this data becomes:-
WPT S WP1 N 52 45.09 W 000 02.80
# WP1 [Waypoint]
# User flight plan
# ----------------
FPL 00
# FPL NAME "EGCJ-WP1"
FWP P A EGCJ N 53 47.05 W 001 13.07
FWP P V GAM N 53 16.88 W 000 56.83
FWP U S WP1
An extra line has been added with the name of the plan. The FPL number will change and depends on the number of plans already loaded. The last field generated by FliteStar is height information which is not required by the AV80R. On the FWP lines column five indicates ‘P’ for a name already in the database or ‘U’ for a user waypoint and column seven indicates the type of waypoint – ‘A’ for airfield, ‘V’ for VOR, S for user site.
If you are hand coding a flight plan use the format used by the unit. I would also add any waypoints required directly into the unit.
Hope this helps
Thread Starter
Join Date: Nov 2008
Location: Cambridge, UK
Posts: 56
Likes: 0
Received 0 Likes
on
0 Posts
Thanks for that - gives me a good starting point, your example load up fine.
One quick question - in the user directory, there are two files (currently identical, with the same time stamp) FPDATA.BK and fplan.bk (and also a FPDATA.OLD)
Any idea which I should add to?
Many thanks
One quick question - in the user directory, there are two files (currently identical, with the same time stamp) FPDATA.BK and fplan.bk (and also a FPDATA.OLD)
Any idea which I should add to?
Many thanks
Join Date: Mar 2008
Location: Bingley
Age: 71
Posts: 5
Likes: 0
Received 0 Likes
on
0 Posts
They appear to be different versions of the same data maybe for backup. Do not attempt to edit them I believe they have check sum keys associated with them.
In any event you do not need to edit them, if you need to change data there use the normal interface.
In any event you do not need to edit them, if you need to change data there use the normal interface.
