Dispatcher Track Requests not needed?

[Jasonic]

At Lazy lc you get the Lazy AI dispatcher asking if track 3 is clear for a train but they don’t ask the same for track 7(behind the box), on track 7 they just request line lock and you notice the arrow flashing white, why can’t they do that for 3 as well? would save loads of messages, as well as the random is Line clear messages from DG asking if track 4 is clear even with route locked in from their direction, more requests not needed.

[Bescot]

Yes it does seem strange for them to phone in when the direction is already set correctly.

They only really need to ask if line is clear, if you need to reverse the direction. Maybe the devs are aware of local instructions for the routings and that's what happens there in real life?

 

The only other reason I can think of is for when left hand running of two track block sections is needed to be taken back to using the normal direction of travel. if they didn't ask you for line clear the AI would continue to send stuff wrong line and you wouldn't be able to stop them. So you *need* to get a phone call before they send each train so you can respond with "no you idiot - send it on line 1!"

Edited December 19, 2022 by Bescot

[SurvivorSean]

The other thing I'm noticing is what they call track #a may be track #b on your board.  I forget where this was happening for me but I found it difficult to know what they wanted.

Thanks

Sean

[GoldLettuce8526]

When trains start breaking down or mistakes happen you'll appreciate the communication before trains start getting fed down the ABS lines between the interlockings, probably more so when its AI dispatchers who aren't keeping up on the conversations between drivers and dispatchers.

[BigVern]

17 hours ago, SurvivorSean said:

The other thing I'm noticing is what they call track #a may be track #b on your board.  I forget where this was happening for me but I found it difficult to know what they wanted.

Thanks

Sean

I must admit to getting a bit confused between the Line (route?) number and the actual track number which I believe is prefixed by "Tor".

[SurvivorSean]

There is a roman numberal I or II on the left side of the platform and then the actual track number visible on the right side of a platform specification.  The roman numberal on the train list is hard to see.

What I was refering to was a signal box next to you in AI requesting a track and showing up on another.  I think the track numbers change but I could be wrong.

Thanks

Sean

[ArtU4]

39 minut temu, BigVern napisał(a):

I must admit to getting a bit confused between the Line (route?) number and the actual track number which I believe is prefixed by "Tor".

Line number (Linia Kolejowa # - LK#) is a number for a railway line in Poland (similar to route/highway number) common for all dispatcher posts countrywide. So, we have ie:

LK1 - Warszawa Centralna - Katowice

LK160 - Zawiercie ZW - Dabrowa Górnicza DZA T3

LK4 - CMK Grodzisk Mazowiecki - Zawiercie

 

When running an express train from Katowice to Warszawa you will be dispatched through LK1 then LK4 at Zawiercie and again LK1 at Grodzisk Mazowiecki.

 

OpenRailwayMap has this numbers entered and additional information you can get here (Railmap - mapa kolejowa (bazakolejowa.pl) - unfortunately only in polish).

 

Track numbers (tor#) are different because these are set for a station or post. Łazy ŁC is a good example - tracks belonging to different lines (LK) have unique track numbers (tor#) set for Łazy post. For a reason track (tor#) number is common for neighboring posts(stations) if we have multiple track line. This makes it easier to communicate between dispatchers.

[SurvivorSean]

Yeah and that is where things get confusing when the box next door says a certain track number.  I'm going to look at that new map as well.  

Thanks

Sean