iFly GPS Forum

I went back to the test setup and made a cheezy video ( https://youtu.be/lodJ0P3mOFc ) of attempting to get the bi-directional Interlink to work. I used an IPad Air2 running IOS 8 as the Master. The latest IFly GPS software on the Apple App Store is Ver 9.2.16. I am using the IFly 720 running 9.2.17. The two devices are connected via my cell phone HotSpot. I do apologize for the shaky video. I did this quickly - it's a lot of fun to juggle a camera, stylus, and two devices while making the movie single handedly. I could not get the bi-directional data updates to happen. Data changes from Master to Slave worked very well.

---

Aircraft Ferry Services, Jonesborough TN (IFly720/Air2/Tab3)

That's not bi-directional, OldPilot. That's uni-directional, and you're choosing which direction to share when you stop and start the sharing process.

I know that I can change which device is "master" and which is "slave", but once that's established it currently only shares from the master to the slave, and not the other direction.

That's why Jim McWhorter and I were confused about Shane and you saying that sharing should work in a "two-way" or "bi-directional" fashion: It doesn't.

For what it's worth - I don't think that the Data Interlink between two devices should be bi-directional. What real-world scenario could one think of where there is a need for data to travel back and forth between the devices. At best, in my humble opinon, the bi-directional capability would be a desktop novelty that would not be worth the development hours invested into it. The interlink between master and slave works, but has some issues. I'd would suggest that development resources focus on the issues - once they issues have been verified

1. The interlink does time out after a period of time somewhere between 4 to10 minutes. To reset the interlink, the Master user has to Open and Close the Flight Plan window. This reconnects the Interlink. The Master should be tasked to send a background pulse to the slave after a specified period of inactivity (maybe 2 minutes) to keep the interlink open. If the Slave does not respond, then the User needs to be notified via an error message.

2. I mentioned this in an earlier post - the Master needs to tell the Slave which aircraft profile is to be used, If the aircraft profile, does not exist on the Slave, the Master needs to send the data to the Slave and the Slave needs to create the aircraft profile. I think this is already on the Wish List

3. Transferring a flight plan from the Master to the Slave for which custom way points were created causes another issue. If the custom waypoints do not exist in the Slaves Custom Waypoint database - the Slave inserts these waypoints into its version of the flight plan as waypoints based on the Lat/Long coordinates. These new waypoints are not placed into the Slaves Waypoint database. As such, the Slave user cannot update the waypoint name, etc. The Interlink needs to force the Master to pass all of the custom waypoint data to the Slave and the Slave needs to create this Custom Waypoint in its Waypoint Database. I think I mentioned this in an earlier post as we..

4. If there is a problem with the WiFi network - IFly needs to display an error message alerting the pilot.

---

Aircraft Ferry Services, Jonesborough TN (IFly720/Air2/Tab3)