1991 timetable

Is it expected that 6K91 terminates with no engine at Sudforth Lane sidings? It's a Tuesday.

I'll take a look at that tonight. Edits will be made where necessary & hopefully an updated TT will be made in a few days.
I must admit I swas getting a bit concerned about the fact that not many users had reported issues & wondered if users had found this timetable too overwhelming to play single manned. But glad some of you have stuck with it.

58050 in post 118026 said:

I'll take a look at that tonight. Edits will be made where necessary & hopefully an updated TT will be made in a few days.
I must admit I swas getting a bit concerned about the fact that not many users had reported issues & wondered if users had found this timetable too overwhelming to play single manned. But glad some of you have stuck with it.

Managed the timetable twice now on my own, if it gets hectic, I cheat and slow down until sort I myself out, needless to say I don't enable the LCs

Glyn

6M18 0850 Lindsey - Glazebrook is booked Up Goole - Up Goods - Up Fast at Wakefield Kirkgate, but the dvr calls up from WK1232 Sig on the Up Goole querying the route and requesting a platform.

6M18 0850 Lindsey - Glazebrook is booked Up Goole - Up Goods - Up Fast at Wakefield Kirkgate, but the dvr calls up from WK1232 Sig on the Up Goole querying the route and requesting a platform.

From a run through of the Mon timetable, the following was noted:

1. 6M49MSX0420 has no rule to prevent it entering on Mondays.

2. The rule controlling the entry of 7K880420 prevents it entering R/T.

