IFD100 Information

oskrypuch wrote: Steve, You mentioned that you were running it on the Surface, was that the 4 or the 3? It ran "all right" there? * Orest

I happen to have a Surface Pro 4 and it runs fine there.

brou0040 wrote: Does the #1 standby between the 540 and 100 sync regardless of their respective location on the screen?  I've never used more than one standby, but the manual states that whichever one is touched is the #1 standby.  In that case, If I had only active and standby on the 540 and 4 comms on the 100, I'd just select whichever freq I want on the 100, which makes it the #1 standby, which pushes it to the standby on the 540 and I can hit the swap from there?  Your examples just happen to have the #1 standby on the 100 as being the second frequency (same order as on the panel mount). Can you make a comment on the general horsepower required for a 100 tablet?  My guess is that the iPad and Surface Pro are way overkill.  Is there a lot of processing required to run the 100 or is it pretty tame in the background?

It's the #1 standby that is sync'd. You can make any of the standby slots the #1 standby simply by touching it. That leaves you up to 3 more standby slots to do with what you please. Those additional standby slots do not sync so you can have up to three per IFD550/545/540/510/440/410/100.

I think we'll characterize the required horsepower with more precision over the coming weeks. It is running the full IFD code including the gigantic terrain database so it is a bit of a memory and processing hog.

Edited by AviJake - 17 Apr 2016 at 1:09am

Nifty.  And unavailable to 80% of tablet owners, like me.  Rats.

Edited by MysticCobra - 16 Apr 2016 at 11:31pm

I just don't understand the need for NAV/COM at all on the IFD-100, since it isn't actually a radio.  I see the IFD100 as more of an extra display, rather than a remote control device, but maybe I'm missing something?  I should always be in arm's reach of my NAV/COM, so why do I need to twiddle the knobs on the iPAD to change frequencies?  Also, I would hate for a co-pilot or passenger to accidentally change my frequency while "playing" with the iPad.  I plan to eliminate the frequencies from the display altogether on the IFD100.  This is possible, right?

AviJake wrote: 1.  We've made the changes in the app to now allow full com sync'ing and control from the IFD100.   Unlike dual panel mount IFDs which have no ability to control and display the other box's VHF radio, the IFD100 is able to control and display VHF com on the panel IFD that it's connected to via WiFi.   That's two-way so if you make the change on the panel IFD, the iPad version changes to follow.

I think a lot of folks "get" the utility of this capability.     I like to think I'm not often susceptible to hyperbole but here comes a clear violation of that.

This capability is unbelievable.   For me, it completely changes the game in managing my cockpit tasks, especially those involving avionics and their role in your flight.

I fly test flights with a dual IFD set up and either one or two iPads running IFD100 and of course the Bluetooth keyboard.   I try combos like:

1 IFD5XX, 1 IFD100, 1 Bluetooth keyboard
1 IFD440, 1 IFD100, 1 Bluetooth keyboard
1 IFD540, 1 IFD440, 1 IFD100, 1 Bluetooth keyboard
1 IFD550, 1 IFD540, 1 IFD100, 1 Bluetooth keyboard
1 IFD550, 1 IFD540, 2 IFD100, 1 Bluetooth keyboard

When flying the 550, 540, 100, 100, keyboard combo, it's just sick.  It is the full glass cockpit experience.

I apologize ahead of time for any jealousy this may create - patience will have to remain virtuous.  I will also say we are pulling the oars as fast as we can to get this all done and shipping and in your hands.

I have three to four pages I typically use in flight so I set each device up to be on one of those pages so I really don't have to touch them at all in flight.

I also am addicted to the Designated Waypoint Info datablock in Release 10.2 and I actually set up a different Designated Waypoint in each device so I have 4 running at all times.  The spatial/positional awareness that provides is a quantum leap in capability all by itself.

I personally mount one iPad Mini to the yoke in front of me.  I put a second iPad Mini on the other yoke and adjust it to be facing me or I put it on my kneeboard on my right leg.

I'm about to create a mounting scheme where I can mount a full sized iPad over my instrument panel instruments that are right in front of me.  I can literally snap the iPad over the instruments.  That leaves the original instruments untouched and still there if I ever need them in the heat of the moment.  Zero mechanical impact to your airplane and no impact to the cert basis.   You can see where we're going with respect to legacy airplane upgrades - leave your steam gauges alone, put in one or two pedigreed IFDs in the center stack and just snap mobile devices over existing panel.  Augment that set up with desired peripherals like ADS-B devices and voila.  The IFD100 app enables all of this.

Here are a few action shots I took yesterday during a flight.   It was
just me, it was very bumpy, it was an iPhone, and I'm not related to
Ansel Adams.

I like to set up taxi chart on the iPad - it's bigger, closer to me and obviously supports pinch zoom.





Here is a shot showing the Map Syn Vis feature that everybody gets on their IFDs (all flavors) as part of 10.2.0.0.  Note my keyboard on my kneeboard (remember that I can do full page navigation now using that with 10.2):




Here's a picture of what FLTA terrain alerts look like on the IFD100.  Note that the picture was taken the instant it went to red warning and the CAS message was presented a split second after the picture was taken.





Here's a shot of both IFD100s running on the two iPads with flight plan page pulled up so you can see the sync'd flight plans.  You may also be able to see one of the GoPro's I have mounted in the airplane in the reflection of the right iPad.  When I get some time, we hope to post some videos of this stuff in action from the GoPros.




And here's a shot of my standard config when shooting an approach.    550 is in SVS page, 540 is in Chart view, IFD100 in Flight Plan page, and 2nd IFD100 (out of view from picture) on Map page. Note the glideslope/path indicators in the IFD550, the runway in the distance and the velocity vector which is on the runway.   I just shake my head on these approaches and wonder why I even need to be in the cockpit - I do nothing other than watch a cool show.  Approximately zero pilotage skills required.













Edited by AviJake - 17 Apr 2016 at 12:18am

shhhh......don't tell Orest.

Hmm, and just when might it be of use to us all?????  

Edited by oskrypuch - 13 Apr 2016 at 4:45pm