Trigger Multiple Signals rule

Ian_Coleman

New member
I'm having problems in TRS2004 with the Trigger Multiple Signal Rule.

I've searched the forums, but have found nothing regarding this rule.

Can anyone please give me any tips regarding the successful use of this rule?

I've been trying to make it work successfully, but I am having no luck with it.

One question I have is - Does the signal have to be within the radius of the signal? I've tried it both within and ouside the radius, but mnothing seems to work properly!

Ian:'(
 
As the creator of the rule in question I should know how to use it but it has been a while so please bear with me.

The Trigger Multiple Signals rule is designed to be used inconjunction with 1 or more signals and 1 or more triggers. The idea is that the selected signals will be set to DANGER when a train is in any of the selected triggers. If ALL of the triggers do not have a train in range then the signals are set back to AUTOMATIC control.

You can have more than 1 instance of the rule in the session, but a signal can only be controlled by 1 instance of the rule.

To set it up, the signals and triggers that you want to use will need to be named. You will need to configure the rule with the signals that you want to control and the triggers that you want to use.

When you run the session, a train entering the trigger radius of any of the triggers should cause the selected signals to change to DANGER. When all trains are outside the trigger radius of the triggers the signals should return back to automatic control.

Please note that you should only use signals capable of displaying a DANGER state.

If you need any further info then I do lurk around here or send me an email through the forum.

Regards

Maggs
 
Sorry for butting in but would this work on dimond crossings, as the crossing rule is some what an hit and miss afair.
 
I recently finished laying out the signals for AI traffic on the main lines. I used dozens of "Trigger Multiple Signal Rule".

By the way . . . THANK YOU MAGGS for this Rule !! (***** five stars)

I found this signal tutorial to be extremely helpful.

http://www.trains.0catch.com/Signalling Crossing Tracks and Double Track Junctions.pdf

My route is split in 3 pieces. I started signaling the main route which has trains coming and going through 5 double track Portals on the route. 4 of the 5 Portals are sending 50% of their roster of trains to one portal. So a 6 track exchange area where all the AI trains sort themselves out to their destination tracks gets very congested. A train comes through every few minutes. It took a few weeks to get all the AI trains to behave. Now it runs for hours without any AI on a "stand-still" or any of them backing up for miles. AIs are impatient . . . but will behave if the signals are set up properly.

In working on signaling here are some snags that I ran into that needed to be solved.

1. Setting up train priority : 2 methods.
Method 1 - Use TMS Rule
In the interest more prototypical train movement, you will need to set lots of triggers.

The Trigger spacing is dependent on the SHORTEST train to be driven on the route under AI operation. In my case, that is a commuter train with 6 cars and a loco. I used the 6 car length as my trigger spacing.

Remember that while if ANY of the triggers attached to a signal(s) is under a train, the signal is RED. BUT, if the Triggers are too far apart, there will be short instances when the signal will turn green. The AI train will USUALLY stop about a car length before the red signal . . . but not always. The instance of green signal might be enough to pass the signal and cause a collision. Its happened to me.

Example: A user driven train is coming out of an industry onto the Mainline. The Mainline speed is 60mph. You want any approaching AI train to give you enough advance notice of his approach. So my signal is controlled by many Triggers on the main line. The actual number depends of the shortest train on the main line. So, if I don't have a yellow or green on my signal, there is an approaching train on the main line close enough to hold me back. The signal will change to proceed after the train has passed.

Method 2 : not so reliable
AI train can HOLD a junction for his use from a very long distance away. You can just use an "invisible junction" in his path to limit WHERE he is allowed to HOLD his NEXT junction. In the example above, the AI's NEXT junction is the one you need to get on the main line.

It is "not so reliable" because, if you already started to proceed on to the main line with a heavy train, but the signal turns red just as you past it, can you stop your train? If you place your signal too far from the junction, An AI train can seize the junction before you are over it. Potential for collision.

2. You may run into a situation where you want ONE signal to be activated more than one TMS Rule . . . which can't be done.

A work-around solution is to place a dwarf signal in the same place as a standard "04" signal. The signals are supposed to be a certain minimum distance apart. I found out that the second signal works with the TMS rule, AND the AI will not proceed until BOTH signals are clear.


It took a lot of "trial and error" and "experiments" to get the AIs behaving.

Hope this helps someone.
 
Ian,

The only time I changed the "trigger radius" is for junctions. I set my radius much smaller that the default (usually 0.05) for a more realistic range.

I usually leave the radius for a "Trigger" at default. The reason is that the Triggers are NOT directional. Anything approaching the trigger from either direction will activate it. The default radius is about 100 feet (30m). I prefer to just add more triggers at the default radius for the TMS rule.

If you have a situation where a very short consist (like just loco consist) is going to be run, you might consider increasing trigger radius to a much larger size to reduce the number of triggers needed for the TMS rule.

For triggering a "wait for trigger" rule, the default radius should be fine.

I rarely change the radius for a Trigger.
 
edion2

Thank you for your extremely helpful postings.
What would you describe as being a reasonable distance for a trigger to be placed from the signal(s) that it controls?

Ian
 
Back
Top