Andis Signal Issues

[Auscgu]

Andis we are seeing a number of issues with the signals which may be linked with the TS transition to DirectX 11.

The distant signal does not appear to be responding to the codes set in the signal ahead.

The speed set in the global and properties table don't appear to be working.
We used the global speed to eliminate spads with the scenario predictors.
Using a reverse predictor now produces spads.

I had the signal working by coding the signal arms ahead to control the distance signals.
The code dose not seem to transfer now.

Distant Signal code for the semaphore signals has not worked for me since I started with the signals.
Would love to sort this out if possible.

Can you check the signal coding in TS with the current changes?

[AndiS]

I do not have TSC installed, so I cannot check anything.

But I can rule out that it has anything to do with DirectX.

But then again, some of the things you say sound like it never worked.

I do not remember codes set in the signal ahead that should influence a stand-alone distant. This sounds a bit mysterious to me.

[Auscgu]

AndiS this is a recurring problem getting the route to or doll information to forward.

The signal is at Crewe Basford Hall Jct and Crewe Sorting Siding South.
The signal ahead is a Splitting home distant signal with call on arm 2
The following signal has a Home Distant arm for route 1, a single arm for route 2 with a smaller arm under for route 3.

The signal has 7 links and link 1 is used to capture the info for route 1 & 2 ahead.
Link 3 is for a right diverging route and used Link 3. The rest are inner links.

The wrapper is the closing signal for the signal above with 4 routes and 6 inner links.

The signal ahead has 2 routes and two inner links.
Link 1 is for route 1 and link 2 for route 2.

I have tried to get the signal configured and use free roam to test.
Can you see any issues with the signals?

[Auscgu]

The signal and script for the Splitting Signals

LNW_Eq_HDm_HDmCo_4T.pdf

(173.26 KiB) Downloaded 26 times

The signals are using MB Anthony Brailsford assets.

LNW_Eq_HDm_HDmCo_4T.pdf

(173.26 KiB) Downloaded 26 times

The script for the signal

[Auscgu]

The signal Ahead

LNW_Eq_HDm_HbHb_7T.pdf

(161.2 KiB) Downloaded 22 times

MB_HDHH.pdf

(80.19 KiB) Downloaded 24 times

Can you see and reason why this may not work?

[AndiS]

My only idea at the moment this: You cannot have a > in the route character. It only works in the configuration string.

At least the back page of the manual says so.

(Personally, I do not remember ever using > in a route character in the properties table, but I do not remember a lot.)

[Auscgu]

Andis you seem miffed and if I have put you offside I do Apologize as it was never my intent.

Your right about the code some time you can see the wood for the tree.
I put the code into the signal ahead and tested with no change.

Next I buried link 1 and setup with link 2 as the primary link for receiving the info from the signal ahead.
Signal 2 now clears and signal 1 will not clear.

Next was buried link 1 & 2 and set link 4 as the primary link.
Now only arm 3 clears for all routes.

Rebuilt the first diamond to eliminate any track issues set the signal ahead with arm numbers 1 & 2.
Set the signal in advance to link 2 and the same result.

How would you signal this situation?
Can we run through the basic of you signal set up to see if we can find a reason for the issue.

[Auscgu]

Can you run through how you intended the signals to work regarding the Arm, Doll & Route function.

The signals have an arm and are activated by the arm.bin file
The naming for this varies with the creator link to the animation files.

I have seen two methods for the arm to arm animation.
MB has one arm name with all the clearing in the one file.
JY have an individual arm number with the clearing for each arm number.

LNW_Eq_HDm_HbHb_7T.pdf

(161.2 KiB) Downloaded 21 times

Looking at the GTable HDHH for the signal in advance.
Link one has Arm 1 with a distant signal for the box ahead.
Arm two is a home signal and arm 3 is a siding signal.

gArmTable[1][ARM_HOME][SEM_CHILD_NAME]
[1] is the route code?
The [ARM_HOME] is the arm status in your signal script
[SEM_CHILD_NAME] is the animation activation in your script

The first arm is named "one home arm" with "Clear01 and "Stop01"

Looking at the arm file ARM_5f0_Hm1.bin
This is a combined file with all the animations links for this arm.

Looking at all the arms for this signal they have the same method.

[Auscgu]

Back to your signal script and Arm routes

In a single arm signal you have one arm but could have multiple route.
The Arm would be "one home arm" and points ARM_5f0_Hm1.bin
The arm can clear far all arm numbers and routes.

Looking at the signal in advance LNW_Eq_HDm_HbHb_7T

We have route 1 with the start arm and the distant signal for the signal in advance.
The start arm is for Crewe Sorting Siding box and the Distant is the second arm for Basford Hall Jct.

Route 2 is the slow line and has a start arm for Crewe Sorting Siding box but no distant arm.

Route 3 is a siding arm for access in to the North Stafford Sidings

All the arm have one signal arm path file irrespective of the arm number or box order.

Is this your intent or could be a problem?

[AndiS]

First of all, let me assure you that I am not miffed at all. I am just confused, quite often. It takes quite some energy to find out what you are talking about.

In this case, I have not idea what the second picture with the wrapper would to in the setup. I believe it is for the opposite direction.

I found two signal diagrams on the net, from SRS, but very tiny as always.

https://www.s-r-s.org.uk/html/lmsr/M756.gif
shows Basford Hall Junction with semaphores. In the middle at the right-hand side, we see two signals that match your description.

So Crewe Basford Hall Jct Home is shown in your third picture. It needs no configuration. You can have $~15 if you like. That is a separate topic.
You do need the - for the inner links, of course. But you do not need any route character for link 1 or 2.

Crewe Sorting Siding South Starter is shown in your first image.
Unfortunately https://www.s-r-s.org.uk/html/lmsr/M923.gif shows CLS era, after rationalisation.
At any rate, there are some sidings on the top left in the diagram. Or rather another route. The crossover seems to be labelled x or so with a note "electrically released by ...".
I am sure that the smaller, lower stop arm on the right-hand doll, reads to this route.

In your image, there is no third route away from the signal. There is just the Up Fast and Up Slow to Basford Hall Junction.

So you need extra trackwork to give this arm a purpose. Then you do not need to configure anything at that signal either.

I believe that the distant at Crewe Sorting Siding South Starter will not clear when the route at Crewe Basford Hall Jct Home is set to cross ever to the left.


Regarding the naming of arms, do as you like. There is exactly one thing that is important: Avoiding mistakes.
Therefore, any scheme that sounds logically to you is a good scheme.

Since you use so many different signal parts, you will not alter everything to one scheme. You will most likely be glad enough to have different groups in your collection where you know which naming scheme is used in which group.