Page 1 of 1
| Timetable editing and chaining 07/04/2011 at 03:08 #2780 | |
northroad
872 posts |
Having a go at creating a couple of timetables for adjoing Sims so that it can be chained........ and also realise that this is going to take time...... However can anyone tell me, if I create a service on one Sim but because of it's movements I have had to split into two sections i.e 6E75 and 6E75-1, does the same train have to be listed on the timetable editor for the adjoing sim when it enters there as 6E75-1 or will the sim recognise just 6E75. Trying to make sure that the two timetables will be compatable and all that..... Geoff Log in to reply |
| Timetable editing and chaining 07/04/2011 at 03:08 #14856 | |
|
northroad
872 posts |
Having a go at creating a couple of timetables for adjoing Sims so that it can be chained........ and also realise that this is going to take time...... However can anyone tell me, if I create a service on one Sim but because of it's movements I have had to split into two sections i.e 6E75 and 6E75-1, does the same train have to be listed on the timetable editor for the adjoing sim when it enters there as 6E75-1 or will the sim recognise just 6E75. Trying to make sure that the two timetables will be compatable and all that..... Geoff Log in to reply |
| Timetable editing and chaining 07/04/2011 at 05:39 #14860 | |
Peter Bennet
5402 posts |
I know for ARS they need to match across the join or it all goes horribly wrong can't say for sure on non-ARS but I'd suggests it's best practice to match. Peter I identify as half man half biscuit - crumbs! Log in to reply |
| Timetable editing and chaining 07/04/2011 at 13:37 #14863 | |
|
northroad
872 posts |
Thanks Peter sound advice...a bit like always expect the unexpected Geoff Log in to reply |
| Timetable editing and chaining 07/04/2011 at 19:52 #14880 | |
GeoffM
6376 posts |
Well, the later ARSs (Edinburgh+) are more tolerant of different line codes and suchlike across a signalbox boundary, but in general both the ARS and the train handover code will initially look for the full ID in the receiving simulation before dropping back to the four-character ID and searching for that instead. So yes, the exiting simulation can have 6E75-1 and the receiving simulation 6E75 and it should be ok. The reverse, however, is not true. There is a plan to have an option for a suffix to optionally increment across a signalbox boundary to get around the issue of a train leaving simulation A, entering B, leaving B, and re-entering A, all with the same headcode. Thus in simulation A it would be called 6E75-1, in simulation B 6E75-2, and back in simulation A it would be 6E75-3. SimSig Boss Log in to reply |
| Timetable editing and chaining 08/04/2011 at 03:12 #14891 | |
|
northroad
872 posts |
Thanks for the update Geoff. I will take Peter's advice and use 6E75-1 for both the exit from A and the entrance to B........if a problem still exists then this should be picked up by initial testing of the two together. It would be interesting to know though for someone setting out to do a timetable for the first time the easiest way to do it. I know easiest is probably not the correct word for this becuase taking on a task like others have done before is a bit awesome, but those that are more experienced at timetable creating must have some thoughts as to the steps to be taken. I have gone headlong into this but useful advice should not be dismissed. Simple things like do you have a run through when you have only listed so many services into the timetable editor or would you wait until you have the full timetable in there and then back track with corrections. Tips on this might be in the Wiki....must admit I have not looked....but any tips would be greatly appreciated. Log in to reply |
| Timetable editing and chaining 08/04/2011 at 12:53 #14899 | |
DriverCurran
688 posts |
Geoff The way I find that works (and this depends on the 'time period' of your timetable) is to create seperate timetables for each type of stock, so for instance if you knew there were 40 (just as an example) that were meant to be say HST's then you create a timetable in each sim (e.g. somewherejunctionHST.wtt) and (notownHST.wtt) and test those trains work, then keep doing this for each type of stock, if known. I would do all the freight trains as one type. Once all the base timetables have been done I then start to use the merge facility to merge each of these timetables doing a test on each merged timetable until I have the timetables fully built. Be aware that this is a very drawn out procedure and no doubt some of my fellow timetabler's have easier/quicker ways to do this. Also I have never done rules in this way so not 100% if they will merge correctly, so will bow to others more indepth knowledge. Hope this is of some use. Paul You have to get a red before you can get any other colour Log in to reply |
| Timetable editing and chaining 10/04/2011 at 13:12 #14945 | |
clive
2789 posts |
Can I suggest the use of Convdata and text files? Being text, they're really easy to merge, and a lot of repetitive stuff gets done for you. There's a tutorial on my web site.
Log in to reply |
| Timetable editing and chaining 10/04/2011 at 20:35 #14956 | |
|
bill_gensheet
1414 posts |
To echo Paul's comments, keep the timetables in bite size chunks for as long as possible. Divided by stock type is certainly one good option, but if you think the diagramming is stricter still, you may be able to work with public timetable or service grouping too. For example Edinburgh 1993 was written consisting of 5 freight timetables, 1 engineers, and 10 passenger ones.
Coal (Longannet) Coal (English) Coal (Methil) Coal (Cockenzie) Engineers Express (that is class 158's to anywhere but Glasgow, and the loco hauleds) Edinburgh - Glasgow IC - initially split further into ECML, sleeper & WCML Table 225 - Shotts line EMU's Table 230 Table 242 (class 150) Table 242 (Class 117) Hope that gives you some ideas. As for writing, the switching between sim editor and text format is worth doing, each is best for certain parts of the job. Use the sim editor to get one train right, or copy an existing timetable. Duplicate in the sim editor or with the convdata codes Clive has mentioned Use text to make later corrections using find/replace. Consider using PFE32 as a text editor regards Bill Log in to reply |
| Timetable editing and chaining 11/04/2011 at 06:20 #14965 | |
|
northroad
872 posts |
Once again thanks for the tips guys this is really useful information and probably not just for me. Geoff. Log in to reply |