[Coolhand101]

darwins, on 06 February 2020 - 10:03 PM, said:

I would be tempted to think the other way.

Ignore if a signal has CLEAR_1 or CLEAR_2

Look for a caution aspect instead

That method is better, thanks!

darwins, on 06 February 2020 - 10:03 PM, said:

Just working on an eng file and realised there is an even more simple TCS - London Transport trip cock system. All that happens is that you get a full emergency brake application if you pass a STOP signal.

ATM, I believe the TCS will apply the emergency brakes, if you pass any stop signal. I haven't tried steam to confirm this.

Also on today's UK railway. TPWS is similar to the LT trip system. So again, the train brakes will apply if a stop signal is past at danger, which the TCS does!

On the subject of AWS, Temporary speed restriction zones. These have AWS for the temporary warning speed board. As in MSTS, this warning restriction board in OR, is placed at a maximum of 2400 meters from the start of the actual restriction speed zone, unless a black track node is under this distance, the restriction warning board will start from there. Could the AWS script detect the restriction warning boards?

Csantucci, on 07 February 2020 - 01:29 AM, said:

OK,
an updated demo pack (rev. 4 )is available here http://www.elvastowe...post__p__255510 , and OR NewYear MG Rev 52.4 can be downloaded from the usual link.

Hi Carlo

Will this work on my version?

Thanks

[Csantucci]

Hi Coolhand,
here are the two updated simulation files for you. Pls. backup the preceding couple, that anyhow worked.
 Simulations.zip (1.26MB)
Number of downloads: 368

[Coolhand101]

Csantucci, on 07 February 2020 - 02:13 AM, said:

Hi Coolhand,
here are the two updated simulation files for you. Pls. backup the preceding couple, that anyhow worked.
Simulations.zip

Thank you!

[Coolhand101]

I can confirm so far, the commercial routes with Clear_1 green signals now work 100%. The consist information HUD also shows the cab aspect as 'Clear_2'.

Thanks

[Coolhand101]

With these commercial routes, they use a unique approach control method. In OR, these are define as "Restricted". So even if the signal is green visually with a route indicator, OR will see these signals as "Restricting" and the AWS will give a warning.

This only applies if these signals use this Approach Control method with the "RED" control option. With the 'Yellow' option, the signal is displaying a single yellow with route indicator and the AWS will correctly give a warning. This should also apply to flashing yellows for high speed crossovers.

I don't believe a workaround can be found, due to the unique approach controls scripts. It's a minor error that I can live with, plus everything else so far, works correctly on these routes.

Thanks

[darwins]

I would be happy with what Coolhand has.

I am seeing the same problems as before on NWE.

Initially works fine with semaphore distants leaving Blackpool North.


Then for the semaphore fixed distant protecting Poulton speed restriction I get a horn, but no sunflower.

Nothing at all for the colour light signals on the way to Preston.

Then the speed limit warning at Preston gives me a horn and a sunflower together.

No response to subsequent colour light signals - the sunflower remains and there are no bings.

Will try another route later.

[Coolhand101]

darwins, on 07 February 2020 - 07:01 AM, said:

I would be happy with what Coolhand has.

I am seeing the same problems as before on NWE.

Initially works fine with semaphore distants leaving Blackpool North.


Then for the semaphore fixed distant protecting Poulton speed restriction I get a horn, but no sunflower.

Nothing at all for the colour light signals on the way to Preston.

Then the speed limit warning at Preston gives me a horn and a sunflower together.

No response to subsequent colour light signals - the sunflower remains and there are no bings.

Will try another route later.

I have NWE but let me first try MEP+. I have the cravens DMU setup for AWS and will use the "Cravens to Ely" activity. I shall report back.

Thanks

[Coolhand101]

No Problems with the AWS in that activity. I shall try the NWE activity next!

I meant to ask before. Does the AWS still recognize 'Normal' shunt signals as before ?

Thanks

[Csantucci]

darwins, on 07 February 2020 - 07:01 AM, said:

I would be happy with what Coolhand has.

I am seeing the same problems as before on NWE.

Initially works fine with semaphore distants leaving Blackpool North.


Then for the semaphore fixed distant protecting Poulton speed restriction I get a horn, but no sunflower.

Nothing at all for the colour light signals on the way to Preston.

Then the speed limit warning at Preston gives me a horn and a sunflower together.

No response to subsequent colour light signals - the sunflower remains and there are no bings.

Will try another route later.

Darwin, are you using OR NewYear MG 52.4, which is the latest version?

[darwins]

Sorry no, it is 52.2 I was using. Sorry thought it was the latest. Will go find 52.4

****

Things are much better on 52.4!!
I have correct behaviour on that route for (most) semaphore, two aspect colour light, multi aspect colour light and speed restriction warnings.
Still the problem with the semaphore fixed distant before the junction at Poulton though - it gives an alert sound, but not a sunflower.
Now off to try other trains and routes.