Feature request for additional API/SDK capability

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   The IFD 100 is a great tool and selling point for the IFD boxes, but despite perceptions to the contrary, not every pilot owns or wants to own an Apple device.  There is a large population of Android users out there who can't benefit from what the IFD 100 offers.
Avidyne has done something no other avionics manufacturer has, though: They've opened access to their panel-mounted devices via an API/SDK to allow integration between phone/tablet apps and some IFD features/capabilities.  It's not exactly possible to recreate the IFD100 capabilities using this access path, but it does still provide some potential benefit to users who don't use the IFD100.  It also offers additional features separate from the IFD100, like Flight Plan sharing between Avidyne devices and 3rd party apps, etc.  Android users may not be able to use the IFD100 features, but this API/SDK interface still offers some integration capabilities that set Avidyne apart from the competition.

I think the API/SDK could be enhanced to provide even more integration and value.  These increased capabilities could expand Avidyne's market differentiation from competitors and help draw customers who appreciate interoperability between devices from different vendors and dislike the lack of integration offered by Avidyne's competitors, as well as appeal particularly to users who don't have Apple devices.

To this end, I would like to propose expanding the options supported by the API/SDK.  Here are some ideas I would like to see implemented, in approximate priority order:
Set Standby comm frequency in Avidyne from 3rd-party app
Toggle Stby/Active comm frequencies in Avidyne from 3rd-party app
Use software keyboard on 3rd-party app to enter data on Avidyne
3rd party app control over Avidyne display selection.  Specifically:
Use 3rd-party app to quickly select an Avidyne screen (have buttons in 3rd-party app that immediately pull up the Avidyne FP page or User Setup page, etc., or pull up a menu of all possible Avidyne pages, etc.)
Toggle right-side "pull-out" details pane on current page , if present (i.e., cycle through hidden/small/large sizes on the Flight Plan page for instance)
Expose some subset of useful datablock/data fields to 3rd party apps
Fuel consumption rate, fuel totals, next waypoint, ETA to next waypoint, destination, ETA to destination, etc.
Expose IFD software version so 3rd party apps can figure out which API/SDK features are implemented? 
Receive alerts from Avidyne and clear Avidyne alerts from 3rd-party app (the messages that pop up in the lower-right corner of the Avidyne screen and require a finger-tap to clear)
When IFD has multiple ADSB-in sources (say, a Skytrax 200 and also a wireless ADSB-in receiver like a Stratus or Stratux), allow 3rd party device to select which device's data is being consumed by IFD
I suspect some of these requests may be impractical to implement (software keyboard?), but I think at least some of them would probably be pretty easy (comm freq set/toggle).  (I'm also actually not sure how the IFD currently handles the situation where it has ADSB-in data available from multiple devices.)

Edited by MysticCobra - 25 Jun 2023 at 12:16pm

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
MysticCobra Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 29 Jan 2013 Status: Offline Points: 652	Post Options Post Reply Quote MysticCobra Report Post Thanks(0) Quote Reply Topic: Feature request for additional API/SDK capability Posted: 25 Jun 2023 at 11:44am
	The IFD 100 is a great tool and selling point for the IFD boxes, but despite perceptions to the contrary, not every pilot owns or wants to own an Apple device. There is a large population of Android users out there who can't benefit from what the IFD 100 offers. Avidyne has done something no other avionics manufacturer has, though: They've opened access to their panel-mounted devices via an API/SDK to allow integration between phone/tablet apps and some IFD features/capabilities. It's not exactly possible to recreate the IFD100 capabilities using this access path, but it does still provide some potential benefit to users who don't use the IFD100. It also offers additional features separate from the IFD100, like Flight Plan sharing between Avidyne devices and 3rd party apps, etc. Android users may not be able to use the IFD100 features, but this API/SDK interface still offers some integration capabilities that set Avidyne apart from the competition. I think the API/SDK could be enhanced to provide even more integration and value. These increased capabilities could expand Avidyne's market differentiation from competitors and help draw customers who appreciate interoperability between devices from different vendors and dislike the lack of integration offered by Avidyne's competitors, as well as appeal particularly to users who don't have Apple devices. To this end, I would like to propose expanding the options supported by the API/SDK. Here are some ideas I would like to see implemented, in approximate priority order: Set Standby comm frequency in Avidyne from 3rd-party app Toggle Stby/Active comm frequencies in Avidyne from 3rd-party app Use software keyboard on 3rd-party app to enter data on Avidyne 3rd party app control over Avidyne display selection. Specifically: Use 3rd-party app to quickly select an Avidyne screen (have buttons in 3rd-party app that immediately pull up the Avidyne FP page or User Setup page, etc., or pull up a menu of all possible Avidyne pages, etc.) Toggle right-side "pull-out" details pane on current page , if present (i.e., cycle through hidden/small/large sizes on the Flight Plan page for instance) Expose some subset of useful datablock/data fields to 3rd party apps Fuel consumption rate, fuel totals, next waypoint, ETA to next waypoint, destination, ETA to destination, etc. Expose IFD software version so 3rd party apps can figure out which API/SDK features are implemented? Receive alerts from Avidyne and clear Avidyne alerts from 3rd-party app (the messages that pop up in the lower-right corner of the Avidyne screen and require a finger-tap to clear) When IFD has multiple ADSB-in sources (say, a Skytrax 200 and also a wireless ADSB-in receiver like a Stratus or Stratux), allow 3rd party device to select which device's data is being consumed by IFD I suspect some of these requests may be impractical to implement (software keyboard?), but I think at least some of them would probably be pretty easy (comm freq set/toggle). (I'm also actually not sure how the IFD currently handles the situation where it has ADSB-in data available from multiple devices.) Edited by MysticCobra - 25 Jun 2023 at 12:16pm

_phm_ Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 08 May 2023 Location: brazil Status: Offline Points: 64	Post Options Post Reply Quote _phm_ Report Post Thanks(1) Quote Reply Posted: 25 Jun 2023 at 5:30pm
	This sounds very interesting. I'm a true believer of open source / open protocols, and this kind of approach would certainly be beneficial for everyone. Would be willing to commit programming effort to make this happen.

rpostmo Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 20 Jul 2015 Location: North Dakota Status: Offline Points: 157	Post Options Post Reply Quote rpostmo Report Post Thanks(1) Quote Reply Posted: 25 Jun 2023 at 10:20pm
	Jim, all of that looks interesting. I can relate my current usage, may be subject to change. I am an Android user through and through. It pained me not to have Android access to the IFDs. But because the IFDs are so spectacular, I have subsequently purchased and now use an IPAD mini4, and and IPAD mini6. I use these to run the IFD 100, and either one works well. I keep one charged as a backup. I also use IFLY EFB and I think this program is also great....will not give it up. When I fly now, I program the IFD540 as my primary Nav/Radio. I connect the IFD100 on IPAD mini6 on my yoke, to the IFD440. I do not have the IFD 540 and IFD 440 cross-synced, I prefer to keep them separate. I use the IFLY EFB on my second tablet, either the IPAD mini4, or the Samsung Tab 10.1. I connect the second tablet to my NGT9000 by WiFi. I keep this on my lap. I put my approach plates on the lap tablet. I also use it for looking up additional data, watch it for weather and traffic, and generally keep it charged as a backup. I think I'm less and less inclined to continue to use the tablets to run the IFD 100 program, as the 540 is so reliable and easy to use, and the screen is large enough. I get so much more information by running IFLY EFB that I've recently been putting that on my yoke tablet, and not using the IFD100. I'm pleased there is effort going toward Android integration with the IFDs, and if I were running a IFD440 only, I would use the IFD100 all of the time because of the large screen. My impression is that I would continue to use the IFLY EFB in its full map and chart mode, without giving it up to run IFD100 real estate. Bob