$detach, $pickup & $attach commands I can't learn to use
#11
Posted 22 September 2020 - 12:47 PM
#12
Posted 29 September 2020 - 03:25 AM
Thank you for your explain.
I'm trying again and again. Fixing the problem at specific location, moving up with the start time and get the problem at different locations. At least three days I can't to attach some loco at all.
roeter, on 22 September 2020 - 12:43 AM, said:
One is to reduce the length of the static train, and so increase the distance between the front of the train and the last signal.
The other is to reduce the speed of the approaching engine. This can be done by setting a much lower max. speed in the timetable. It can also be done be setting an approach control sequence for the last signal, keeping it at danger when the section beyond is occupied until the approaching engine has stopped. If a specific aspect is shown on occupied track, it is also possible to set a maximum speed for this specific aspect.
All my station lines has a back-facing signal heads on an exit signals at both directions. There signal heads are at RESTRICTING state when the block ahead is occupied with the 20 km/h speed limit. Also the attaching loco has a speed limit itself by setting maximum speed of 20 km/h at speed row.
I'm trying to understand what wrong again.
It must to be something else.
Now I have check .con files and .eng files and I suspect the "Velocity" line at the "Coupling" block in the .eng.
"CouplingHasRigidConnection ()
Velocity (0.01m/s) "
Is it possible that the attachment not happens because of this value is too small?
Regards
Oleg
#13
Posted 29 September 2020 - 09:16 AM
As for the approach to the siding - at 20 km/hour, and requiring two updates to be on the save side, the front of the train should at least be 60 meters from the protecting signal.
As for the velocity definition in the coupler - no idea if this could affect anything. This value is not used in the timetable logic as such, but what is done in the rolling stock logic I do not know. However, if this would be a problem I think it would always be so, in both prerun and in normal running. So it still would not explain the problem occuring during prerun only.
Regards,
Rob Roeterdink
#14
Posted 29 September 2020 - 03:18 PM
roeter, on 29 September 2020 - 09:16 AM, said:
It is not working with more longer distance from the signal (The "problematic" train is 2918)
https://i.ibb.co/X3cgdNd/image.png
Maybe I defined a commands at wrong way...
Train 2918 formed from another train - S-2918 that arrived at the location and has a $pickup/static command at station stop field and then - $forms=2018 command at #dispose field. Is that syntax wrong?
Regards
Oleg
#15
Posted 29 September 2020 - 04:24 PM
https://i.ibb.co/wcj3jCK/Run-Activity-2020-09-30-01-44-44-54.png
It looks like the static consist just doesn't exist for the loco :wallbash:
Regards
Oleg
#16
Posted 29 September 2020 - 11:41 PM
Regards,
Rob Roeterdink
#17
Posted 30 September 2020 - 02:12 AM
OR crashes at first minute of loading...
Regards
Oleg
Attached File(s)
-
OpenRailsLog.txt (14.31K)
Number of downloads: 3
#18
Posted 30 September 2020 - 04:23 AM
$forms=2918$pickup /static
note the white space before /static
or another example
$forms=2918$detach /nonpower /static
so in the #dispose $forms comes first, followed by the qualifiers
rick
#20
Posted 30 September 2020 - 02:57 PM
Edit
Something wrong with the platform. I played with the platform length (was made it shorter) and the previous train (it does the same operations of pickup and forms and that was works before) now does not connected.
Regards
Oleg