Is there a way to make a junction controllable only by User or Schedule Command?

[RFAX]

I am recreating our HO club layout in TS12 in order to test train orders for operating sessions. I am using the schedule library to build the train orders so that I can run multiple trains simultaneously. There are a few sections of track on the layout (bypasses, reverse loops) that should be off limits to most AI trains except those running certain schedules. Because some AI trains will need to run there I can't use direction markers to keep them out. I could use priority markers to keep most trains out most of the time but I would prefer strict control. Ideally I am looking for a way to do something like: Navigate to trackmark placed before the controlled junction. Send message to some controlling object to switch the junction. Drive to next trackmark, with the controlling entity returning the switch to its original position after the train has cleared the junction.
The key thing here is that the junction is locked so that other AI trains can't control it the way they would normal junctions, but also a way to message the controlling object to switch it. Does a tool set to control things this way already exist?

 

[JCitron]

Hi Mike,

I wonder if some of the path-control or junction control driver commands might work for this.

John

 

[ElStoko]

Path or junction controls only enforce a junction's switch direction while it is seized by a driver or the rule. Usually seizure is released once the target train has passed over a junction. If seizure was left in place over an extended period to force other trains to take a default route, then only AUTODRIVE commands (which don't require the seizure of junctions in the path ahead) would work to get these trains across the critical junction. Trains under AI control using "DRIVE TO" or "NAVIGATE TO" to cross an already-seized junction will stop and refuse to cross the junction until it is released.
Instead of using path or junction controls, you could simply place a track mark just beyond a critical facing junction on each alternative path : the default normal path and the 'special diversion' path. For most trains use "DRIVE VIA <normal-path track-mark name>" to pass over the critical facing junction. For trains you wish to divert, use "DRIVE VIA <diverting-path track-mark name>". "DRIVE TO" and "DRIVE VIA", unlike "NAVIGATE TO" and "NAVIGATE VIA", will only take the most direct route to a target track mark. If this route is not available the train will stop and wait. By this means no normal train will ever choose to take the diverting path.

 

[RFAX]

I was hoping to avoid having to add the extra commands to the schedules but wasn't aware that an AI train wouldn't cross a junction it couldn't lock (other than in autodrive). Useful info - thanks.

 

[KenRuof]

I have been using the "Multi Path" rule with great success. It takes a little set up but works good. You would also want the "ControlPath" driver command so multiple drives can use the same path.