[rickloader]

I would like now to tackle what i call "stuck trains". As a non programmer i can`t deal with the issue directly in terms of OR code, but only as stuck trains appear to a user. The same as a beginner would experience As always any contributions are welcome!
Definition
A "stuck train" has tested correctly, but subsequently can not progress in the timetable run, and commands fail. There are no errors shown in deadlock information (F5HUD) or in the ORlog. However secondary errors may show from failure to carry out operations earlier in the train path. eg "no units to detach" because the train previously never picked up any units.
A train may become stuck following a timetable revision. The stuck state will be consistent until next revision, but may revert to normal on a subsequent timetable revision, even if the changes are remote from the stuck train.
Causes and Solutions
1) Over complex paths with attach/detach/pickup/transfer commands (ADPT). OR can handle many reversal (far more than MSTS) but the ADPT command seems to be lost after several path reversals.

The solution is to split the path after the reversals and form a new train. In the #dispose row. "$forms=newtrain /$pickup /static". A "newtrain" tt column is started. In general a maximum of 1 ADPT in the train tt column in station fields.
If this still gives trouble, then split the train at the station with the ADPT in the #dispose.
Transfers are particularly demanding, and it may be possible to substitute a $detach, folowed by a $pickup.
At terminal stations this won`t be possible because any locomotive will be blocked in against the buffers. So a $transfer will be needed. In this case putting the $transfer in the #station field seems more successful. Yes, contrary to the usual advice of ADPT in the #dispose

2) Path conflicts
Generally path conflicts show in the path section of the F5 HUD - but not always, especially with a lot of sub paths (ie reversals).Usually the signals and timetable can handle 2 trains trying to access the same track, but sometimes when a train is badly delayed, or when a 3rd train traverses the shared tracks, then a train can "lose" the next move and will not restart .
Controlling the projection of paths ahead is the key here. Commands like $hold $noclaim $wait can help, and a new command $activate looks promising , though I haven`t yet got it working. These path control commands appear to work best on the 1st subpath, and not reliably on subsequent reversals. Another reason to split trains

3) Reserved Switches
A variation of stuck trains is when switches are not released after the train passes, but remain set against following trains.
Signals protecting the switches will be correctly red. If signals are forced to clear, the real reason ; RSW, reserved switch, is shown in the F5 hud. Also shown is the train number reserving the switch. This train may no longer exist having terminated or run off the system. Running the timetable earlier may help find the train from the alt F9 window.
However, the train reserving the switch may be blameless, and it is then a matter of finding and examining other trains that have paths sharing the route at the same time.

Summary
Stuck trains can be resolved by controlling path projection , and simplifying paths by splitting trains. Although splitting trains make a more complex timetable for the compiler, it presents data to OR in smaller , simpler chunks.
In general, OR signalling and timetable mode is very robust, but the fact that hundreds of trains are interacting means that problems can sometimes occur. I hope this thread has given some guidance. In future it is hoped that devs can provide additional diagnostic info for timetables. Chris Jakeman`s upcoming dispatcher viewer is a big step forwards.
Rick

[Laci1959]

A lot of people use Timetable mode with us, and making Timetable is becoming more and more popular. The Alföld_7.2 track is also under continuous development in order to make better use of Timetable's knowledge. This is especially true for the development of sigsrc, and for signaling stations.
It would be a shame to lose.

[Weter]

Yes. The great thing there-is marking sidings, that are no platform-tracks actually, with platform-markers, giving them names as "*<StationName>*-freight *<TrackNumber>*" during route-builing; so freight trains cAn have stops not only by platform-tracks; and this way, they can take part in TT full-funtionally.

As far as we have no opprtunity yet, to use sidings for trains to stop there, this is a compromiss measure to deal with freight traffic at TT mode.

The "minus" is, that signals behave very strange way at Alfold 7.2 now.

[m61]

Open Rails #7 =The presentation= Route 351 Poznań-Szczecin
The official premiere of route 351 this weekend on the website:
https://or.trainsim.pl/aktualnosci-3/