Page 1 of 1
| Marylebone IECC - Signal 132 (Beaconsfield) 16/03/2014 at 19:38 #57153 | |
Llanelli Lad
2 posts |
Signal 132, north of Beaconsfield seems to me to be operating in an idiosyncratic (not to say unsafe!) manner. I have run the Marylebone Combined 18_12_12v6.0(0400) and v7.0(0400) timetables in 2013 and 2015 modes respectively and have found that signal 132 clears to green ~30 seconds after a train fully vacates the track section immediately before signal 132 and then changes to the expected amber once signal 130 goes to red. This has resulted in a closely following train 'amalgamating' with one stopped in Beaconsfield and the occupied track section immediately before signal 130 indicating only the identity of the following train. When the stopped train departs Beaconsfield the two trains 'de-amalgamate' with the front train having no identity. Am I missing something? Log in to reply |
| Marylebone IECC - Signal 132 (Beaconsfield) 24/03/2014 at 14:50 #57670 | |
|
MarkC
1089 posts |
Hi Further to this Issue thats has already been started I have a screen shot here of train 1I50 stopped in Beaconsfield a train 1H63 is right behind BUT has a green proceed aspect, i had thought there was an issue before as train reporting codes around Beaconsfield have changed to a different train usually the train in front become the train in rear Have attached A screen shot and a save game Post has attachments. Log in to view them. Last edited: 24/03/2014 at 14:51 by MarkC Log in to reply |