In the menu journey editor> stop is set to "end of platform", but some time the Train stop just by entering the block (4 in setup). It is hard to understand, because by running several laps (5) and it stop perfect for every lap. Then suddenly it stop and beginning of platform. Seems to happen when a new train is started, but not 100% shure that is the reason.
Is there a log anywhere to read why the train is forced stop?
Or a tip what to check for this issue.
See image for actual setup.
Hi Kjell,
please make sure, that the stop-contact doesn't "blink" sometimes. You can dot that within the Logbook (option: record feedback events) or in the feedback configuration window (option: display feedback log.
regards from the city of berlin
Bernd
+++
hello
I found a feedback log in the menu , seems for me that all feedback's is set on/of several times. I don't find a way to save the log to a file, menu therefore image enclosed.
If I add a delay timer in <feedback menu> the train will run future into the block, by increasing to 5,5 sec it stop when all of the train enter the block (end of platform). But I don't believe at all that that this solution it a work around.
My feedback's are controlled by HSI-88_USB, Marklin train system.
Finlay it seems for me that this problem occur only at block (4) trains using blocks 1,2,3,5 run ok.
I found something that may cause this error, at block 1, one of block 4 was inserted, strange that it was not discovered by me earlier. I will correct and do a new test and let you know the result.
My finding do not solve this issue, it is something else. I believe now that there is something unstable with the system, it might work, but then it doesn't work again. For the moment I'm confused.
What always cure the problem is the feed-back delay-timer.
Hello Thommy,
it may also be that a detector is more sensitive due to mechanical causes, the thickness and length of the power cable, and/or ground pickup via another occupied detector nearby.
First, I would use a software-based response delay offered by WDP.
I always want the detector to switch on immediately, but not switch off again within half a second or a whole second, so you build in what I visualise as a 3-second or even longer afterglow period, which suppresses the flashing.
Well, interference is very difficult, but take a few ferrite clamps and place them near where there is a connection to the rails and/or FB module.
Sometimes a ferrite ring around a number of detector wires can help. It removes a lot.
A DCC snubber can also help with an Inline or T Line DCC bus.
Hello Bernd from Berlin
I never found the cause of this error, but it seems for me as a software issue.
Why this conclusion?
In the menu (Tour-automatic> (see image) I deleted the actual trouble tour that was inserted in line 1, and then just reinserted it by the menu <Select start/destination> into line 10 (see image), when done the tour run as expected and train stopped 100% correct at end of platform.