Seite 1 von 1

Behaviour of itinerary requests after splitting a train

Verfasst: Sonntag 27. Juli 2025, 21:37
von 1993matias
Hello,

I am trying to make an itinerary request for a train just before it splits such that the rear, reversing half of the train can get an itinerary to leave the platform. Even though the contact is set up correctly (by confirming the request is present before the train reaches the shunting point), the request disappears after the train splits.

This differs from the behaviour I had expected where the request follows the internal train identifier.

Why don't I make use of the itinerary request built into the shunting point? Or place the contact after the train splits? Simply because there is no space available.
Bild
Each timing point requests its own pair of itineraries - or none due to the diverging nature of the trains leaving from that TP. Thus there is no space to combine the timing points.

I am open for suggestions as on how to solve this problem, but I would prefer not having to rebuild half the station.
Thanks!

Re: Behaviour of itinerary requests after splitting a train

Verfasst: Samstag 2. August 2025, 07:29
von Seb144
Hi Mathias,

this is hard to understand. Can you upload the layout (or just the relevant part of it) so it's possible to have a look at it? So far I dont't even get what you're trying to do.

Best,

Sebastian

Re: Behaviour of itinerary requests after splitting a train

Verfasst: Samstag 2. August 2025, 18:32
von 1993matias
I will upload it tomorrow and share the link. But I have found a workaround instead.

What happens is that a train passes a contact that requests an itinerary. After the contact there is a shunting point where the train is split in two parts. All of a sudden the itinerary request is completely gone