20323: Two (or three) different train merge during the route. If all three trains are entered separately on the part of the route where they are coupled together conflicts occur. How can FBS know that all trains are coupling together?

There are three trains (Train 1111, Train 2222 and Train 3333) are coupled together and depart from station A to station B. Upon arrival at station B, these trains uncouple, with Train 1111 continuing its journey to station C, Train 2222 traveling to station D and Train 3333 traveling to station E. In this scenario, how should the train routes be created?

The principles of implementing train coupling and sharing in FBS are the following:

  • There is only one train in the section A-B from an operational view, so there is also only one train A-B in FBS. (In opposition to that operational view, the travellers may regard it as three trains in that section running at the same time.)
  • The one operational train A-B contains three train parts A-B. Each train part will continue from B to C/D/E as a separated train.
  • The program will link the trough-running of the three train parts A-B to the final destinations C/D/E by the same train part number. So, the train part A-B which goes through to C must have the same train part number in the section A-B as well as in the section B-C and so on.
  • Usually, the operational train runs through from B to the final destination with the first train part (the train part which is in front of the combined train at B). So, if the first (in-front) train part leaves B to E, the operational train also runs A-B-E, from A to B with three, from B to E with only one train part. This is optional; there is no need to have a through operational train; there could be three new operational trains starting at B.

More Information on this topic and some detailed examples you can find in the document:

Train coupling & sharing in FBS - Examples

Last update on 17.06.2024 by iRFP Administrator.

Go back