Rules, Triggers, etc...

[Hot_Box_Detector]

I am running an 80 mile route with 4 coal consists, under AI. I line them up to depart at 30 minute intervals with all the driver commands. What is happening, is they will tend to bunch up at one end of the route or the other.
Is there a rule that will allow me to hold a train say, 10,20 or 30 miles out until the train ahead has delivered it's load and returns to a particular point, thus releasing the waiting train(s)?

 

[R701Rusty]

One way of doing this is to apply a "Wait for Trigger" command and set a trackmark (x?) at the place you wish to get the next train to stop at until the earlier one returns empty. Then you will need to find an appropriate spot to place a trigger. In your list of commands you would then tell the drivers to "drive to trackmark (x?)", 'wait for trigger' and set the trigger for each train you wish to have wait at the spot where the trackmark sits. Follow this with the rest of the orders to get your trains to do what you want.

Hope this helps.

Cheers
Russell.

 

[Hot_Box_Detector]

THanks,

I didn't think it would be that simple... I'll try that. It seems like if the trains are running in order, that would work.

 

[stagecoach]

Another good driver command is the post message and wait for message and clear. These commands dont need to know consist details as the message can only be recieved by the consst set up to use it. Train A returns to a suitable passing point and posts message ******** task one completed. Only a consist that has the wait for message ******** task one completed and clear will respond to it. Once a consist has got the message it is removed and can be used again by another consist. This way stops unwanted trains setting the trigger off by mistake.

 

[Deano5]

But you can set up the trigger to work with any one or all trains too.

 

[Hot_Box_Detector]

Well.... you may have answered my next question. If I am running 4 trains, and train 1 is unloading at the powerstation and train 2 appears at the trackmark and waits for train 1 to run it's routine and return to the trigger
all is well...unless train 3 appears, runs around the waiting train 2 and conflicts with both.
I think, at some point, this would turn into a scripted scenario very quickly...

 

[ShadyCadence]

Have you considered just altering the interval? Figure out how long it takes to drive to the location, unload a complete train and proceed to the bypass track. Subtract the time it takes the next one to arrive at the bypass, then round up to the closest time wait available.

 

[stagecoach]

With post message you would need to add the following to each driver command for it to work.

Drive to trackmark (A) ............this is the wait at TM
Wait for message and clear ...........Alistair completed task 0
drive to ........Power station and unload
Drive to trackmark (B) ...........this is the TM on the exit route when clear
Post message ..........Alistair completed task 0

Add the above to all 4 trains and it wont matter in which order they arrive and leave. You need one train leaving the power station at the start in order for the first post message to be stored for an incoming train.

 

[Hot_Box_Detector]

Have you considered just altering the interval? Figure out how long it takes to drive to the location, unload a complete train and proceed to the bypass track. Subtract the time it takes the next one to arrive at the bypass, then round up to the closest time wait available.

In a perfect world, that would work. But there are too many variables in a 160 mile round trip with 4 coal trains running and another delivering diesel fuel to the coal mine...

 

[Hot_Box_Detector]

With post message you would need to add the following to each driver command for it to work.

Drive to trackmark (A) ............this is the wait at TM
Wait for message and clear ...........Alistair completed task 0
drive to ........Power station and unload
Drive to trackmark (B) ...........this is the TM on the exit route when clear
Post message ..........Alistair completed task 0

Add the above to all 4 trains and it wont matter in which order they arrive and leave. You need one train leaving the power station at the start in order for the first post message to be stored for an incoming train.

I'll try this tonight, thanks.

 

[Hot_Box_Detector]

Wouldn't you know it? ...

" post message" shows up red in the rules list and does not appear in driver in 2010 sp3...

 

[trev999]

" post message" shows up red in the rules list and does not appear in driver in 2010 sp3...

Post message has been superceded by Comm with Timetable <kuid2:131986:210055:1> but is written for TRS2004. probably needs to have the config file tweaked.

Edit: I see there is a TRS2006 one as well <kuid 131986:1030>

 

[stagecoach]

" post message" shows up red in the rules list and does not appear in driver in 2010 sp3...

It is working in 09 but needed some small alteration in the config. CMP should tell you what the error is.