This would be great. Right now I'm having to continue to use the Stratus 2 for my foreflight... and by doing so I lose my flight plan transfer to/from foreflight. Can't connect foreflight to stratus and IFD at same time. Well at least by default.

Actually, you should be able to connect to both Stratus and the IFD, from what I've been reading here. The trick is to set the IFD in remote WiFi mode and have it use the Stratus network. Your iPad would also connect to the Stratus network and then your IFD and Foreflight can communicate with each other. ForeFlight would then get traffic and weather from Stratus and would still transfer flight plans to and from the IFD.

One thing I wish is that there was a dual-band ADS-B solution from Avidyne. I have a SkyTrax100 that is UAT-only. I get traffic but only from planes with UAT transponders or towers broadcasting the information. Last week for some reason I was not getting traffic from a friend flying nearby with a GTX345 transponder. I don't know if the ground stations had an issue, but in any case it appears I wasn't getting the rebroadcast signal. Firing up Stratux allowed me to see the other traffic directly through its transponder signal. I also flew to Mexico and it would have been nice to see any 1090MHz ES transponders.

I don't trust Stratux enough to hang my IFD onto its network (don't even know if it is possible), but I sure would like dual-band reception. If I had a Stratus 2S, I might not turn it off.

This would be great. Right now I'm having to continue to use the Stratus 2 for my foreflight... and by doing so I lose my flight plan transfer to/from foreflight. Can't connect foreflight to stratus and IFD at same time...

Can't remember, are you having specific troubles with that? Connecting to both (Stratus <-> IFD + tablet) with remote mode on the IFD is a supported setup with 10.2.1, and I have done just that. Actually, it got it working with 10.2.0, most of the time.

The hardest part might be figuring out what address the Stratux gets assigned by the IFD. You always have the option of statically assigning it an ip that is in the IFD's network range, might be a good idea to do that with your Tablet as well so that things don't change between flights.

If you attach a Stratux to the IFD network, and also have a SkyTrax100/MLB100 installed, does the duplicate traffic and weather information interfere with each other on ForeFlight? I assume the IFD only displays the SkyTrax information.

I was going to test it at sun n fun but the Stratux that I grabbed and put the experimental firmware in had no AHRS module. I had taken it out the week before to do some antenna testing and forgot to put it back in.

This would be great. Right now I'm having to continue to use the Stratus 2 for my foreflight... and by doing so I lose my flight plan transfer to/from foreflight. Can't connect foreflight to stratus and IFD at same time...

Can't remember, are you having specific troubles with that? Connecting to both (Stratus <-> IFD + tablet) with remote mode on the IFD is a supported setup with 10.2.1, and I have done just that. Actually, it got it working with 10.2.0, most of the time.

* Orest

I did not know that was a change with the update. I will need to dig into the manual to see how that's done. So you're saying the Ipad (foreflight) can connect to both the Stratus and IFD at same time?

I knew there was a configuration where the Stratus could function as the "wifi server" to both the Tablet and the IFD but I just didn't want to got that route to have any strong reliance on the portable Stratus.

So you're saying the Ipad (foreflight) can connect to both the Stratus and IFD at same time?

I'm not aware of any way to do that since the iPad has only one WiFi radio. You can connect Foreflight (i.e. iPad) to the IFD directly (local WiFi mode) or through the Stratus (Remote WiFi mode). Regardless of which way you do it, you can transfer flight plans between Foreflight and IFD, but those are the only two usable configurations I'm aware of.

HenryM wrote:

I guess the trick would be to figure out how to connect the Stratus to the IFD network, rather than setting the IFD to Remote WiFi. I don't have a Stratus, so I don't know if this is possible.

ForeFlight Mobile doesn't currently support receiving ADS-B traffic from Avidyne ADS-B receivers (or through the IFD540 WiFi connection), but that's something we're hoping to add in the future.

I'm looking forward to seeing the response from Avi support so I can finally get an answer about whether the IFD is emitting GDL90 or not. I've heard both that it is and that it isn't. It is irritating me that I can get better compatibility with a Stratux (a direct competitor to a big chunk of FF's revenue) than with my IFD.

