[darwins]

Here is a diagram to help explain:
https://i.imgur.com/0wnRcYg.jpg

Can anyone solve my problem. I have been playing with timetables and I can't seem to get this one to work.
Train 1 arrives from Route 1 on Platform 1 and locomotive is detached.
Train 2 arrives from Route 2 on Platform 2 and locomotive is detached.

Loco 3 attaches to Train 1 and attaches Train 1 to Train 2 and leaves by route 3.
https://imgur.com/0w...gur.com/0wnRcYg

[Weter]

train 1
detach power, forms static, engine dispose as static
train 2
detach power, forms static, engine dispose as static
light loco
pickup static, pickup static, dispose as forms train 3

Merry Christmas!

[darwins]

Merry Christmas
Good news, the detach power command works for steam locos with tenders, it detaches both the loco and the tender (this is not clear from the OR manual).
Unfortunately it does not seem to solve my problem. This is what I have:
https://i.imgur.com/95IuCOV.jpg
The log file does not like two pickup statements for the same station. Also it does not know what Train 3 will be. - Dispose details formed train not found.
Train 1 loco detaches and forms LE - but train 1 disappears rather than becoming static.
Train 2 loco does not detach and whole train becomes static.
New loco seems goes to where train 1 should be picked up and stays there (active).

[Weter]

Quote

Good news, the detach power command works for steam locos with tenders

Indeed. That's why i've suggested that to You (I've guessed, You like steamers activities)

Quote

does not like two pickup statements for the same station

For this, every pickup in same station should form a new (i.e. another) train, to which single command set would be applied.
Other variant - give to ALL of route's sidings UNIQUE names and use every of them as a station.

Quote

New loco seems goes to where train 1 should be picked up and stays there (active).

Is it because there's no TRAIN#1 there already (as it've disappeared)?

[Weter]

Manual said:

Parameters for formed train :

/forms=<train>

Detached portion will form train as indicated.

/static

Detached portion will form a static consist.

Train#1's loco forms train#1133LE!
Shouldn't it actually be #1131LE?
#1133LE should pickup consist of Train#1, forming some intermediate (passing) train, which will be driven to Platform#2, where it will pickup Train#2's consist, forming Train#3

[Weter]

Train#2 now is being created at 11:35, but should depart from it's initial station at 10:35, for arriving to destination point at 11:36

Quote

Train 2 loco does not detach and whole train becomes static.

Not sure, why it's so for now... Let's try to fix known faults for Train#2 first and see..

Thanks for attaching screenshot of table - it's very easy to see, What Your project is looking like.

[roeter]

Here is what I would suggest.



Apart from correcting some typo's, the main changes I made are :

• Moved all $detach and $pickup commands to the #dispose line. It always works better that way for trains that terminate or start at that location.
  
• Split the move to collect the train portions in two separate moves. This is necessary as it is not possible to define two pickup-commands for the same location for one train.
  
• Removed all timings for Jn C for the collect moves, but instead used $wait commands to ensure these moves take place at the correct time, and not accidently before the required train has arrived.

By the way, you might need to add a $keepclear /rear=xxx or $terminal command for the arrival of Train 2 at Jc C to ensure that Train 3 will fully fit into the platform.

CSV file is added for your convenience (as .txt as the system does not allow to include something named .csv) :  ttpuzzle.txt (887bytes)
Number of downloads: 86

Regards,
Rob Roeterdink

[Weter]

Hello.

Quote

It always works better that way for trains that terminate or start at that location.

Shall I add this note to Timetable concept description? (I guess, yes)
It seems logic for me to perform maneuvers on station not strictly at certain time, but upon some circumstances, so I do agree: wait commands are more preferable.
And of course, trains should leave some space, enough for extra cars to be added within platform length.
What about train 1133A:
Is it principal, that $forms command is preceding $pickup /static? (iMO, loco picks up static consist, then forming a new train takes place)

Robert, You can attach any file, by zipping it (e.g. *.timetable_or)

[Laci1959]

Hello

Why does the train have to fit in the platform?
With us, the useful length of the track (from signal to signal) is often much larger than the platform. The latter is adapted to the special platform used by passengers. At least on the Hungarian tracks. It is also clear from the picture that it is several hundred meters from the end of the platform to the marker. It is not common, but it is placed on the tracks where passenger traffic takes place.
Sorry, but the translator sometimes confuses the term Platform used by the train and the elevated area used by passengers, which we call Peron.

Sincerely, Laci 1959

https://kephost.net/p/2022/52/7151_6e0924777350.png

[Laci1959]

Weter, on 27 December 2022 - 06:49 AM, said:

Hello.

To facilitate passengers boarding. Otherwise, they shall take their seats before train 1 depart from platform 1 and wait untill maneuver of getting it to platform 2, coupling to train 2, brake tests, documents completing and permission to depart for joint train 3 will happen.
Yes, picture indicates, marker of platform 2 area is shorter, than two coupled trains, though.

Hi.

Thanks.
I understand that, but that's not what I meant.
I was thinking of some limitation that is true for all trains. This is true even if the train does not carry passengers or is only a freight train.
I still remember the Puskin Express, which consisted of 20 Soviet sleeping cars, and two MÁV cars were added to this in Záhony. Not all stations fit in the area designated by the Platform.