Author: Paul
Subject: 540 Interoperability
Posted: 22 Aug 2014 at 5:37pm
MikeK,
Currently the only way to use Connected Panel is to have some expensive Aspen gear. It requires a CG100 Connected Gateway. That requires an EFD500 or EFD100 MFD, and I think that requires a PFD. That is a whole lot of stuff to add just to be able to copy a flight plan from ForeFlight into a panel GPS!
If Avidyne were to implement code so their WiFi transceiver could be a Conected Panel server then Foreflight would "just work". So would WingX and any other tablet software that implemented CP.
But Avidyne hasn't done this and it doesn't sound like they are going to. Which means it is either technically very difficult or that Aspen's licensing prevents it. The software engineers at Avidyne seem to be smart people. So I'm betting it is the licensing. If so, the CP community should either kick Aspen into allowing open use of the protocols or it should adopt a different set of protocols that everyone can use.
Subject: 540 Interoperability
Posted: 22 Aug 2014 at 5:37pm
MikeK,
Currently the only way to use Connected Panel is to have some expensive Aspen gear. It requires a CG100 Connected Gateway. That requires an EFD500 or EFD100 MFD, and I think that requires a PFD. That is a whole lot of stuff to add just to be able to copy a flight plan from ForeFlight into a panel GPS!
If Avidyne were to implement code so their WiFi transceiver could be a Conected Panel server then Foreflight would "just work". So would WingX and any other tablet software that implemented CP.
But Avidyne hasn't done this and it doesn't sound like they are going to. Which means it is either technically very difficult or that Aspen's licensing prevents it. The software engineers at Avidyne seem to be smart people. So I'm betting it is the licensing. If so, the CP community should either kick Aspen into allowing open use of the protocols or it should adopt a different set of protocols that everyone can use.