Page 1 of 1
| Use of 'BLOK' command 25/11/2009 at 01:58 #298 | |
Mattyq
259 posts |
I am currently playing Stafford and creating my own track closures at various times. I used the 'BLOK' train ID to prevent trains entering from Crewe on the closed line and this worked fine. At a later time I tried closing the Fast lines Polesworth to Tamworth using the 'BLOK' code but thiis did not stop trains entering on the Fast line at Nuneaton. I thought maybe the system would cross the train to the Slow at Polesworth but the train stayed on the Fast. I'm sure this has been discussed before. Am I doing something wrong or does the 'BLOK' command not work at Tamworth? Not fat ..... fluffy!! (G Iglesias) Log in to reply |
| Use of 'BLOK' command 25/11/2009 at 01:58 #4510 | |
|
Mattyq
259 posts |
I am currently playing Stafford and creating my own track closures at various times. I used the 'BLOK' train ID to prevent trains entering from Crewe on the closed line and this worked fine. At a later time I tried closing the Fast lines Polesworth to Tamworth using the 'BLOK' code but thiis did not stop trains entering on the Fast line at Nuneaton. I thought maybe the system would cross the train to the Slow at Polesworth but the train stayed on the Fast. I'm sure this has been discussed before. Am I doing something wrong or does the 'BLOK' command not work at Tamworth? Not fat ..... fluffy!! (G Iglesias) Log in to reply |
| Use of 'BLOK' command 25/11/2009 at 03:26 #4513 | |
AndyG
1842 posts |
Hi Matty, I suspect the use of 'BLOK' only works at the actual entry points. From Manual (Crewe Fringe): "It is possible to stop trains entering on either the Fast or Slow Lines by interposing ‘BLOK’ into the first signal’s (that shows an aspect) berth on the line that you don’t want trains to enter on. It is possible for trains to enter on the Fast Line instead of the Slow Lines or vice versa, so watch that train describer." Manual also quotes Lichfield as fringe with just 2 tracks, so not sure. Not sure whether collaring 1st signal works or not. I can only help one person a day. Today's not your day. Tomorrow doesn't look too good either. Log in to reply |
| Use of 'BLOK' command 25/11/2009 at 03:34 #4514 | |
|
UKTrainMan
1803 posts |
Firstly I am only taking a bit of a candle-lit stab in the dark here but I think the reason the 'BLOK' command will NOT work at the Nuneaton entry point is because Nuneaton is NOT a fringe. I don't even fully know what that means exactly however to put it simply you will not be able to stop trains entering from Nuneaton. Of course you're free to create your own timetable if you so wanted to and then not have any trains entering at a certain location until later on during the TT, then if you added 'BLOK' it would [sort of] work until the next scheduled train enters. Anyway, I think I'm right here, the fact that Nuneaton is NOT a Fringe is your problem. Hope this helps. Cheers, UKTrainMan. (P.S: Like I said, I'm taking a candle-lit stab in the dark here but who knows maybe I'm right. If I am wrong then please do let me know whilst at the same time helping Mattyq with his problem.) (P.P.S: Just wanted to clarify that I was looking at this thread and was typing out my reply before AndyG had posted his reply. I had problems in posting my reply in the first place and by the time I had eventually typed out and posted my reply, AndyG has beaten me  by reply quicker/first)
Any views and / or opinions expressed by myself are from me personally and do not represent those of any company I either work for or am a consultant for. Log in to reply |
| Use of 'BLOK' command 25/11/2009 at 10:37 #4521 | |
|
Forest Pines
525 posts |
AndyG said:The manual probably dates back to the first version of Stafford, which didn't include the Armitage Jn-Nuneaton section. Log in to reply |