Derby 1992 Summer Timetable

there is no path available for trains to come from Bardon Hill through towards Moira West. this affects a couple of MGR workings and a Departmental working which have been left out the timetable currently.

Joe

Thanks for uploading this Joe. I worked in Derby TOPS Office at that time and have been long looking forward to a Derby TT from that era as it was a busy time with all the mail trains at Derby and the many associated shunt moves, still plenty of freight (much of which had relief at Derby), many light engine moves on and off 4 Shed and all the ECS to and from Etches Park. I just have one query posted below:-

jc92 in post 116780 said:

there is no path available for trains to come from Bardon Hill through towards Moira West. this affects a couple of MGR workings and a Departmental working which have been left out the timetable currently.

Joe

I'm not sure why this can be as the Welton Blockade TT (which for some reason is not on the downloads page) contains various trains running from Bardon Hill to Moira West and beyond.

Regards,

Phil.

Phil/Vince,

thanks for that. I tried every combination possible other than using the T.C. location so I will add the offending trains for next release.

I'd welcome any input or feedback you both have as doubtless there will some errors or ommissions you can assist with.

Joe.

Hi Joe,

I'm glad you've been able to make some use of the information supplied by myself and Nick. I look forward to seeing all the extra trains and shunt moves. Derby really was a busy place late into the night with the mails and the ECS to 4 Shed, Etches Park and going through the wash. Incidentally, when sets went through the wash they only came part way out onto the pilot or connecting line. This was because they had a driver each end and once the rear power car cleared the hand points at the end of the wash road they shunted straight back into the depot without coming completely out of the depot. Also, when they came off 4 Shed they would often stop behind DY476 GPL on the Pilot line (again because they had 2 drivers on) and go around to Etches Park from there. With so many sets to get fuelled and washed the signalman, in order to keep things fluid, would tell the driver where to stop and change ends (on the Pilot, Dn Goods at Derby North or round Chad Curve behind DY472 Sig) in order to not keep sets waiting out for too long. The Centre Panel man really earned his money from 2200 to around 0200 when it started to quiet down a little.

I've just discovered another error with 2M04, arriving Marlock at 0948 and shown to form 2F08 0900 Matlock - Derby. I think I've discovered the earlier problem with 2M04 standing all that time at Derby. Should it not depart Derby at 0817 instead of 0917? That way it would a) remove the platform clash with 1E27 and b) be at Matlock at 0848 to form 2F08 0900 Matlock - Derby instead of 5M04 0849 shunt to Peak Rail (which I see from the TT notes is an issue with Matlock GF). I did think at the time that 2M04 standing for so long created a large gap in the Matlock service. I have to admit I don't recall units having to shut themselves in at Matlock, but it was a long time ago, and now I come to think of it I've an idea that in 1992 the Matlocks, while having TOPS train schedules, were not live in TRUST and may even have just ran up and down with the same reporting number as the service was essentially self-contained. I seem to recall it was only with the start of privatisation in 1994 and the introduction of performance regimes that Matlock services were given individual reporting numbers, their schedules became live in TRUST and we had to start reporting them. Again, I'm calling on memory for some of this, so if anyone reading this has more accurate information I'll happily stand corrected.

I don't know if this is a TT bug or a sim bug with Denby as an entry location, but 7A24 0835 Denby - Ratcliffe was reported it would be 12 mins late entering the sim, I'm now up to 1020 and it still hasn't entered.


Regards,

Phil.

Denby trains not entering seems to be a sim issue. The timetables are valid and there's no delays. I've noticed the same thing.

It's a shame about the various bugs that various people have reported this sim has, because most of them appear quite minor but prevent timetables being written to take the sim to its full potential. THe modern TT's are ok but very predictably clock-face, whereas this is the first TT that makes use of more of the shunt moves and of the locations for where traffic no longer exists in the modern world.

I'll review the 2M04 issue tonight. I think you may well have solved that one.

Apologies for the issues. The timetable wasn't fully tested due to the problems with the sim but I appreciate being a Guinea pig!

No apology necessary Joe, I'm glad be of help and quite enjoying putting to good use some of my dormant grey matter trying to think of what we did back then, and having a good chuckle at some of the memories this has jogged.

The shunts out of EPS and back can he set to shunt "half way" out of EPS before dropping back in but It will cause you to get penalised for not getting a slot/permission to go back in.

Personally I run all the sims as realistically as possible rather than paying attention to performance scores so if setting it to 'Half way' loses me a few points for the sake of realism then so be it.

Incidentally, in real life it used to be possible to set a route from DY426 Park to the Pilot and then from DY427 Pilot to Etches Park to allow the Park to shunt back and forth to their heart's content. In reality this was never used as the two routes had a habit of sticking in, so instead they just cleared 426 to shunt half way out off the wash. When something wanted to come out the supervisor would tell the signalman when he could return 426 to Danger to then set a new route for a departing move, or tell him to let a departing move leave on the existing signal and then take it back. If the Park had 426 and the signalman had something to depart south via the Pilot or Connecting lines he would ring the Park supervisor first and ask to take the shunt back.

Keep them coming!

Not sure whether this is a bug: 6M01 is scheduled to be taken over by 1V40 but it has no Branston Jn timing point (with arrival and passing time) like other trains that are being taken over there. (I forgot to loop it - decided to loop it at Elford instead.)

There is a conflict between 1M06 and 1M79 on departure from Derby towards Sheet Stores Jn. Does 1M06 leave Derby too early by accident? 1M79 is scheduled just half a minute later and does not call at Long Eaton.

Another conflict: 1M00/5M00 (15:50 to 16:10) with 1M12 (16:01 to 16:05) on platform 1 in Derby.

There is a conflict between 1M06 and 1M79 on departure from Derby towards Sheet Stores Jn. Does 1M06 leave Derby too early by accident? 1M79 is scheduled just half a minute later and does not call at Long Eaton.

It will work if you let 1M00 call further along the platform. Right now it's mostly on 1A, only its loco 0M00 occupies the 1B track circuit.