signal clearing in timetable mode

[bprice]

This problem seems to only appear in Timetable Mode.

I find that on some routes, trains (operating as AI) will stack up because a signal doesn't clear. This seems to be in routes with more complex tracks and signaling. Sometimes re-routing will solve the problem but not always.

I have not used any complex timetable functions such as wait points. The routes are mostly double track.

I remember in some MSTS activities that sometimes a signal wouldn't clear until the player moved forward a bit. I wonder if that has something to do with the issue.

Sometimes I can manually clear a signal in the dispatcher (ctrl 9) screen, but this doesn't always work.

Is this a Timetable, OR, route bug? Any ideas?

Open Rails 2015-06-17 11-22-08.jpg

[Don6218]

I have a similar problem still with one activity, trains stacking up and not going anywhere even after clearing signals and rerouting with Ctrl#9. It is with the "Going Green" activity for the MLT NC route.

I wonder if I tried this "Timetable Mode" it may clear up the mess! The act was written for MSTS, not specifically for OR, which I use all the time.
Going Green Aldershot4.jpg

[markus1996]

I could imagine it has to do with the SignalNumClearAhead value of some of the signals in the sigcfg.dat file. For "normal" US signalling I have that parameter set to 3 normally.

Cheers, Markus

[peaches461999]

You should also be setting up passing paths when you create your timetable paths. I currently am developing an Orin Line timetable and currently have 6 mines running full operation over 24 hours and approx 60 plus trains on the southern portion that is shared by up and bnsf. If i have encountered a problem as you describe i have added passing paths in the OR path editor and this usually resolves the problem.

[bprice]

[QUOTE=markus1996;1873393]I could imagine it has to do with the SignalNumClearAhead value of some of the signals in the sigcfg.dat file. For "normal" US signalling I have that parameter set to 3 normally.

The sigcfg file has a variety of parameters. Some are 3 and some are 4. Are the 4's creating a problem because they are looking too far ahead?

[bprice]

You should also be setting up passing paths when you create your timetable paths. I currently am developing an Orin Line timetable and currently have 6 mines running full operation over 24 hours and approx 60 plus trains on the southern portion that is shared by up and bnsf. If i have encountered a problem as you describe i have added passing paths in the OR path editor and this usually resolves the problem.

The only single track in these paths is a bridge. The rest is double track. The issue is not occurring due to a standoff. The path is clear in both directions where the stack-up occurs.

[markus1996]

I could imagine it has to do with the SignalNumClearAhead value of some of the signals in the sigcfg.dat file. For "normal" US signalling I have that parameter set to 3 normally.

The sigcfg file has a variety of parameters. Some are 3 and some are 4. Are the 4's creating a problem because they are looking too far ahead?

I checked my above statement also with some routes on which the signalling worked fine without manually "tuning" it, and found I also had some SinalNumClearAhead values of 5.

So, you should be fine with 3 and 4, and the issue must be somewhere else.

What route route is it that you´re encountering these problems on?

Cheers, Markus

[bprice]

The one I was working with was the Marceline route in the FL here. But the issue has also appeared on the Cajon 4.2, and PRRER routes. The one thing that all of these routes have in common is rather complex track and signaling layouts. I think that this is only a timetable mode issue but I need to check some activities.

[Claude350]

I have problems with the MLT route Shuswap Sub. I'm having to clear signals and reroute train just to keep going. Some signals will clear as they should while other don't. I'm having to get permission by signals or permissive signals are giving a restrictive indication. At one point I passed an approach signal and the train went into emergency giving me the, "train out of control", message. The signals read 4 aheadahead. I'm running the route in Open Rails.

[markus1996]

@ bprice: sorry for the late reply, must have overlooked it.

@ bprice and Claude350: Could you please post your OpenRailsLogs?

Cheers, Markus

[Claude350]

Trying to figure out how to attach the log file.

[bprice]

I attempted to attach the log file. I get an error that it is too big. I may have to open a bug ticket.

Basil

[baldwin]

Zip the file first.