Page 1 of 1
| Fictional replace 37 and ETHEL with 37/4 on 1Y01 17/07/2024 at 07:41 #157868 | |
mjkerr
195 posts |
I have attempted to create a (personal) timetable for 1989, from the 1984 / 1986 timetable, Old layout This uses a Cl 37/4 instead of Cl 37 and ETHEL 5Y01 arrives into P2 However for some reason it refuses to fully enter As a result the shunt with 0Y01 cannot take place, so I concentrated solely on 5Y01 I even added the Stopping Position Near end exact, but this does not appear in the original I have tested all the trains from Westerton, even swapping them into P2, no issues Ironically, 1Y01 is now shorter, but the movement is simply taking the Light Engine from P7 to P2, joining 5Y01, then returning back to P7 I have compared as much as I can but am no further forward trying to work out where the issue is Please advise  Post has attachments. Log in to view them. DELETED Log in to reply |
| Fictional replace 37 and ETHEL with 37/4 on 1Y01 17/07/2024 at 07:47 #157869 | |
|
sunocske
121 posts |
Try setting FX instead of NX, as Near and Far end are viewed from the direction of travel of the train. NX means the train will stop as soon as it's behind the signal in rear (which you can observe in your screenshot).
Log in to reply |
| Fictional replace 37 and ETHEL with 37/4 on 1Y01 17/07/2024 at 08:30 #157870 | |
|
mjkerr
195 posts |
Yes, my mistake, I would normally use that term in Carlisle Excellent, 5Y01 now runs fully into P2 The question remains now, why does the default position work until I revise the 37 + ETHEL into 37/4 It looks like the loco is at the wrong end? Another change I thought about was to amend 0Y01 Eastfield - Mossend to Cowlairs instead Use a Cl 47 instead on 1Y01 and have it detach once arrived at Eastfield DPL 5Y01 would then have a Cl 47 at the southern end and a Cl 37/4 at the northern end 1Y01 would then arrive with a Cl 47 at the southern end only, 5Y01 is then a simple move from P2 to P7 By 1988 / 1989 were Cl 37/4 in use? When did the sleeper swap to Edinburgh? DELETED Last edited: 17/07/2024 at 08:40 by mjkerr Reason: None given Log in to reply |
| Fictional replace 37 and ETHEL with 37/4 on 1Y01 17/07/2024 at 10:57 #157872 | |
|
bill_gensheet
1408 posts |
The sleeper changed a lot around mid 1980's, and one of the earlier versions of the timetable had the locos as you say, detach at Eastfield. Corrected after further research. There were vandal problems when waiting in loops around Glasgow, so various plans were hatched to keep it out of harms way until time to run to Mossend just in front of the Inverness portion for joining. 1983 (still VB/dual heat) through to Carlisle to meet Stranraer portion - also VB/DH 1984 May (now Mk3 + ETHEL, sleeper portion on Inverness train) - wait Coatbridge - bad plan 1984 June - wait Cowlairs curve - bad plan 1984 (July?) - Detach Dumbarton and through low level, Sunnyside and join Carstairs - tolerable but needed shunting at Dumbarton ! 1984 - To Stirling (as the sim TT) only formally in WTT from October Northbound was Ok anyway as the vandals were back in bed by 0300 ! 37/4 from 1985/6 June 1988 still via Stirling, with a 37/4 though May 1989 FW sleeper now a stand-alone train, went via Central LL, Rutherglen West curve and Central HL (some dates was reversed either via Shields or Cathcart circle due to Motorial vans) 18 March 1991 - Sleeper now to Edinburgh. (Sources mainly PSUL - https://www.branchline.uk/PSULintro.php and http://www.thebashingyears.co.uk/index.html ) re 0Y01/5Y01 etc When I did it in 1986, it was a 37/4 both ends arriving at Queen St., and the sleepers were in the rear heading north. What reports there are have the same 37/4 from Mossend - as it had got there via Stirling once no longer ETHEL. Bill Log in to reply |
| Fictional replace 37 and ETHEL with 37/4 on 1Y01 17/07/2024 at 12:55 #157873 | |
|
mjkerr
195 posts |
bill_gensheet in post 157872 said:0Y01/5Y01 etc Sadly I was never normally able to get to GLQ early or late enough to see it However I did manage to see it once northbound due to excessive late running I do remember it having a Cl 37/4 at each end, around 1987 I suspect this was to keep ETH throughout at GLQ (just in case the shunt went pear shaped) As the base timetable is 1986 it is this operation I am trying to recreate I do remember asking someone about the ETHEL around the same time, and two had been kept as spares for charter use (from memory two Eastfield Cl 37/0 and one Class 20 which had RETB / portable RETB) As an aside, I forgot that the passenger timetable from 1989 swapped from Cl 37/4 to Cl 156 (and the mad three car setup over the summer) I have also noted the Inverness - Bristol service (reversal) is not present This later swapped into the XX:X3 (09:33, 13:33, 18:03) Glasgow services, and simplified it even further! DELETED Last edited: 17/07/2024 at 13:01 by mjkerr Reason: None given Log in to reply |
| Fictional replace 37 and ETHEL with 37/4 on 1Y01 17/07/2024 at 13:00 #157874 | |
|
mjkerr
195 posts |
bill_gensheet in post 157872 said:What reports there are have the same 37/4 from Mossend - as it had got there via Stirling once no longer ETHEL That would make sense This would remove the LE movement from Eastfield to Mossend The rule associated could then be amended to the LE movement from Stirling to Mossend (depart 10 minutes after arrival or something like that) DELETED Log in to reply |
| Fictional replace 37 and ETHEL with 37/4 on 1Y01 19/07/2024 at 05:07 #157885 | |
rfw
177 posts |
sunocske in post 157869 said:Try setting FX instead of NX, as Near and Far end are viewed from the direction of travel of the train. NX means the train will stop as soon as it's behind the signal in rear (which you can observe in your screenshot).Here's a guide I put together a last year for stopping positions. Positions are relevant to the platforms and not signals. NX and FX mean the end of the train stops exactly at the near or far end, as with N or F you lose a couple of meters which doesn't matter unless platform length is very tight (which I count as less than 5m difference) in which case you want be using the exact positions in order to avoid the other end of the train dropping a track circuit you don't intend. In a terminus, FX is effectively drawing right up to the buffers. Mike, your train (5Y01) is 78m in a 160m platform and if the joining element (0Y01-1) is less than 77m, you can get away with just Far and not Far Exact. Else as this looks like a shunt move in a platform you could have 5Y01 stop NX with an offset of 1m longer than the length of 0Y01-1 and put F or FX on the stop positions of 0Y01-1. This latter method would have the train closer to the signal so there is less waiting around when the train moves off (and as it is a shunt move you don't need to worry about Pax walking a long way), but don't use this latter one if 0T72 needs to platform share PL2 with something else longer than 5Y01+0Y01-1 as you can't timetable it in for 0T72 to move further down the platform. I'll do a guide diagram at some point soon for stopping positions to include offsets and for reliable joins at through and terminus platforms, as the method is slightly different depending on where train 2 comes from.  Post has attachments. Log in to view them. The train now standing on platform 2, should be on the rails Log in to reply |
| Fictional replace 37 and ETHEL with 37/4 on 1Y01 19/07/2024 at 21:20 #157890 | |
|
mjkerr
195 posts |
rfw in post 157885 said:Mike, your train (5Y01) is 78m in a 160m platform and if the joining element (0Y01-1) is less than 77m, you can get away with just Far and not Far Exact. Else as this looks like a shunt move in a platform you could have 5Y01 stop NX with an offset of 1m longer than the length of 0Y01-1 and put F or FX on the stop positions of 0Y01-1. Sadly I am not Mike, mjkerr 5Y01 is a Class 47 and three Mark 1 coaches arriving into P2 In the original Timetable there are no instructions, the train arrives and draws to the normal position A Cl 37 + ETHEL, 0Y01, then take the three Mark 1 coaches to P7 When I amended 1Y01 and 0Y01 from a Cl 37 + ETHEL to just a Cl 37/4 5Y01 does not enter P2 I am more intrigued as to why, but using FX resolves the issue for just now DELETED Log in to reply |