Csantucci, on 20 September 2015 - 07:23 AM, said:
Hi Serana,
some thoughts about your proposal, which surely touches a quite important point:
1) I wonder why explorer mode works in a more restrictive way than activity mode; one would expect the opposite or that they behave the same on this point;
2) What happens in reality (probably every railway system has its own rules) and how can this be emulated best without unnecessarily complicating things?
3) I would prefer linking such distance to route speed than to train speed; I think it could be a bit more prototypical;
4) As far as I am concerned, if an approach depending to train speed or route speed is chosen, I would prefer to go not only above 5000 meters, but also below 5000 meters; 5 Km can be too much for not too fast routes; I had already at least two cases where a train could not enter a route because there was another one almost 5000 meters behind, even if in reality the former would have entered the route.
some thoughts about your proposal, which surely touches a quite important point:
1) I wonder why explorer mode works in a more restrictive way than activity mode; one would expect the opposite or that they behave the same on this point;
2) What happens in reality (probably every railway system has its own rules) and how can this be emulated best without unnecessarily complicating things?
3) I would prefer linking such distance to route speed than to train speed; I think it could be a bit more prototypical;
4) As far as I am concerned, if an approach depending to train speed or route speed is chosen, I would prefer to go not only above 5000 meters, but also below 5000 meters; 5 Km can be too much for not too fast routes; I had already at least two cases where a train could not enter a route because there was another one almost 5000 meters behind, even if in reality the former would have entered the route.
Hi,
1) Don't know either. I think the SNCA value could have been used in explorer mode.
2) In France, in the modern signal box, the switch-man has a system called MISTRAL that allows him to command and control the interlocking, to monitor the trains and to protect the engineering work areas.
With the train monitoring functionality, he knows when the train is supposed to arrive, even if the train is delayed. He can set the route in advance or let the system set it automatically (with a plan he programmed the day before). The route is set several minutes before the arrival of the train.
For the simulator, I think both the SignalNumClearAhead and the distance are good solutions. Maybe the SNCA solution is a bit better because it uses data coming from the route itself. But if the value is wrong, too many or not enough signals will be opened.
3) I agree with you. When I talked about speed, I didn't precise if it was the current speed or the allowed speed. I was thinking about using the allowed speed.
4) The problem is that this minimum value depends on the type of route : fora tramway, the value will be low (maybe 500 metres) whereas, on main lines, this value should be at least 3000 metres even in low speed zones.
vince, on 21 September 2015 - 09:39 AM, said:
Hello Serana,
If you look at the photo of the Single Heads SNCA chart I posted and assume that I use a SignalNumClearAhead value.of 6.
Now also assume the signals are all spaced at about 1500 to 1600 meters ( about a 1 mile) apart.
This will give a train traveling at 230 Km/Hr about 8 Km to stop from first encountering the first restrictive signal (Clear2 Flashing Green) before encountering the Red signal.
Is this not enough distance to have the train to slow to a stop in time? Or, if not, longer distance signal spacing would be the way. Maybe?
If you look at the photo of the Single Heads SNCA chart I posted and assume that I use a SignalNumClearAhead value.of 6.
Now also assume the signals are all spaced at about 1500 to 1600 meters ( about a 1 mile) apart.
This will give a train traveling at 230 Km/Hr about 8 Km to stop from first encountering the first restrictive signal (Clear2 Flashing Green) before encountering the Red signal.
Is this not enough distance to have the train to slow to a stop in time? Or, if not, longer distance signal spacing would be the way. Maybe?
In France, on high speed lines, we use a system called TVM430. When the train has to stop at a signal box, there is a sequence of speed limitation : 320 kph (green) > 320 kph (green blinking = the next indication will be lower) > 300 kph (white diamond blinking = announcement) > 270 kph > 230 kph > 170 kph > 80 kph > 0 kph (red diamond = stop at the next marker). That means that the train has to stop on 7 block sections. On HSL East, the track sections are longer than those of the HSL North (1500 meters, 300 kph) due to the less important traffic. The track sections length is about 2500 meters. The train has to stop on 17,5 km (FYI, a TGV can stop on about 3,3 km from 300 kph in emergency braking :) ).
That means that, in Open Rails, the signal opening distance that has to be put in the code is at least 17,5 km for this high speed line. Of course, this is not adapted to other lines such as tramways.
The guy who modelled the TVM430 on MSTS has set a SignalNumClearAhead value of 15. That's too much. I would have set the value to 8 or 9.