[देव]

Can anyone please Explain how the wait and follow commands are applied in the timetable mode?


According to the Docs: "Defines that a train is to wait for the referenced train to allow this train to proceed first. The referenced train can be routed in the same or the opposite direction as this train itself. A search is done for the first track section which is common to both trains, starting at the location where the $wait is defined, or at the start of the path if defined in the #note row. If the start location is already common for both trains, then first a search is done for the first section which is not common to both trains, and the wait is applied to the next first common section beyond that."

I am confused about the Common Section where the wait is applied, For the wait to applied do we have to give a siding path for the train that have to wait? Or Open-Rails will automatically re-route the train to the siding path for waiting?
<admin comment:
Thanks a lot for understanding about carefully picking the branches for new threads!
The misplaced topic was moved and opened for further discussion.>

[Laci1959]

Hello.

The command looks like this:

13:03-13:05 $wait=7214

The two times in the cell separated by a hyphen are the arrival and departure times, followed by the $wait command separated by a space. The command consists of the word command ($wait) and the name of the train (in European practice, its number) to which the command applies, separated by an equal sign. After the equal sign, enter the name of the train to which the command applies. To the cell at the intersection of the column of the guided (selected) train and the row of the station where the train will meet. This can be overtaking or crossing.
Several trains can be set in one cell as follows:

13:03-13:05 $wait=7214 $wait=7221

https://kephost.net/p/MTE0NzUxMw.png

The picture shows it in an excel table, I used excel because it has a search function, which is useful in such cases, and because it clearly shows the column for the train and the row for the station name.

https://kephost.net/p/MTE0NzUxMg.png

Sincerely, Laci1959

Ps The ranking can also be solved in Activity, with a programmable waiting point, or by using the appropriate time data in the AI train schedules. Of course, it is a completely different technology.

[Weter]

Hello.
"Open-Rails will automatically re-route the train to the siding path for waiting" works with activities, when "automatic passing paths processing" option is activated.
With timetables - exact routes should be defined by paths, and program will look, where waiting is possible. So, yes: for the wait to be applied, we do have to give a siding path for the train that have to wait"

Here's a variant of manual's translation:

Quote

- $wait (pass train В).
Syntax: $wait=<target_train_name> /maxdelay=n /notstarted /atstart /owndelay=n
Makes train A wait for train B to pass. Train B may be traveling in the following direction or in the opposite direction.
In fact, the crossing/overtaking is performed before the nearest common track section for trains A and B: starting from the location for which the $wait command is specified; or from the beginning of train A's route, if the command is specified in the #note row.
When both trains depart from the same point, the overtake will be performed before the next common section of track following the first one, which was not shared by trains A and B.
In cases where the waiting position is close to the starting point of train B, and there is a risk that before train B starts, the common section may be reserved by train A, the latter can be made to wait using the /notstarted attribute; otherwise, train B must already exist for the wait to be valid.
The $wait command is ineffective for places where the train changes direction, since the common section will be in the next part of the route (after the turnaround); and the search is only performed for the active part of the route. In such a situation, the train should be specified as two separate trains: the first one is in motion up to the turnaround point, the second one - starting from this point. (this is the one that can be set)
Command parameter: target train name (В), - mandatory.
Attributes:
/maxdelay=n n-maximum delay time of train B (in minutes), within which train A is still waiting.The magnitude of train B's delay is compensated by train A's own delay time. For example, if maxdelay=5 (minutes), train B is 8 minutes late, but train A itself is 4 minutes late, the actual delay will be 4 minutes, and so the wait is still valid.The attribute is optional; the default value of 0 applies.
/notstarted perform wait even when the target train (В) has not yet started.
/atstart to wait strictly at the given location, not at the nearest non-common section of track.
For cases where the route of an oncoming train B ends at the same location where the route of train A begins, and there is no possibility of a crossing between that location and the current position of train B.
/owndelay=n n n-The minimum time train A is late (in minutes) beyond which waiting starts to be performed.
This is used to delay a late train so that it does not cause additional delays to other trains; particularly on single-track sections.
/trigger=HH:MM Experimental*: Waiting in effect only after the specified time.
/endtrigger=HH:MM Experimental*: Waiting in effect only until the specified time.
*Apply with caution! /maxdelay and /owndelay are preferred
- $follow (following the B train)

[Weter]

Quote

12.5.7.3. Wait Commands and Passing Paths

From the location where the ‘wait’ or ‘follow’ is defined, a search is made for the first common section for both trains, following on from a section where the paths are not common.

However, on single track routes with passing loops where ‘passing paths’ are defined for both trains, the main path of the trains will run over the same tracks in the passing loops and therefore no not-common sections will be found. As a result, the waiting point cannot find a location for the train to wait and therefore the procedure will not work.

If waiting points are used on single track lines, the trains must have their paths running over different tracks through the passing loop in order for the waiting points to work properly.

It is a matter of choice by the timetable creator to either pre-set passing locations using the wait commands, or let the system work out the passing locations using the passing paths.