If I understand the thread dilemma, with the Stratus WiFi talking with our IFD's, is it that FF does not display the SkyTrax Traffic on FF?

I have been routing my IFD540 WiFi as "Remote" using the Stratus box, allowing flight-plan transfers to/from FF and IFD. Traffic displayed on IFD is Skytrax and Traffic on FF/iPad is from the Stratus directly.

So until FF receives our Skytrax UAT traffic directly from the 540-WiFi, the work around is to have the two separate sources of traffic displayed.

Incidentally, for all of you FlyQ SA users, our IFD540 Skytrax UAT traffic (and Wx) does currently integrate quite well with the iPad SA FlyQ App and does display Skytrax derived ADSB on the iPad App... just saying.

Thanks, Tom-- there are 2 issues commingled in this thread. One is getting the IFD and Stratus to coexist with an iPad so that they all play together nicely. I'm not trying to do that; I get Stratus traffic on FF and Skytrax traffic on the IFD and am OK with that for the time being. Hats off to the brave folks who are battling this-- it sounds like there have been lots of false starts and dead ends along the way.

The other issue is getting IFD traffic on FF. I know it works with FlyQ (and a few other apps), and I like FlyQ just fine, but it doesn't replace FF's capabilities for me so it's not a solution. I can deal with the aggravation of having to keep my Stratus on the glare shield or the aggravation of having to use FlyQ instead of FF :)

FF has a development center nearby. It appears Avidyne is slightly different than other providers despite the claim of using Capstone (GDL-90) format. This was before FF 10 came out. I'm disappointed FF10 didn't fix whatever the underlying issue is. They (FF) are aware of the problem and it is on their list to implement whatever special processing Avidyne needs. However, I don't know if there is a schedule for it.

Yea I can confirm that Foreflight still needs some work. Flying around today had good success with Aerovie receiving traffic and FIS from the Skytrax 100 via Wifi from the IFD540. But not Foreflight.

Going one step farther I grabbed a couple wireshark packet traces and the IFD isn't sending to UDP port 4000 which the open protocol spec shows. Probably no surprise, but the open spec does allow vendors to supply data without waiting for Foreflight development. In this case the plugin needs to be finished by Foreflight. Several other vendors have implemented the protocol. Aerovie is nice, but not a full replacement to Foreflight yet. Oh well..

Running a Stratus(x) on longer trips is fine with me for now to have a backup. But it would be nice to have one solution.

What I would really like is to be able to use the IFD-540 in local WiFi mode and have a Stratus or Stratux connect to the IFD network. I may or may not have a portable device with me, and rather than be changing the access point to be the portable device, I'd like the portable device to connect to the existing network. Then I could get data to ForeFlight either from the IFD or the portable device without having to be changing settings in the IFD. I have a TSO'd, robust device in my panel. It should more reliable than the portable device. It is always in the plane.

I know this isn't an Avidyne issue. I've forwarded a suggestion to Appareo. If others do the same, maybe they'll listen. Maybe Avidyne has some pull there too.

I complained to Appareo over a year ago about FF not being able to be a client. I felt the same as others here. Why would I want my mult-thousand dollar, TSO'd, certified, in-panel device to be a network client of a device held in my airplane by velcro.

I normally fly with the IFD as the server and just switch back and forth between the IFD 100 and Foreflight as needed. With the latest release of FF, I now get this message every time I switch to FF if I have not closed out of the IFD 100. It does not seem to impact FF in anyway so once I hit "OK", FF still seems to operate normally.

I normally fly with the IFD as the server and just switch back and forth between the IFD 100 and Foreflight as needed. With the latest release of FF, I now get this message every time I switch to FF if I have not closed out of the IFD 100. It does not seem to impact FF in anyway so once I hit "OK", FF still seems to operate normally.

I can't read the message as it is too small and I can't zoom on it either. What does it say?

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot delete your posts in this forumYou cannot edit your posts in this forumYou cannot create polls in this forumYou cannot vote in polls in this forum