signals by diamond crossings

[jytte]

Hello All,

I'm sure someone has thought of this before me, but thought I'd share it anyway, with any newbies that might have similar signal problems.

I found myself with 1 one-way track crossing 2 one-way trakcs, like so:

I needed to signal this crossing, but the "diamond crossing rule" that is available, was not ideal for this purpose, since it would
require that I put a total of 8 signals on this crossing (like below), when all I needed was 3. On top of which, I have a number of other signals
in that immediate area, for a bridge, converging tracks etc, so adding 8 more signals, that wasn't even needed, would only add
to the confusion

I came up with this solution instead:

Adding the 3 signals I needed, and 6 triggers, like so: (never mind the distances, it's just for this drawing)
I am using sets of two triggers, as it will allow me to set them precisely for each track where i want the trains to trigger a red light or revert.

Each individual signal and trigger has to be named, and I named them like so:
("name" being an identifier for this particular crossing area, since I will have more)

Then added these "trigger check" and "set signal" rules to my session-rules:

For the last two checks, it's important that the two "set signal" rules are at the same level (not further
indented), or else the 2nd rule will not take effect.

The trigger and "trigger check rule" needed for this are built-in content in TRS2006, but if you do not
have it already, you will need to download the "set signal rule" from DLS.

Hope this helps someone.

 

[tdstead]

There is a diamond crossing rule on DLS

you can set all the signals in one direction and all the ones in the other to work with each other.

A nice easy solution

Tom

 

[jytte]

I know the diamond crossing rule. Like I said, it requires 8 signals, which I didn't want.

 

[tdstead]

Hi again

It might want 8 but don't forget they all don't have to visiable.

Tom

 

[jytte]

That's a good point!

 

[ess1]

Hello All,

I'm sure someone has thought of this before me, but thought I'd share it anyway, with any newbies that might have similar signal problems.

I found myself with 1 one-way track crossing 2 one-way trakcs, like so:

I needed to signal this crossing, but the "diamond crossing rule" that is available, was not ideal for this purpose, since it would
require that I put a total of 8 signals on this crossing (like below), when all I needed was 3. On top of which, I have a number of other signals
in that immediate area, for a bridge, converging tracks etc, so adding 8 more signals, that wasn't even needed, would only add
to the confusion

I came up with this solution instead:

Adding the 3 signals I needed, and 6 triggers, like so: (never mind the distances, it's just for this drawing)
I am using sets of two triggers, as it will allow me to set them precisely for each track where i want the trains to trigger a red light or revert.

Each individual signal and trigger has to be named, and I named them like so:
("name" being an identifier for this particular crossing area, since I will have more)

Then added these "trigger check" and "set signal" rules to my session-rules:

For the last two checks, it's important that the two "set signal" rules are at the same level (not further
indented), or else the 2nd rule will not take effect.

The trigger and "trigger check rule" needed for this are built-in content in TRS2006, but if you do not
have it already, you will need to download the "set signal rule" from DLS.

Hope this helps someone.

Does the distance between triggers matter?

 

[ldowns]

Have you considered using the Trigger Multiple Signals rule instead?

--Lamont

 

[jytte]

Does the distance between triggers matter?

No. This is a "start and end" kind of setup, and the short trigger radius of the built-in trigger is actually helpful here.

 

[jytte]

Have you considered using the Trigger Multiple Signals rule instead?

--Lamont

I did, but the "trigger multiple" sets signals to "danger", then reverts them when train leaves the trigger radius, which is not what I want here.
A set of two triggers (set danger / set auto) allows me to set exactly where I want the signaling to start/end.
In some instances I need 3 or more triggers for one signal, because of diverging tracks etc, and this setup will allow me to do that.

 

[jytte]

Which leads me to another question.

I have yet to figure out how one might change the radius of a trigger?

But even if I could change the radius, I would have to have a trigger for each individual placing, since the radius I might need would vary from place to place. That's a lot of work. Using 2 seems simpler in that case. Also not everyone is capable of/comfortable with modifying assets.

 

[builder300544]

Hi,

how one might change the radius of a trigger?

In Surveyor click marker menu and then click advanced at the bottom.

You have three options.

a) Check trigger radius
b) Set Trigger Radius
c) Adjust Trigger Radius

Highlight c)

Left Click the trigger and hold the the button down. Now by moving the mouse you will see the trigger radius altering.

You can also click b) type in the Radius you want, then left click the trigger in surveyor.

This works for both triggers and markers.

I,m not a 100% sure but I think I read somewhere that a trigger radius of 0 will not work.

Regards, John

 

[jytte]

Duh, never saw that. Thanks a bunch John!

Now that will work beautifully for the places where I need only two points.

 

[ess1]

No. This is a "start and end" kind of setup, and the short trigger radius of the built-in trigger is actually helpful here.

Thanks for reply. Thought that this rule was just the job for singly-line working until I read that in AI the signal remained red. Ah well...

 

[jytte]

Thanks for reply. Thought that this rule was just the job for singly-line working until I read that in AI the signal remained red. Ah well...

What was that? Either I'm not understanding you right or you are talking about something I'm not aware of. I always drive this manually, so I haven't tried any of my signal setups in AI. What do you mean, you read "in AI the signal remains red" ??

 

[ess1]

Sorry, did not make myself clear. Checked in CMP (Asset Details-Description) where the creator informed prospective user that signals do not work under AI. They remain red.
Trust all clear now.

 

[jytte]

Ok, hmm.
this is the description on the "set signal rule"

These signal states should only be presented to user-driven trains. AI drivers cannot understand extended signal states and will stop at the signal. Signal AI will treat the set signal as Danger, so the preceeding signal will show Caution. Care should be taken to reset signals to automatic after a train passes it, as this will not be done automatically.

Maybe I'm not understanding this correctly, but I thought that as I am setting the first danger then auto via set sig rule, AI would ignore this, and "read" the original state, which would be green. I'm probably wrong then.
I always use "user-driven" trains, so I haven't delved much into this. Guess I have to try this out to see how things work or can be changed to work.

Anyone tried any of these rules with AI yet???