Route: Train slows down even when next tour IS FREE. Why ?

[Per Olsen]

Hi.

OK, so what is wrong, then..? 
I never understood how simulation works in Zugfahrten (my german is not too good, sorry), so I have not tried this, sorry.  The trains slow down anyway, sorry..

Regards,
Per.

[Stefan Lersch]

Hello Per,

is it only at one place that it slows down or everywhere? In the first case I would check if the feedbacks from all of the route and the follow-up route fire correctly.

[Per Olsen]

Hi.

It is everywhere (I think, I did not check ALL routes one-by-one..).  All feedbacks are OK. 

What I think is strange, is that the next route really IS activated; all turnouts of the next route are shifted, and all tracks are marked yellow.  As a normal activated route.  But STILL, the train runs at slow braking-speed all through the braking-section.  It seems only way I can avoid this, is to put the check-contact earlier, before the brake-section.  But this is not always so good..

Regards,
Per.

[Jürgen Gräbner]

Hello again,

please translate it by google...

was müssen wir tun um das Problem in der Simulation zu sehen? Ich konnte es bisher nicht nachvollziehen...

[Stefan Lersch]

Hi,

Jürgen's answer (manually translated ):
What do we have to do to see the problem in the simulation? I couldn't reproduce it until now.

[Markus Herzog]

Hi Per,

in your example you use the as follow-on routes for example the routes:
ID 63 Ven01>Sol01
ID 64 Ven01>Sol02
ID 65 Ven01>Sol03

These routes do also include signals 215 and 216 at the left end of Solbaken and 243 and 244 at the right end (the right ones not in all routes).

You set the switching time for these signals to 5000 msec.... A train will never enter a route where the switching time of one of his solenoid devices is still running.

In your case: Your route will be switched at the check contact. The speed commands of the route will not get valid until all solenoid devices have been switched and the switching time is over.
So only solution for these switching times: put the check contact before the brake contact (driving time until brake should be larger than 5 seconds...)

Regards
Markus

[Markus Herzog]

Hi Per,

as addition to my last post. I saw some data stuff from old versions where you might have not used the rubber when deleting solenoid device symbols. I removed the scrap for you. Please replace your Gplan.dat with the attached one.
The explaination in the last posts remains the same.

Regards
Markus

[Per Olsen]

Hello Jurgen, Stefan and Markus !

Thank you all for your help...!

Jurgen and Stefan:  I do in fact read a bit German, but I am not an expert..  I may also write some, but this is more of a problem, sorry.  English is much better for me..
Translation (not Google !!):  Ich kann en bisschen Deutsch lesen und schreiben, aber ich bin kein Expert, dass ist warum ich besser English benutze. 

Markus:  (I continue in Englsih ):
I did in fact suspect that this could be a part of the problem.  But as the mentioned follow-on routes ID 63, 64 and 65 pass the signals 215 and 216 "from behind", I thought the entered delay-time did not have any effect.  I understand now that they do, so I will remove them again, and enter the delay-times in the tour-automatic again, like I had before.

I will go over the entire layout again, and remove again all the un-needed delays.  I did start to use these delays to avoid turnouts to change too late in long routes, where the train started to move before all turnouts had finished to switch.  But of course, like this case with signals 215 and 216, the same thing may be the problem in many of the other routes.

Yes, I saw that the problem went away by putting the check-contact earlier, but this often a problem, if the next route is activated TOO early.

OK for the GPLAN.DAT.  Yes, I know it is easy to forget to use the rubber.  I try to do my best...  Thank you, I will replace the file.

All the best regards to all of you !
Per.

[Adrian L]

Thanks for this post Per.  I was also having this problem and now I understand at least one reason why it occurs.  Later this week, I will work through the layout design and make the recommended adjustments.

Like Per, I have never been able to get the simulation working properly. I must admit to not trying the function in 2015, but in every other version of WDP (going back many years) it would not work for me.

Thanks also to Markus, Stefan and Jürgen for the thoughtful insights.