It appears from a quick test that a route triggers in order of turnout number, not internal or sensors. So a turnout with a number higher than the turnouts in the route should react after the last turnout command is given.
I'm running into a similar problem on my old module that I've just installed signals on. It used to use routes for setting the turnouts (I did it quick for a modular meeting), but the decoder has a long delay between starting each motor (it only does one at a time) and the max delay in a route is 1s, much shorter than the decoder, meaning I can't get the program to workout when they have finished, so would have to have a 1 minute delay for the signals to ensure all turnouts have moved. Looks like I'll have to put this one into Logix where delays can be long enough. At least it will then be compatible with the newer modules, and I can have parallel moves.
Mike
