Page 2 of 2
Trains with duplicate train describers 30/05/2014 at 11:53 #61130 | |
jc92
3701 posts |
telephones to advise of out of course running from the WTT and/or use of TRUST terminals which will show delays/early running etc.
"We don't stop camborne wednesdays" Log in to reply The following user said thank you: Muzer |
Trains with duplicate train describers 30/05/2014 at 11:57 #61132 | |
Muzer
718 posts |
Makes sense. Thanks!
Log in to reply |
Trains with duplicate train describers 30/05/2014 at 13:39 #61135 | |
KymriskaDraken
963 posts |
I remember one morning when I was working Little Mill Jn box (fringe to Newport panel, and AB up to Abergavenny) I had an 0Z00 fire in from Newport. The Newport Signalman wasn't sure what it was "It's going up your way somewhere..." so I decided to stop it and ask the Driver. The train pulls up at LM115 (the up section signal) and the Driver comes on the phone: "'ello Bobby, which train am I?" Log in to reply The following users said thank you: jc92, JamesN, kbarber |
Trains with duplicate train describers 30/05/2014 at 20:42 #61151 | |
DriverCurran
695 posts |
" said:Thank you for all of the information on train describers.You are correct Geoff in this assumption, 02 was between 1961 and 1981 or somepoint between the two. I am working on a 1982 version. The way I lay out the info in the timetable is as follows YYYY from - to [zz] where XXXX is the departure time, from and to no need to comment lol and [zz] is the two digit route code so for a train in my area would have for instance 5H52 04+50 St Leonards West Marina Depot - Hastings [01] Paul You have to get a red before you can get any other colour Log in to reply The following users said thank you: northroad, TimTamToe |
Trains with duplicate train describers 31/05/2014 at 10:08 #61166 | |
kbarber
1764 posts |
" said:" said:Broadly jc92 is right and in Cornwall I wouldn't expect there to be any information other than the standard bell code for class of train plus phone messages (we didn't have TRUST in my day so I've no experience of using it).Of course, none of these systems were capable of identifying individual trains. So you can imagine what an incredible advance it was when the 4-digit description came on the scene in the early 1960s. The signalman could now tell exactly which train he was dealing with, rather than having to know all the trains a particular description might refer to and use his knowledge of the timetable to work out which was which. In those far-off days, even the largest powerboxes covered areas we would now consider trivial. (Controlling the southern West Coast Main Line from just five boxes - Euston, Willesden, Watford, Bletchley and Rugby was considered a magnificent achievement at the time.) The idea that there might be duplicate headcodes within a box area simultaneously was considered pretty far-fetched and, as signalmen were expected to know the traffic (and were used to having nothing more than the first digit - the class the bell code spelt out) it was never imagined it might cause a problem. The big exception, of course, was Euston where (as jc92 says) the same codes kept repeating for the DC lines. This was to allow a high degree of automation of description sending with the primitive relay technology then on offer. (For the same reason, DC lines ECS ran as class 3 rather than class 5 until the new Willesden Suburban - later Wembley Suburban - box was opened in 1988.)Thanks for the detailed information. I have a question that might seem obvious but I've looked and haven't found a clear answer - in (for example) mechanical signalboxes that don't have modern train describers (eg the far west end of the GWML to Cornwall, IIRC?), how do they know which train is which in those cases? Is it just that the areas are simple enough that it's easy to tell from the class and time alone, or do they have some other way of transmitting the destination/route using bell codes, or what? Going further back and looking at some of the busier areas, there were numerous ways of doing it. As I said, one way was the electro-clockwork train describer in conjunction with block bells; that would most often give you (in effect) the first two digits of a description (class and route/destination), leaving the signalman to work out exactly which train it was. The Southern was much more concerned with route than class so their standard bell codes (if I recall correctly) only distinguished between passenger, ecs and freight but in each case with a 'main' and a 'branch' variant (so 3-1 for main passenger, 1-3 for branch passenger). Of course signalmen still had to work out for themselves which train was which - where there were several successive junctions, a train you received as 'main' might need to be offered forward as 'branch', for example. Some areas made use of 'additional' (routing) codes. There were complete alternative sets - the A, B and C codes, which were shown on printed notices issued to the boxes where they were in use. I know for a fact that some boxes used at least two in addition to the standard range; the chances are some used all three. Each set was usually linked with a special Train Entering Section code that would be specified in the signalbox special instructions. In later years signalmen were expected to know which train was which in order to send the special TES, but further back it would be initiated in response to whistle signals the driver was required to give (specified in the Sectional Appendix). So for example, a train approaching St Albans South that continued on the main line through the Cricklewood area wouldn't use any specific whistle code. A train for Brent Up Sidings would whistle a code of 2 short and 1 long blast; St Albans South would then use the special TES code 2-2-2 to Napsbury. Because the section was short, Napsbury would already have offered on to Radlett so would again use the special TES, whereupon Radlett would offer forward to Elstree using the appropriate A code. If the train was for Brent Down Side or the Acton Branch, the whistle code would be 1 short 1 long, the special TES would be 2-2-4 and Radlett would offer forward with the B codes. In some cases particular codes extracted from the additional codes would be used; between St Pancras and Cricklewood (down direction) ecs for Cricklewood Carriage Shed would be 2-2-1-5 (which was one of the A codes) and for Cricklewood DMU Sidings 2-2-1-3 (a B code), while a light engine for Cricklewood Depot was 2-3-5 (which didn't appear in any of the additional codes). These were specified in full in the SBSIs. The Western made some use of routing codes and in some cases they distinguished between trains booked to call or not at certain stations (Taunton - Exeter - Newton Abbot was one stretch where they existed). The 'not booked to call' variants allowed signalmen to distinguish which trains they could accept under Regulation 5 (warning arrangement) at the major stations (not permitted for non-stops). Signalmen were simply expected to know which train was which in order to initiate a special code. The North and West London lines relied on freight trains being advised by phone. Junction Road phoned direct to South Tottenham and vice versa (there was also a 2-2-4 TES for trains going towards Tottenham South Junction but nothing in the up direction). It would be common to advise 2 or even 3 trains at a time and we'd be expected to keep track of which had actually passed for ourselves. The messages were pretty casual ('Next up you've got the Hawkesbury lane, then the Severn Tunnel's behind the passenger', for instance). Elsewhere the norm was to circuit from box to box, so as soon as you'd accepted a train you picked up the omnibus phone to be told what it was you'd accepted. This kind of working was inevitable, given the number of yard-to-yard trips and the variations in timetabling etc. I didn't experience any other ways it was done; I know some areas used special headlamp codes (in the days before 4-digit descriptions) but whether these were used with routing bell codes or what I simply don't know. Hope that helps. Log in to reply The following users said thank you: Muzer, northroad |
Trains with duplicate train describers 31/05/2014 at 16:00 #61172 | |
Danny252
1461 posts |
Quote:The Southern was much more concerned with route than class so their standard bell codes (if I recall correctly) only distinguished between passenger, ecs and freight but in each case with a 'main' and a 'branch' variant (so 3-1 for main passenger, 1-3 for branch passenger).3-1/1-3 aren't strictly Southern, and were in the BR standard regs at least. There's also a code for branch freight, but I'll be buggered if I can remember it (perhaps 1-2?). However, that isn't to take away from your point about the Southern having all sorts of crazy routing codes! Quote: Some areas made use of 'additional' (routing) codes. There were complete alternative sets - the A, B and C codes, which were shown on printed notices issued to the boxes where they were in use. I know for a fact that some boxes used at least two in addition to the standard range; the chances are some used all three. Each set was usually linked with a special Train Entering Section code that would be specified in the signalbox special instructions.IIRC, A/B/C routing codes were an LMS/MR (and maybe BR as a whole?) thing, and I've never come across a similar listing for the GWR/WR. I'd also debate most routing codes having a different TES code - which was used seems mainly to be based on when the signalman found out about the route. If he knew at the time of offering, a routing code was used, whilst cases where he found out later (e.g. the whistle codes you discussed) would warrant a TES code, as it's a bit late to give a different ILC code! Of course, the special TES would usually cause the box in advance to use a special ILC when offering on. Quote: The Western made some use of routing codes and in some cases they distinguished between trains booked to call or not at certain stations (Taunton - Exeter - Newton Abbot was one stretch where they existed). The 'not booked to call' variants allowed signalmen to distinguish which trains they could accept under Regulation 5 (warning arrangement) at the major stations (not permitted for non-stops).Not sure about the Reg 5 part, but it may apply to Taunton/Newton Abbot - for Exeter, at least, the non-stopping codes were important to ensure that the train was not brought to a stand within the station, and also because the braking distances between signals were not sufficient for a fast-moving train. You then ended up with the strange situation where several signalmen would all be stood by their block instruments, waiting for acceptance from the box in advance before they accepted it from the one in rear! Log in to reply |
Trains with duplicate train describers 31/05/2014 at 17:37 #61173 | |
Late Turn
699 posts |
A couple of examples that still remain in use: the Barton (S Humbs) branch unit is (or was, at least, when I last visited) signalled throughout as 1-3. Back on the Midland, the special TES signal 2-2-2 is used between Ashwell and Manton for Up trains towards Corby (ILC is passed forward immediately upon receipt at the two intermediate boxes, so there's no opportunity to 'convert' it to a routing ILC signal), with a whistle code (1L 1S) still given by such trains approaching Ashwell box. I gather there are still some complex routing codes used around Worcester too.
Log in to reply |
Trains with duplicate train describers 31/05/2014 at 20:12 #61179 | |
DriverCurran
695 posts |
" said:[quote="Muzer" post=61129][quote="kbarber" post=61122]The webpage here http://www.bluebell-railway.co.uk/bluebell/walkers.html gives basic information on one of the last if not the last of these type of instruments still surviving in use. Paul You have to get a red before you can get any other colour Log in to reply |
Trains with duplicate train describers 31/05/2014 at 23:16 #61187 | |
Danny252
1461 posts |
I know that some exist(ed) in the Shrewsbury boxes (probably Severn Bridge Jn-Crewe Jn), though I'm not sure that they're still in use - I recall reading that they had become unreliable and were rarely used.
Log in to reply |
Trains with duplicate train describers 01/06/2014 at 04:54 #61192 | |
uboat
219 posts |
Earlier this year while viewing the live feed from Sussextrains.co.uk I clicked on a 2Dxx around Redhill to read the timetable but ended up with the timetable from a 2Dxx around Lewes. Log in to reply |
Trains with duplicate train describers 23/06/2014 at 09:22 #61945 | |
northroad
872 posts |
" said:Quote:I have continued to test this with the timetable that I am writing and got the hic cup that some feared would happen. 2H06-1 and 2H06-2 was not at all liked by ARS or the F2 function when both were on the board at the same time. This happened when both trains were on the same panel i.e. Sutton area. First I had the message that there was a duplication of the code and then when I looked at F2 to see where they both were I realised that 2H06-2 was not showing at all. Both of the two were shown on the Sim, however 2H06-2 had become non ARS and it was only by manually signalling it through to Sutton from Wallington/Carshalton Beeches and it arrived at Sutton to re-describe did the problem sort itself.For example train one I have given the TD as 2H01 and the second as 2H01-1. Moral in the story is that I think I may have to keep away from 1's and 2's or A's and B's and use a unique train describer. I will have to put a note in the general notes though that some services have had their TD's changed to avoid confusion. Shame really as it takes away the orthentisity of the timetable with all of it's glitches that may be in there. Geoff. Log in to reply |
Trains with duplicate train describers 23/06/2014 at 21:37 #61952 | |
Finger
220 posts |
That's strange, since it works for me perfectly on the Peterborough sim. Tried creating two timetables 1X00-1 and 1X00-2, they entered and ARS routed them, even honored the distinction between the two. From what you describe about F2 I reckon you must have seriously confused the sim. F2 should always tell you the real thing and if it gave you two trains with the same ID where they should be different, it must have been confused by either the timetable or your action during the game. If you want to investigate the problem further, please attach either a save or the timetable. Post has attachments. Log in to view them. Last edited: 23/06/2014 at 21:41 by Finger Log in to reply |
Trains with duplicate train describers 24/06/2014 at 09:47 #61967 | |
northroad
872 posts |
" said:That's strange, since it works for me perfectly on the Peterborough sim. Tried creating two timetables 1X00-1 and 1X00-2, they entered and ARS routed them, even honored the distinction between the two.Thanks for coming back to me on this Finger. I have run this through again and think I might just have found out what happened. I reckon it is what goes on in the background around Selhurst and Norwood Junction etc. 2H06-1 is routed from Victoria through to Sutton and it goes off panel at Selhurst and re-appears at West Croydon. When it goes off and on panel it shows it is routed off the planned path in the message box. It reappears at the correct time. Meanwhile 5H02 has reached it's destination of Epsom Downs and has just tried to re-describe to 2H06-2 but comes up with the error message trains duplicated n the same area. I have also noted that I have not put anything between Selhurst and West Croydon in the timetable such as Gloucester Road as a passing point. I guess some of it or probably all of it is my fault but it just shows how you have to concentrate on getting everything tickety boo when compiling a timetable. Geoff [attachment=2524]2H06problem.ssg[/attachment] Post has attachments. Log in to view them. Log in to reply |
Trains with duplicate train describers 24/06/2014 at 11:12 #61971 | |
Finger
220 posts |
Quote:I guess some of it or probably all of it is my fault but it just shows how you have to concentrate on getting everything tickety boo when compiling a timetable. Exactly! The problem is your timetable mention both train simply by "2H06" in activities, and the sim then can't decide whether it's -1 or -2. You should use proper IDs as next workings, etc. There are several such occurences in your timetable - this is a list of them (eg. list of trains and their locations at which they reference something nonexistent/misnamed): $ xpath -e '//Timetables/Timetable/Trips/Trip[Activities/Activity[not(//Timetables/Timetable/ID = AssociatedTrain)]]' -e 'concat("Train ", ancestor::Timetable[1]/ID, " at ", Location)' /tmp/SavedSimulation.xml
Log in to reply The following user said thank you: northroad |
Trains with duplicate train describers 26/06/2014 at 09:50 #62070 | |
northroad
872 posts |
Thanks for your help on this. It is a question of when do I change them so that I do not any conflict. I think I will plod on inputting at this moment and when finished then have a look at how many conflicts I could possibly have and change those. I know I could change the second letter digit but the trouble with that is that some users memorise the code as to where and what the routing will be. Perhaps I should have laid it all out in something like an Excel spreadsheet before I started as I know some do that also. I blame those WTT writers who should have foreseen something like Sim Sig coming along one day....... Geoff Log in to reply |
Trains with duplicate train describers 26/06/2014 at 10:10 #62071 | |
TimTamToe
664 posts |
" said:Thanks for your help on this.I haven't had the time yet to look at what you attached Geoff, but what I gather from what Finger wrote is that as well as adding a -1 or -2 to the train ID, you also need to do this in the activities for next train. so have N:2H06-1 rather than N:2H06 I'll try and have a look for you Gareth Log in to reply |
Trains with duplicate train describers 26/06/2014 at 10:37 #62072 | |
northroad
872 posts |
Thank you for your help also Gareth. In order to stop you spending a lot of time on this I can confirm to you that I was going back and changing the activity field for the associated train. If you use the analyse function in the timetable this helps to alert me to the fact that it needed to be done. As I have said previously, I admire anyone who has submitted a timetable for the enjoyment of others. With this project on Victoria I now know only too well how much time and effort is required...... Geoff Log in to reply |
Trains with duplicate train describers 26/06/2014 at 10:53 #62073 | |
TimTamToe
664 posts |
" said:Thank you for your help also Gareth.That's not a problem Geoff, I only thought it may save you time at the end if from now on whatever trains you enter you also have the correct activity field Having written a modern TT for Vic I know how tough it can be with such a complex area let alone writing one for days gone by! Keep persevering, it'll be worth it in the end and just shout if you need anymore help Gareth Log in to reply |