Pilotedge with Foreflight

[pellelle@hotmail.com]

HI quick question. I was trying to use foreflight mobile with Pilotedge for traffic and was not able to see the traffic option within Foreflight (i have a ForeFlight Pro Plus USA subscription). I followed the configuration instructions as follows:

Navigate to the * plane/Resources/plugins/PilotEdge/VSPro Resources* folder
rename the VSProTrafficRelay.bak file to VSProTrafficRelay.ini
open the VSProTrafficRelay.ini file and insert the IP address of your iPad (ie, 192.168.1.10)
Connect to PilotEdge and enable Traffic within ForeFlight

The problem is that I can't see the the traffic option in the menu of Forefligt. Is there something particular I need to enable in foreflight to allow for traffic visualization (do I need a different subscription)?

Foreflight is enabled to work with my X plane 10 and I currently use it for my flights with PE.

Thanks

[Keith Smith]

It sounds like everything is configured correctly. Can you verify that you connected to PilotEdge AFTER you changed the ini file and not before? The file is read at the time you connect to the network.

[asad112]

The most basic subscription will get you traffic. More than likely it is an issue with your PilotEdge configuration ForeFlight won't allow you the option to enable traffic if there is nothing feeding it data (I.E., ADSB receiver, or PilotEdge config).

[barcman1967]

Do you have traffic selected in the map overlay options? I think it is in the same area as weather, etc.

[pellelle@hotmail.com]

Hi. I confirmn that I have connected to Pilotedge several times after i changed the ini file. Also, the problem is that I do not have the traffic option to select in the map overlay options. I only have Radar, Satellite, Hazard advison then air/sigmet/cwas etc (no Traffic option).

What i did was to change the extension of the VSProTrafficRelay.bak from bak to ini (as such, there is no longer a .bak file). The only IP address that the The ini file has is that of my Ipads ip address (as it appears by pressing the blue circle in the wifi options). I eliminated the original IP address that appeared in the file. is this the correct way? or did I make a mistake?

Other usefull information is that I use two ipads normally in pilotedge. I put the ip address of my main Ipad in the file. Could it be that there is a conflict because of the two ipads? They seem to work well with X Plane.


Thanks for your help.

[Keith Smith]

All of that is correct. Is xplane configured to send gps to that iPad? Traffic is only likely to work if you are sending gps and ahrs data from xplane already.

[stealthbob]

A good place to confirm that you are properly connected is in the Devices tab in FF

It should indicate that X-Plane is connected and green

[pellelle@hotmail.com]

My Ipad is indeed conected to X plane 10. All my PEdge flights have been done with the assitance of Foreflight (the only thing that doesnt work is traffic...that is I dont see the traffic option). Toinght I will try starting X plane 10 and conecting to pilotedge prior to opening the foreflight in the IPAD. Maybe my mistake has been opening foreflight prior to connecting to pilotedge each time. Ill let you know if this makes a difference.

[stealthbob]

Another check would be to verify the correct ip you have....

I don't have it in front of me but I think there is an "I" symbol top right in the devices screen...that indicates the correct IP the iPad is connected to. Verify that to the IP in the PE plugin.

[Keith Smith]

This is a stretch, but if xplane is configured to broadcast to all ipads, then firefight might ignore the packets that come from pilotedge with a specific target address.
To test this, make sure that xplane is configured to send foreflight data to the same ip as the address in the ini file rather than the broadcast option. that's all I can think of.