No call back at Furbanks

You are here: Home > Forum > Simulations > Released > Peterborough > No call back at Furbanks

Page 1 of 1

No call back at Furbanks 17/04/2023 at 16:42 #151189
Guts
Avatar
586 posts
I'm playing Peterborough chained to Kings Cross and Donny South.

Furbanks called to cross I said call back after next train when 1A44 was at P368, Abbots Ripton on the Up Fast.

It's passed clear of Furbanks with no call back

Screenshot and Saved before and after.

Post has attachments. Log in to view them.
Last edited: 17/04/2023 at 16:49 by Guts
Reason: 1A44 not 1A63

Log in to reply
No call back at Furbanks 17/04/2023 at 16:46 #151190
Guts
Avatar
586 posts
Call has arrived after the passage of 1P32 on the DS instead.


Post has attachments. Log in to view them.
Log in to reply
No call back at Furbanks 17/04/2023 at 20:47 #151208
clive
Avatar
2738 posts
The strike-in point for Furbanks on the Down Slow is the end of P317 overlap. Since 1P32 was past that when 1A44 cleared the crossing, the "another train coming" logic kicked in.
Log in to reply
The following user said thank you: Guts
No call back at Furbanks 17/04/2023 at 21:15 #151210
postal
Avatar
5190 posts
Is that logic applicable when considering the actions of the caller at the LC? They would presumably not know of the second train approaching and would ring back in any event leaving the signaller to give them another "ring back after the next train" response.
“In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe
Log in to reply
No call back at Furbanks 17/04/2023 at 22:42 #151218
clive
Avatar
2738 posts
postal in post 151210 said:
Is that logic applicable when considering the actions of the caller at the LC? They would presumably not know of the second train approaching and would ring back in any event leaving the signaller to give them another "ring back after the next train" response.
That's an interesting question.

The realism argument I would make is that the caller would see that the miniature lights are still red, so would wait a short while before phoning, at which point they'd be able to hear or see the second train coming, so would wait for it to pass.

The implementation reason is that MWLs are implemented as AHBs with a simpler barrier logic, so "second train coming" - even on a 4-track line - comes for free. Someone sensible isn't going to phone with the barriers still down. (Yes, I know not everyone is sensible, but I couldn't be bothered to simulate that.)

Log in to reply
The following users said thank you: postal, flabberdacks