ETCS doesn't let me pass "stop signal" when it's already green light

[N3sW➀➁]

I have strange problem when I on for example ed250 pendolino with ETCS on: Ahead there is a "Stop" signal and ETCS informs me about this, and I fully stop on the "Stop" singal. Then dispatcher gives me green light, but ETCS still thinks that it's "Stop" signal. And no matter which button I press, it won't give me pass, even if I restart the ETCS. And currently my solution is to disable ETCS, and it kinda sucks. So please somebody can explain how to fix it, like maybe I missing out something? Thanks.

[lewnemejski]

26 minutes ago, N3sW➀➁ said:

I have strange problem when I on for example ed250 pendolino with ETCS on: Ahead there is a "Stop" signal and ETCS informs me about this, and I fully stop on the "Stop" singal. Then dispatcher gives me green light, but ETCS still thinks that it's "Stop" signal. And no matter which button I press, it won't give me pass, even if I restart the ETCS. And currently my solution is to disable ETCS, and it kinda sucks. So please somebody can explain how to fix it, like maybe I missing out something? Thanks.

I assume you were driving under L1 level. When you get signal allowing proceeding further, you can go up to 40 km/h to get update from balise. Therefore ETCS will allow you continuing ride. All information about how to ride under ETCS you will find in ETCS tutorials (SP mode, tutorials scenery) and guide: https://tutorials.simrail.eu/etcs/EN/ .

Edited yesterday at 04:34 PM by lewnemejski

[Quacking Duck]

I briefly elaborate on what was said by the previous reply.

In ETCS level 1, your train only receives new information about your movement authority upon passing over balises, which are typically located at signals. When your train reads a balise at a yellow signal, it is told that your movement authority ends at the position of the next signal, which at that moment is red. If the red signal then stops being red, your train does not immediately know this. Your train can only find out upon next reading a balise. This creates a problem: if the next balise ahead of you is the one at the signal which was red, you would never be allowed to arrive at that balise because your movement authority ends there. Sometimes, "infill balises" are built[1] at locations between signals to mitigate this problem, but cannot eliminate it entirely: the problem would still occur if a signal stops being red only after you have already passed the final infill balise as you approach that signal.

The solution to this problem in ETCS level 1 is that your movement authority has a "release speed": You are allowed to pass your end of authority (the signal which was red at the moment the movement authority was given to you) at a low speed, typically 40km/h in SimRail, for a short distance. This enables you to arrive at, and read, the balise located at the signal where your movement authority ends. If the signal there has become something other than red, that balise will give you a new movement authority. If that signal is actually still red, you will be stopped by ETCS; release speeds are typically selected such that you are brought to a stop before anything too dangerous results.

This system sometimes means that ETCS requires you to decelerate nearly to a stop for a signal which you know to be green, which can cause considerable delay and frustration, especially when following another train. This is a major reason for continuous-update systems[2] such as ETCS level 2.

[1] I am not actually sure whether these exist in SimRail.

[2] A different solution is to use induction loops ("Euroloops") in ETCS level 1. I do not talk about these here because I am quite confident that they do not exist in SimRail.