Hello !
This worked OK before (I think :) ), but not now after I re-installed everything and created New routes and tours:
When a Train runs Down a tour, it checks the Next route at the check-contact, and if the next route is free, it is activated and the Train does not slow Down at the brake-contact, but starts the New route. But now it slows Down to the braking speed anyway, before it accelerates again after the brake-contact. What am I doing wrong? This looks a bit akward... :) :)
Best regards,
Per.
PS: OFF-TOPIC: Can anybody tell me how to avoid getting CAPITAL letter as the first letter in many of the Words (look at this mail). I do NOT Write these :)
Hello Per,
maybe you didn't use random before and now you do? That would explain why it takes a while because it takes a random time until the next route is requested.
What you can do is to use the new follow-up routes. Unfortunatelly I don't have WDP round here right now. In the German editon the old ones are the "Folgefahrten" and the new ones the "Anschlussfahrten". When using the first ones the train might stop. But it never will when using the second ones if the next routes are free.
Off topic: What are you using for writing? A PC or a tablet? Tablets like to "correct" your writing....
Hello !
I use both random and not-random, both now and before..
When using Zugfahrten, the Next Fahrstrasse should be activated when reaching the check-contact in the previous Fahrstrasse. Check-contact is normally the same as the braking-contact. Earlier the Train went directly to the Next Fahrstrasse when reaching this check-contact without braking. Sometimes it braked a short time before accellerating again, but now it seems to always run through the entire braking-section before accellerating again.
Yes, I know about Folgefahrten and Anschlussfahrten, but this is not what I am talking about here :)
Off topic: This happens only (as far as I have seen) in the WDP forum. And it happens regardsless if I use my Laptop or my desktop PCs. I have no tablet..
Regards,
Per.
Hello Per,
sorry, mixed it up, I thought you were talking about the Zugfahrtenautomatik, but you're not. Are you using profiles?
Are you writing in English in other forums, too?
Hello Stefan.
That's OK. No, I am only in this forum. Yes, I am using profiles, but not all the Fahrstrassen I talk about, have profiles. It seems to be the same With or without profiles.
Best regards,
Per.
I've experienced very similar problem as I re-worked tours, routes, and automatic operation for WDP2015.
When the first route in tour-automatic was with profile, and the follow-up route had no profile, train jumped up immediately to the follow-up route skipping the speed, functions, macro of the first route. So train started with the speed of the second route, when reaching break contact of the first route it slowed down to the breaking speed, and ran on the breaking speed until nearest speed contact of second tour. Very annoying.
When I've added profiles to follow-up routes that problem disappeared. So far all routes I edited with profile 1, I didn't make tests with other profiles, i.e. followed routes with different profiles.
Hello !
I just checked some more....:
Stefan: Actually, I do have the same problem With Fahrstrassen and Folgefahrten/Anschlussfahrten. The Train slows Down to braking speed anyway, and runs on braking speed all through the braking-section, even if the Folgefahrt/Ansclussfahrt already has been activated. This was definitely not like this before.
Kuba: I still have the same problem, also With profiles on both routes. Train slows to braking speed and uses that speed all through the braking-section, even when the NeXT route has been activated.
I noticed that by putting the check-next-route contact further back, the problem sometimes disappear. But then I have to put it so far back, that it makes other problems. So I would really like to be able to use the brake-contact as check-contact. WDP should first see if the Next route is free (and then NOT start the braking) before starting the braking.
Best regards,
Per.
Hello again....
Any more suggestions? Anyone...?
:) :)
Best regards,
Per.
Hello Per,
happy new year!
What happens if you put all of your routes into a Zugfahrtenautomatik? With Anschlussfahrten. Does the train slow down, too?
Hello, Stefan !
Happy new year to you, too !
Yes, it is the same in Zugfahrtenautomatik.
I guess I am doing something wrong, but don't know what it is....
Regards,
Per.
Hello Per,
I need your project. Please use the backup option for the forum (which is new in 2015). And a description of the problem.
Hi.
Enclosed is the project. Hope you can find what I am doing wrong...
The problem is described earlier in this thread..: Train slows down to braking speed, and maintains that speed through the entire braking-section, even when the next route already has been activated (both in Anschlussfahrten, Folgefahrten and also inside Zugfahrten). Only when I put the Prufe-Kontakt very early, I can avoid the problem. But this often creates other problems, so I want to use the brake-contact as check-contact.
Regards,
Per.
Hello,
ZitatThe problem is described earlier in this thread..:
is clear, but in which tour and what routes we can reproduce that?
Hello.
OK. I am not home right now, but let me see...:
In Zugfahrten-Automatik "0 Fremvisning 00.ZFA" , lines 062-069. With Folgefahrten back to station SOLBAKKEN and also Anschlussfahrten line 71 and 72 continuing to line 73 and Folgefahrten to station Nesttun. All these slow down to braking speed before accelerating again even when all other tracks are free, no other trains moving etc.
In the long Zugfahrten in lines 134-212, the train slows down between Fahrtrassen inside each Zugfahrt.
I do not know what I am doing wrong, and I would really like to fix it. So I hope you can help me, I look forward to that.
All the best regards,
Per.
Hello again,
I can´t see it in Simumation. The speed is constant during the Zugfahrt.
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.
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.
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.
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...
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.
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
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
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.
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.