The most obvious scenario, where you have routes on an IFD and want to transfer them to the IFD100 seems pretty straightforward. Likewise, I think if you have routes on the 100, and want to transfer them to the panel, that seems to mostly work as expected. 

What happens if you pair an IFD100 to a different IFD, or the IFD simulator on another iPad? Could you use the IFD100 to move routes between two aircraft with different IFDs?

If you create a route on the 100, and then bring the iPad to the cockpit, should that route transfer to the panel?

I’ve seen some strange behavior when moving iPads between planes, and I’d like to know what I should expect. 

Thanks!

We've done a lot of work lately on stored routes to improve that model so that you'll be able to more reliably share individual routes between IFDs and IFD100 and offline usage will no longer pose a problem.  Those changes will be included in the next software release.

Sometimes it works perfectly, but others it counts up slowly or pauses sporadically.

Occasionally, both the 100 app and the panel seem to choke on a shared stored route, with the soft keys pulsing and no progress despite multiple attempts. 

Clearing the route on the 100 seems to fix this issue on both. 

I’ve also seen routes that appear to have transferred, but are devoid of waypoints on one or the other device. 

This maybe an odd use of the stored routes function, but it’s common in our operation to stitch together routes on the fly based on weather conditions or other factors. There is a push to standardize some segments of some routes based on impacts to people on the ground, but we like to change up the arrivals to or departures from those sensitive areas. Ideally incorporating these segments by name in other routes, or specifically the active route, would be quite handy; sort of a user defined airway.