3. Seed 6k86sudfthlnup divides to form 6K951414 using DCR activity. This leaves 6K95 with no power (although 6K95 TT spec'd as Cl56 + 36 wgns) and no loco appears to provide power.

4. 6K761647's rule regulating its entry references the wrong Ferrybridge location so train does not run.

5. Does 7K860915 run MX as its rule only refers to 6K860749 not 6K86MO0749?

6. Rules for 6K952357 refer only to the FO version of 7K952218.

7. 6K790514 is not able to select the MO version of 7K790710.

8. 7K802014 needs a rule to prevent it entering too early - 6K801828 empties that form?

Hope that isn't too much of a handful! Looking forward to being able to chain in Leeds & York.

geswedey in post 118030 said:

58050 in post 118026 said:

I'll take a look at that tonight. Edits will be made where necessary & hopefully an updated TT will be made in a few days.
I must admit I swas getting a bit concerned about the fact that not many users had reported issues & wondered if users had found this timetable too overwhelming to play single manned. But glad some of you have stuck with it.

Managed the timetable twice now on my own, if it gets hectic, I cheat and slow down until sort I myself out, needless to say I don't enable the LCs

Glyn

Well done personally speaking I've only ever run through this timetable whilstKev & I were testing it & that involved 2 or 3 of us. I've never actually gone through the whole timetable on my own, but similarly I wouldn't have the level crossings active as it gets unmanageable at times.

From a run through of the Mon timetable, the following was noted:

1. 6M49MSX0420 has no rule to prevent it entering on Mondays.

2. The rule controlling the entry of 7K880420 prevents it entering R/T.

3. Seed 6k86sudfthlnup divides to form 6K951414 using DCR activity. This leaves 6K95 with no power (although 6K95 TT spec'd as Cl56 + 36 wgns) and no loco appears to provide power.

4. 6K761647's rule regulating its entry references the wrong Ferrybridge location so train does not run.

5. Does 7K860915 run MX as its rule only refers to 6K860749 not 6K86MO0749?

6. Rules for 6K952357 refer only to the FO version of 7K952218.

7. 6K790514 is not able to select the MO version of 7K790710.

8. 7K802014 needs a rule to prevent it entering too early - 6K801828 empties that form?

Hope that isn't too much of a handful! Looking forward to being able to chain in Leeds & York.

Another little one Pascal. 6E31 1113 Weaste - Port Clarence booked through line at Wakefield Kirkgate but is also booked relief there. When signalled along the Up & Dn Through from WK1211 Sig he queries the route. Maybe needs to be booked a platform like 6M18.

Had another little issue with 2G60 Track Recording Unit as well. When returning from Monk Bretton to Calder Bridge he queried the route at Oakenshaw South Jn stating not booked via Calder Bridge Jn.

Does anyone have a saved snapshot around 0400 (not a Monday, any other day will be fine)? Or else I will have to run the timetable from the start to that point so I can see what sdg is free at Milford WS.

Another little one Pascal. 6E31 1113 Weaste - Port Clarence booked through line at Wakefield Kirkgate but is also booked relief there. When signalled along the Up & Dn Through from WK1211 Sig he queries the route. Maybe needs to be booked a platform like 6M18.

Had another little issue with 2G60 Track Recording Unit as well. When returning from Monk Bretton to Calder Bridge he queried the route at Oakenshaw South Jn stating not booked via Calder Bridge Jn.

Muzer in post 117622 said:

Is it expected that 6K91 terminates with no engine at Sudforth Lane sidings? It's a Tuesday.

Looking at the MGR coal plan 6K910442 TO MGR Ferrybridge- - Sudforth Lane arr.04.54 shows detach empties & LD to Knottingley TMD. The loco departs Sudforth Lane at 05.10 & arrives at Knottingley TMD at 05.14.
Another loco comes off Knottingley TMD as 0K91 05.56 TWThO to Sudforth Lane & attaches to either that set of empties or another set there to form 6K91 06.26 MGR Sudforth Lane - York Yard North. I'd be very surprised if Kev & I missed something as we both extensively tested this timetable throughout each day of the week well before the advent of the alpha & beta tester teams. What you need to realise with MGR workings is that any set at either Sudforth Lane or Milford WS could be used for any MGR working as they are all 36 MGR wagon sets apart from the circuits working to Welbeck Disposal which are restricted to 32 MGR wagon sets due to coal slag weighing heavier than the coal sent to the power stations. So when allocating a set to its next working it doesn't necessarily follow that the specific set you are quierying has a next working.

58050 in post 117624 said:

Muzer in post 117622 said:

Is it expected that 6K91 terminates with no engine at Sudforth Lane sidings? It's a Tuesday.

Looking at the MGR coal plan 6K910442 TO MGR Ferrybridge- - Sudforth Lane arr.04.54 shows detach empties & LD to Knottingley TMD. The loco departs Sudforth Lane at 05.10 & arrives at Knottingley TMD at 05.14.
Another loco comes off Knottingley TMD as 0K91 05.56 TWThO to Sudforth Lane & attaches to either that set of empties or another set there to form 6K91 06.26 MGR Sudforth Lane - York Yard North. I'd be very surprised if Kev & I missed something as we both extensively tested this timetable throughout each day of the week well before the advent of the alpha & beta tester teams. What you need to realise with MGR workings is that any set at either Sudforth Lane or Milford WS could be used for any MGR working as they are all 36 MGR wagon sets apart from the circuits working to Welbeck Disposal which are restricted to 32 MGR wagon sets due to coal slag weighing heavier than the coal sent to the power stations. So when allocating a set to its next working it doesn't necessarily follow that the specific set you are quierying has a next working.

Pascal - I'm up to 19:40 on a Wednesday and 6K86 has entered at Shaftholme Junction for the Sudforth Sidings. The trouble is, all three sidings are full and none of them are due to depart until after 6K86 is booked to arrive, change engines, and then depart at 20:59.

One of the sidings is occupied by empties 6K91, which arrived earlier in the day and have been sat there for many hours. I have empties which will become 6K82 and 6K86 in the other two sidings. With reference to the 6K91 which you addressed in the quoted post, should the 6K91 empties be still sat here, or should an engine have coupled up and taken them away?

Looking through the F4 list of the several 6K91s that have entered the sim I see one with UID 6K91MFX0951 which enters Eggborough PS at 09:51, runs to Sudforth, detaches engine 0K91 and then has no further activity. I believe the empties I have sitting there are from this train.

I know that in the quoted post you state that some empties may not have a forward working, but in this particular instance 6K91 is blocking the job up quite a bit. I can't perform the engine change for 6K86 on the Down Goole line as trains for Eggborough and Drax are due through before it's due back out again.

Is this an oversight, or are those empties supposed to just remain there once the engine uncouples at 10:02? As it stands the only thing I can do is hold 6K86 at Knottingley South Junction and wait for one of the other two empties to be taken away. I've attached a screenshot showing the train I believe is the problem in the F4 list.

Thanks.