Page 1 of 1
Chaining/ Seed Trains. 25/01/2018 at 11:08 #105434 | |
Colourlight
117 posts |
I,m considering starting a new project. In the light of which I have a couple of questions. Is it possible to chain Peterbough as a Loader sim to Cambridge as a Non Loader sim? When seeding a train in the timetable how do you identify the actual location that you want the train to seed at when selecting one from the list? Thank you. Last edited: 25/01/2018 at 11:08 by Colourlight Reason: None given Log in to reply |
Chaining/ Seed Trains. 25/01/2018 at 12:02 #105435 | |
9pN1SEAp
1181 posts |
I can't answer the first part, but when you tick "seed train" the "Entry Point" changes to "Seed Point", and the drop down becomes a list of signals, as per the signal number plan in the Reference Section. Any train you want to be in the area at the start of the sim (i.e. doesn't cross from a fringe area) needs to be seeded. If that signal matches the first location in the TT, it will follow timetable and schedule its departure or follow next action. If it's not at the first location, the train will start moving towards the first TT location. You'll see in some timetables that seed trains don't always use a "normal" headcode, where they seed at a siding/platform, and have one TT entry whose only function is to change to a proper TD which either interposes automatically under ARS or manually done by the signaller. That's a more advanced topic though. Jamie S (JAMS) Log in to reply The following user said thank you: Colourlight |
Chaining/ Seed Trains. 25/01/2018 at 14:01 #105439 | |
clive
2789 posts |
Colourlight in post 105434 said:I'm pretty sure it will work just fine. It's not a Loader v non-loader issue. The chaining protocol changed in the dim and distant past, but I'm pretty sure the most recent release of Cambridge uses the current protocol. Log in to reply The following user said thank you: Colourlight |
Chaining/ Seed Trains. 25/01/2018 at 15:52 #105449 | |
Danny252
1461 posts |
clive in post 105439 said:Colourlight in post 105434 said:Having given it a quick test, trains travel between the two sims correctly. I'm not sure what happens if a train is sent to Cambridge that has "new" TT features enabled (e.g. Cambridge's TT Editor doesn't know what speed classes or "Overhead DC" are), or whether a train coming the other way will pick up speed classes, etc., when entering Peterborough.I'm pretty sure it will work just fine. Log in to reply The following user said thank you: Colourlight |
Chaining/ Seed Trains. 25/01/2018 at 23:07 #105472 | |
Jan
906 posts |
If I remember correctly (it's been a while since I tried it), at least speed classes are taken from the timetable of the sim the train is currently running in. Given the existence of sim-specific speed classes, this does makes sense.
Two million people attempt to use Birmingham's magnificent rail network every year, with just over a million of them managing to get further than Smethwick. Log in to reply The following user said thank you: Colourlight |
Chaining/ Seed Trains. 26/01/2018 at 12:23 #105483 | |
Colourlight
117 posts |
Thanks to everybody who replied. I,m working on two timetables. Cambridge 1985 which I checked for timing errors and added a number of overnight coal trains from Toton to mainly Temple mills via Whitemoor . This addition was in direct response to requests from my hosting guests who wanted more trains (well, one certain Aussie anyway, lol!) Now I,m in the very early stages of doing the same thing to Peterborough 1985. In addition though, I will have to make them both compatible with each other. The March Peterborough line is especially busy as this was the doomed Speedlink era and at the time the truncated former Whitemoor Marshalling Yard was a Speedlink Yard. I,m also considering adding further trains which will be the winter timetable sugar beet traffic although I have no schedules for those at the moment. And if you have not already guessed I live in March and have worked in a number of signalboxes in that area for more years than I care to remember. Log in to reply |