Countdown time:
Forced cancellation takes place at the earliest at the start of green. This means that a request is held even if the self-counting time is 0s, for example, until the green start. The exception to this is the special case of the compulsory request time of the check out message point = INAC.
PT priority list:
If a priority list is defined without equal positions, the following decision criteria become ineffective, as the decision can already be made unambiguously. On the other hand, further criteria must become effective in the case of equal rankings.
|
Display |
Identifier |
Values |
Description |
|
TctDn |
Countdown time |
|
With the initial request at the first message point vs | plus starts a request time counter [twts] related to the traffic stream as described. The following message points are recalibrated with TCAL. Thus, the request time counter [twts] represents the current travel time since the initial request on the recorded route. Now a logoff can be lost e.g., by faulty acquisition. For these cases vs | plus provides the parameter "countdown time". With this, a train is deregistered (train-by-train forced deletion) when the time counter [twts] reaches the value countdown time. It should be noted that vs | plus holds a request until either a correct check-out or a forced deletion occurs. |
|
|
|
|
|
|
|
|
0 .. 3276 |
If the traffic stream waiting time reaches the countdown time, the foremost train is deleted. The request remains until the countdown time has elapsed. Several green repetitions are possible. |
|
|
|
once green |
Forced deletion after the first green window, which is in the range of the expected arrival second. |
|
PrioList |
PT priority list |
|
Ranking order according to which competing PT are to be considered (rank 1 = high priority, rank 50 = low priority). The parameterization is done by assigning ranks. Equal positions of traffic streams (traffic streams have the same rank) are allowed. |
|
|
|
|
|
|
|
|
1 .. 50 |
Rank |