Gents,

 

I have decided I am going to tackle the Proline 21 Avionics by myself, the only obstacle I am finding at this point is building the FMS. I know its going to be a complicated process, however I am only really focused on the Lateral Navigation abilities, could someone steer me in the right direction as how to work with the AIRAC NavData. Do you use the default GPS map with nothing displayed and then overlay the intersections? Any help or a point in the right direction would be greatly appreciated, thank you!

 

-Matt Chase

Matt

 

1. there is a freeware FMS , it's complex , but studying its code might help.

 

2. Get the following it's freeware " fs9gps Complete Guidebook v1.1 " , there is a lot of reading in that

magnificent document , it will give you the structure of VOR , ADF , Intersections , airports and how to conduct searches for them , I assume that it is these together with their indexes that you will have to assign.

 

3. Try either an Email to NAVDATA or if they have a forum , I suspect that they would want to provide access data

to instrument developers to maximise the useage of their NAVDATA packages .

 

4. For data entry the following might help :

Cockpit Commander , Com Gold ,

also aircraft that have a UFC (Up Front Control ) keypad examples are payware :-

Aerosoft F-16

VRS F-18 Superbug

Milviz F-15E

 

Good luck .

Cheers

Karol

If you wish to search/read nav data from any type of file, then you will have to code entirely in C or C++ since XML has no ability to do file reads or file writes...

 

Also, the FMS will need to be coded in C or C++ for much the same reason as above. Creating a flight plan is pretty useless if you have no way to save it, or load a previously saved FP...

Thanks for the replies gents! If I was to do this in C# via simconnect my only question is what would I use to create the platform (ND) to display the Airac Data, I guess this is where I'm stumped, I know how to parse and read the data for the most part, and I know I'll need to use GeoCalcs to search the nearest waypoints if I want to display them, I'm just not sure how to start the ND display.

You can not make gauges with C#, gauges that show in FS have to be made using either the XML parser language or C/C++.

I use the default gps-map only showing the flightplan-line with custom-made text and symbols, all xml.

 

See Ed's ND:

 

http://forum.avsim.net/topic/71886-moving-map-display/page__st__25__hl__hud#entry1776186

That topic is so old that even my attempt several years ago to recover the XML script is borked, and since it's over 180 days old no (re)editing or new posts are allowed...

 

BTW, I truly HATE this new forum's method of (re)formatting XML scripts in the CODE box! :mad:

 

So, here once again is the recovered XML script example:

 

<!-- Draw GPS Map -->
<Macro Name="c">"C:fs9gps</Macro>
<Macro Name="g">C:fs9gps</Macro>
<Element Name="MapView Pages">
<Visible>(L:EFIS MODE, number) 2 == (L:EFIS MODE, number) 3 == || </Visible>
<Position X="0" Y="0"/>
<MaskImage Name="PS737EFISMASK.bmp" ImageSizes="400,420"/>
<CustomDraw Name="fs9gps:map" X="400" Y="726" LayerTerrain="Yes" LayerBorders="Yes" LayerFlightPlan="Yes" FlightPlanLineWidth="4" ActiveColorLayerFlightPlan="0x7010B0" PastColorLayerFlightPlan="0xF0F0F0" ColorLayerFlightPlan="0xF0F0F0" Bright="Yes" CenterX="200" CenterY="363">
 <Zoom>(L:EFIS MAP RANGE, number) 1852 *</Zoom> <!-- 1852m is 1 nautical mile -->   
 <Latitude>(A:GPS POSITION LAT, Radians)</Latitude>   
 <Longitude>(A:GPS POSITION LON, Radians)</Longitude>   
 <Heading>(A:GPS GROUND TRUE TRACK, Radians)</Heading>
 <DetailLayerTerrain>1</DetailLayerTerrain>   
 <LayerAirports>(L:EFIS MAP SHOW APT, bool)</LayerAirports>   
 <LayerVORs>(L:EFIS MAP SHOW VOR, bool)</LayerVORs>   
 <LayerILSs>(L:EFIS MAP SHOW ILS, bool)</LayerILSs>   
 <LayerNDBs>(L:EFIS MAP SHOW NBD, bool)</LayerNDBs>   
 <ObjectDetailLayerAirports>0 0 0 0 0 0 0x5 0x5 0x7 0x7 0x1F 0x1F 0x1F 0x1F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 24 (@g:map_ZoomStep) case</ObjectDetailLayerAirports>   
 <TextDetailLayerAirports>(L:EFIS MAP SHOW APT, bool) (L:EFIS MAP RANGE, number) 40 < ==</TextDetailLayerAirports>   
 <TextDetailLayerVORs>(L:EFIS MAP SHOW VOR, bool) (L:EFIS MAP RANGE, number) 40 < ==</TextDetailLayerVORs>   
 <TextDetailLayerILSs>(L:EFIS MAP SHOW ILS, bool) (L:EFIS MAP RANGE, number) 40 < ==</TextDetailLayerILSs>   
 <TextDetailLayerNDBs>(L:EFIS MAP SHOW NBD, bool) (L:EFIS MAP RANGE, number) 40 < ==</TextDetailLayerNDBs>   
 <ObjectDetailLayerFlightPlan>0xE 0xF (@c:FlightPlanIsActiveApproach) ?</ObjectDetailLayerFlightPlan>   
 <TrackUp>1</TrackUp>
</CustomDraw>   
</Element>

I use the default gps-map only showing the flightplan-line with custom-made text and symbols, all xml.

 

See Ed's ND:

 

http://forum.avsim.n...ud#entry1776186

 

Hi Jan,

 

I would like to get a copy of your navaid symbol xml vectors if you don't mind sharing. I'm sure they all look very nice.

 

I'm writing another guidebook, this one for the CustomDraw fs9gps:Map, FS9 & FSX, and I have a chapter on map projections, scales, and overlay schemes. If you allow, I could reference your vector symbols in that section.

 

Regards,

 

Bob

 

XML has no ability to do file reads or file writes...

 

unless you use LOGGER

I'm interested in the definition of " file reads and file writes " .

 

I have created xml radars that seem to read files perfectly adequately and display just about all the

text data you could wish for .

Similarly I have created a xml mission adaptive flight planner that is ICAO based that can modify

existing saved flight plans or create complete complex flight plans from scratch .

While those freshly created flight plans cannot be saved for future sim sessions it remains that

an incredible amount can be achieved with xml.

 

Cheers

Karol

Bob,

 

What e-mail adress?

Jan,

 

[email protected]

Hi Jan

 

I am also interested in trying this would you send me a copy?

 

Thanks Paul

Paul,

 

What e-mail adress?

Then i can send you a copy of my mail to Bob.

Jan, please add me to the list of recipients as well: [email protected]

Fr. Bill,

 

Arrived.