Page 1 of 1
| Can't reverse trains out of the LUL area 08/08/2024 at 20:00 #158085 | |
RailwayFan8
7 posts |
I can't reverse trains out of the LUL area from Amersham to Great Missenden because the train thinks it's at a buffer stop. The specific move is reversing away from JW1 towards ME769. The train then gets trapped at Mantles Wood. Is this a bug?
Log in to reply |
| Can't reverse trains out of the LUL area 09/08/2024 at 04:44 #158087 | |
Giantray
347 posts |
Have you tried manually reversing the train? If the train has it in the timetable to reverse, it should reverse if it is and does, it's a bug, but if it is an un-planned move, manually reverse the train. <F2> right click train concerned, Hover mouse over "Signalling Options" highlight and click "Reverse Direction" Click 'yes' if it says "Train is in motion. Do you wish to stop and reverse this train". The train should now reverse. Professionalism mean nothing around a bunch of Amateur wannabees! Log in to reply |
| Can't reverse trains out of the LUL area 11/08/2024 at 16:08 #158139 | |
|
RailwayFan8
7 posts |
Yes thus is a bug when you try to manually reverse. It thinks it's at a buffer stop when there is none.
Log in to reply |
| Can't reverse trains out of the LUL area 12/08/2024 at 14:27 #158147 | |
|
clive
2789 posts |
bill_gensheet in post 158143 said:Actually, this is the default and is built into the loader, so the age of the sim doesn't matter. However, if an arm of pointwork doesn't have any routes in either direction coded, then there won't be any there, which can cause this situation. (I haven't looked at the data for Marylebone, so can't comment on the specific case.) Log in to reply |
| Can't reverse trains out of the LUL area 12/08/2024 at 21:57 #158159 | |
|
clive
2789 posts |
Okay, I've taken a quick look. My test train is stopping at the end of TJWBA where it meets TVG6. The latter is where the different layouts for LU simple versus LU full meet and both track circuits are coded for up traffic only. The fact that the train got to TJWBA tells me that the code for wrong-direction working was invoked. But clearly something went wrong at this point and I don't know what without a lot of digging that I don't have time for. Sorry. Log in to reply |
| Can't reverse trains out of the LUL area 13/08/2024 at 15:38 #158166 | |
GeoffM
6377 posts |
Lots of speculation but it would be far more useful to see the timetable @RailwayFan8.
SimSig Boss Log in to reply |
| Can't reverse trains out of the LUL area 13/08/2024 at 17:23 #158170 | |
Steamer
3986 posts |
GeoffM in post 158166 said:Lots of speculation but it would be far more useful to see the timetable @RailwayFan8.It's not a timetabled/'normal' move. A train authorised past JW51 wrong-line will hit the buffers at the end of TJWBA. Possibly related to it being the Full/Simple LUL transition point so only set up for the expected right-line moves? "Don't stress/ relax/ let life roll off your backs./ Except for death and paying taxes/ everything in life.../ is only for now." (Avenue Q) Last edited: 13/08/2024 at 20:40 by Steamer Reason: None given Log in to reply |
| Can't reverse trains out of the LUL area 13/08/2024 at 23:13 #158175 | |
|
GeoffM
6377 posts |
Steamer in post 158170 said:GeoffM in post 158166 said:As Clive said/implied, the code already generated the wrong direction moves. Nevertheless we don't routinely handle unsignalled moves anyway, because of the amount of background (non-signalling) things that have to happen alongside.Lots of speculation but it would be far more useful to see the timetable @RailwayFan8.It's not a timetabled/'normal' move. A train authorised past JW51 wrong-line will hit the buffers at the end of TJWBA. Possibly related to it being the Full/Simple LUL transition point so only set up for the expected right-line moves? SimSig Boss Log in to reply |
| Can't reverse trains out of the LUL area 15/08/2024 at 19:47 #158204 | |
|
metcontrol
227 posts |
Whether or not a "bug" exists, this is not a move "in real life" that would be considered without lots of other things taken into account. My first instinct is that the sim contains each and every piece of real-life data within, and this would add some considerations in the locking / programming for a signal prior to JW1 in the "up" direction - that being a "repeater" signal RJW1. A repeater ordinarily on LUL would simply be an early warning to an aspect of a running signal that has restricted sighting. RJW1 is such a signal, but is situated close to the LUL/NR Boundary and is not only the first LUL signal Chiltern drivers see, and is not just a repeater of the aspect of JW1, but it is further tied in with the last NR signal which is actually ME376. The nature of the signalling from Aylesbury down to Amersham is pretty much basic 2-aspect which replaced semaphores on an almost like-for-like basis in terms of track circuits and locking. I have witnessed an occasion (just 1 in 16 years of being a controller on the Met) where a Chiltern was reversed from north of Amersham back to Great Missenden, but it did take a very long time and did indeed leave some track circuits dropped as a result of sequential signalling (put simply, the signalling system must see tracks drop/pick up in sequence or else consider there to be a fault and fail). In summary, reversing a Chiltern north of Amersham from the position the OP suggests will not be straightforward (involving 2 separate rule books - NR and LUL) and would likely cause issues with signalling for subsequent trains. I would therefore suggest there is no actual "bug" in this instance as the process would be a very last resort. Log in to reply The following users said thank you: GeoffM, mldaureol, flabberdacks |
| Can't reverse trains out of the LUL area 16/08/2024 at 02:05 #158207 | |
|
mldaureol
14 posts |
I agree with Metcontrol above. This is a wrong direction move on a main line. It would require the filling out of various LUL forms. It would only be done in an emergency situation. Log in to reply |
| Can't reverse trains out of the LUL area 19/08/2024 at 19:13 #158233 | |
|
clive
2789 posts |
GeoffM in post 158175 said:I agree with Geoff that this specific instance isn't an important case. However, I've now tracked down the root cause, the fix is simple, and it's possible that it might affect other sims more significantly either now or in the future. So Mantis 41318 raised. Log in to reply The following users said thank you: bfcmik, Soton_Speed |