Interfacing the AP to other EFIS makers?????

[Brantel]

Dynon,

I would like to know the possibility of something.....

Most of your competitors have the ability to drive stand alone GPS Steering enabled AP's with many different data sources.

That being said, say for instance someone wanted to use a competitive EFIS and just use your EFIS/AP combo as the AP and standby EFIS. In this scenerio Dynon would need the ability to put the Dynon AP in GPSS and GPSV mode and just follow the commands.

In this setup, one could either drive the AP directly from the normal Data Sources or from the competitive EFIS that is outputing GPSS/GPSV labels over ARINC429? This would allow for AP data source redundancy.

Is this possible today (after the release of the AP76) to follow any generic GPSS/GPSV ARINC 429 commands that may be comming into the HS34 from a competitive EFIS?

Since the GPSS/GPSV stand alone autopilots fly these labels (as output from competitive EFIS's) and Dynon accepts these labels from radios such as the 430W, this seems like it should be possible???

 

[dynonsupport]

ARINC-429 labels are ARINC-429 labels. When we support GPS steering over ARINC, then we'll have no idea where the data is coming from. If you want to send us GPSS signals from an EFIS, it should work, just be aware that the performance of the AP is now based on how well the EFIS flies us, not our own internal algorithms.

One would wonder why you would want to do this though. The main reason this is done is because TruTrak charges a ton to follow NAV sources, so EFIS manufacturers lie to the system by converting NAV to GPSS.

Since the Dynon AP will naively fly a VOR or ILS, there isn't much reason to put another EFIS between the two systems. It just reduces reliability and increases confusion.

 

[Brantel]

The reason someone might want to do this is this....

They have a panel full of AFS, GRT, MGL or other EFIS's and want to ad an AP.  The Dynon AP would be much cheaper than a stand alone GPSS/GPSV enabled AP plus you get an EFIS for free.  Can't beat that hu?

Face it... Some people are sold on GRT or AFS and they ain't going to change.  

The ability to do this would allow the competitive EFIS to do everything they do but drive the Dynon AP same as a stand alone unit.  They then get an EFIS for backup for free.

GPSS and GPSV basically take your algorithims out of the equation anyway and puts that burden on the ARINC source creating the steering labels.

This would be no more confusing than a AFS/GRT unit coupled to a stand alone AP.

No different reliability wise either.  That is why most people with GRT/AFS units have an AP nav source switch for both serial and ARINC data.

My panel will be Dynon all the way so I do not plan to do this myself but it might be an option for those with competive EFIS's that are shopping for an AP.  If it works SELL IT while they will buy it!

Why would Dynon not want to position it's AP/EFIS(Efis being a great byproduct of the AP but not the primary reason to use the solution) in direct competition with stand alone units?

Here is mine:  

ARINC-429 labels are ARINC-429 labels. When we support GPS steering over ARINC, then we'll have no idea where the data is coming from. If you want to send us GPSS signals from an EFIS, it should work, just be aware that the performance of the AP is now based on how well the EFIS flies us, not our own internal algorithms.

One would wonder why you would want to do this though. The main reason this is done is because TruTrak charges a ton to follow NAV sources, so EFIS manufacturers lie to the system by converting NAV to GPSS.

Since the Dynon AP will naively fly a VOR or ILS, there isn't much reason to put another EFIS between the two systems. It just reduces reliability and increases confusion.