540 Interoperability

The confusion is clearly understandable.  The devil is always in the details.

I'm sure more will come up but....

1. To some degree, yes.   For some, probably not ever.   We publish GPS position in an open, non-proprietary format.  If the listening device can take it, fantastic.   Clearly we are not optimistic that Garmin devices will ever willingly take 540 position data.   What complicates that even further are "approvals".  For example, even if the GTX330 can take 540 position data, the STC holder (or a new STC applicant) must amend their STC to add the 540 as a position source.   We don't have the ability to alter a Garmin STC (and vice versa).   We haven't taken the time to initiate the effort with BK on the KT74 being able to take 540 position data - it hasn't bubbled up high enough on our priority list.

2.  Yes, definitely.  We have publicly stated the 540 will support (as in display) Capstone data.  In fact, we've already started that effort for the next 540 and 440 release which is underway.

3.  We have a high priority project underway to have a solution for ADS-B In.   It will apply to both weather and traffic.

4.  Yes.

Steve,

Are there different rules for different types of connections?

I can connect an IFD to a brand X audio panel without any paperwork from the manufacturers saying the combination has been tested.

If I buy a brand X box that speaks Capstone does it need an STC in order to be connected to an IFD in my certificated aircraft?

In the case of the AXP 340, KT 74, and TT-31, does Avidyne and BK hold the STCs or does Trig?  Is the STC to use a position source unrelated to the certification of the transponder?

As for ConnectedPanel, we'll see.   We obviously love the concept but there is a proprietary interface/licensing challenge that seems to exist for it so our excitement has waned on that front.

Jake:

Thanks for the suggestion on iFly.  I'll take a closer look.

iFly has a nice product, but it knows nothing about airways. 

Edited by oskrypuch - 21 Aug 2014 at 12:54pm

Allowing the IFD to be used as a bluetooth GPS position source for iPads and other tablets would also be a useful feature as Apple only builds GPS into cellular-equipped iPads.

Paul wrote: If Hilton Software and ForeFlight were on board the rest would probably come too.  They're all frozen out of the Garmin ecosystem and would benefit from an alternative.

I agree with Mike.  If foreflight doesn't want to play with others, then I will look for another app (maybe there's an avidyne app coming?) that will work and play nice with the equipment I'm about to install. 

The Foreflight/Stratus thing is annoying.  But the Stratus doesn't drive an autopilot or set radio frequencies.  There is plenty of space for an IFD in their universe.  Garmin Pilot is their competition, not anything from Avidyne.  If I were a ForeFlight user with a GNS in the plane I'd be seriously tempted to buy a Flight Stream 210 and switch to Garmin Pilot.  For one AU (plus installation) it would give me a larger iPad screen, touch entry, victor airways, and more.

Foreflight did implement Connected Panel.  They're probably not real happy if it is tied to an expensive piece of Aspen hardware.

Meanwhile Garmin is the big competitor to Aspen.  The G500 has fallen behind in integration with the rest of their products but it wouldn't be surprising if they were to announce a firmware update that tied it with the Flight Stream 210, GDL-88, and Garmin Pilot.

Garmin is the big competitor for just about everyone in the industry.  No one company can match their product breadth and it would be suicide to try.  They can integrate their products to provide an experience no other company can match.

Maybe it is time for the Connected Panel partners to put pressure on Aspen to open the protocols.  If not then it is certainly time for someone else to propose a set of open protocols.

There are plenty of examples of industries where there is a dominant player with a closed ecosystem and a group of smaller players working with open standards.  For example in computer servers there is Microsoft and Unix / Linux, and in phones and tablets there is Apple and Android.

If the Avionics industry doesn't work on interoperability Garmin will be able to provide the best experience even though the other companies have better products.

Paul wrote: Foreflight did implement Connected Panel.  They're probably not real happy if it is tied to an expensive piece of Aspen hardware. <snip> Maybe it is time for the Connected Panel partners to put pressure on Aspen to open the protocols.  If not then it is certainly time for someone else to propose a set of open protocols.

Paul,

I don't know how CP devices communicate.  I did not find anything in the publicly available descriptions.  I assume one of the Aspen boxes handles interfacing CP to the Garmin GPS.

It would be nice if in a system where there is a CG100 it could handle the WiFi and the devices such as the JPI and the IFD could talk through it.  And in a system where there is no CG100 the IFD could provide the WiFi interface.  That would allow companies who invest in CP to leverage their investments to handle more configurations.

It is possible to design a protocol which allows a device such as an engine monitor to talk to a tablet through a device such as an IFD even if the IFD doesn't understand what the engine monitor is saying.  If Aspen didn't provide such a capability to CP they should add it.

Good Morning Steve,

I have not been monitoring this lest recently, but I do believe you have stated that certain actions can be taken by using a 337 as they are considered to be "minor alterations". May I suggest that only a major alteration requires a 337? If the installation is a minor alteration, all that is required is a log book entry by a suitably licensed individual.

Whadda Ya Think?

Happy Skies,

Old Bob

PS Where's my box! <G>

Old Bob,

Yup, of course you are right.  I don't know how I made that order of magnitude mistake.

"Minor alterations" = log book entry.
"Major alterations" = STC or 337.

Sorry for the blockheadedness.