TimeOut issue
 

TimeOut issue

Begonnen von kiv@vftronic.no, 14. August 2026, 12:30:03

Vorheriges Thema - Nächstes Thema

kiv@vftronic.no


Hello Windigipet friends,

I use safety contacts and timeouts in my journeys. This works very well, except when the train is stopped on the defined timeout block (see image Timeout1).

When this happens, and I restart the train manually using the throttle, it runs forward to the destination block. However, but the throttle is never switched off by the software, and the journey never disappears from the "Tour Event Inspector" (see image Timeout2).

If the train stops earlier, when the timeout block is not active, and I restart it manually using the throttle (see image Timeout3), everything works very well and as expected.

Does anyone have any tips on what might be wrong with my setup?
Project file enclosed, timeout in journey 28-27

Kind regards,
Kjell Ivar
Rgs
Kjell Ivar
  • Win-Digipet-Version:
    2025 Premium Editon
  • Anlagenkonfiguration:
    Marklin, CS3+/ESU, HSI-88-USB
  • Rechnerkonfiguration:
    Win10

Konrad Schwarzjirg

Hi!
it seems that your route has the wrong contact or that the contact doesn't work correctly
Mfx+ und Schöne Grüße aus Wien
Konrad
------------------------------------------------------
www.wdp-stammtisch.at
www.youtube.com/@KS-MOBA
  • Win-Digipet-Version:
    WDP 2025.x Beta
  • Anlagenkonfiguration:
    Märklin K-Gleis ca 800m, MM, MFX+, DCC, Märklin Signale 763xx, 764xx, Märklin Oberleitung, CS3+, RMK: LoDI S88, Booster 60175, Decoder: M83, M84, ESU Lokprogrammer, LUX Radreinigungsanlage
  • Rechnerkonfiguration:
    Win11 Pro, Intel Core i5 7400 @ 3,00Ghz 8GB Ram, 1x 28

kiv@vftronic.no

Hello
Konrad

Thanks a lot for your quick replay for this case appreciate that
Enclosed image showing my setup, where is my mistake?

rgs
Kjell Ivar
Rgs
Kjell Ivar
  • Win-Digipet-Version:
    2025 Premium Editon
  • Anlagenkonfiguration:
    Marklin, CS3+/ESU, HSI-88-USB
  • Rechnerkonfiguration:
    Win10

Konrad Schwarzjirg

can you share your project here?
so i can see
Mfx+ und Schöne Grüße aus Wien
Konrad
------------------------------------------------------
www.wdp-stammtisch.at
www.youtube.com/@KS-MOBA
  • Win-Digipet-Version:
    WDP 2025.x Beta
  • Anlagenkonfiguration:
    Märklin K-Gleis ca 800m, MM, MFX+, DCC, Märklin Signale 763xx, 764xx, Märklin Oberleitung, CS3+, RMK: LoDI S88, Booster 60175, Decoder: M83, M84, ESU Lokprogrammer, LUX Radreinigungsanlage
  • Rechnerkonfiguration:
    Win11 Pro, Intel Core i5 7400 @ 3,00Ghz 8GB Ram, 1x 28

kiv@vftronic.no

already shared in my first page
Rgs
Kjell Ivar
  • Win-Digipet-Version:
    2025 Premium Editon
  • Anlagenkonfiguration:
    Marklin, CS3+/ESU, HSI-88-USB
  • Rechnerkonfiguration:
    Win10

Konrad Schwarzjirg

#5
Hi.

1st the name of your route is wrong 028->026 is correct but that is not the probelm



2nd -> my idea --> your security contact 31 will be proofed 8 seconds after you start your route. I can imagine that after 8 seconds the train has passed it already and so it is not possible to be proofed
Mfx+ und Schöne Grüße aus Wien
Konrad
------------------------------------------------------
www.wdp-stammtisch.at
www.youtube.com/@KS-MOBA
  • Win-Digipet-Version:
    WDP 2025.x Beta
  • Anlagenkonfiguration:
    Märklin K-Gleis ca 800m, MM, MFX+, DCC, Märklin Signale 763xx, 764xx, Märklin Oberleitung, CS3+, RMK: LoDI S88, Booster 60175, Decoder: M83, M84, ESU Lokprogrammer, LUX Radreinigungsanlage
  • Rechnerkonfiguration:
    Win11 Pro, Intel Core i5 7400 @ 3,00Ghz 8GB Ram, 1x 28

kiv@vftronic.no

Hello
Konrad

My goal is to stop the yellow bus train as quickly as possible if it travels in the wrong direction due to a wrongly set turnout.

During fine-tuning of the timer, I discovered that if the train stops at Block 31 (7.5 seconds), a strange situation occurs. When the train stops at Block 31 and I then restart it using the hand throttle, it never stops running — it becomes a "wildcat".

If the timeout is set for Block 28 (7 seconds), restarting the train with the hand throttle works correctly.

Setting the timeout to 8.5 seconds will secure this journey, but I am struggling to understand why stopping at Block 31 does not work and why this dangerous situation occurs. I would also like to understand what might be wrong in my setup.

If you send me an email address, I can send you a video showing the reason starting this job.

Kind regards,
Kjell Ivar
Rgs
Kjell Ivar
  • Win-Digipet-Version:
    2025 Premium Editon
  • Anlagenkonfiguration:
    Marklin, CS3+/ESU, HSI-88-USB
  • Rechnerkonfiguration:
    Win10