Progettato da Rob é realizzato da Mark, questo semplice progetto sorprendentemente possiede alcuni problemi complessi che possono essere risolti solo tramite le pianificazioni. Esso é l'evoluzione di uno dei primi lavori di Mark con il "Dueling Dampfloks".
Ogni blocco é settato sullo stesso tempo di attesa di 1 minuto.
Originariamente c'erano 7 itinerari che definivano i possibili collegamenti tra i blocchi:
Notare che tutti questi itinerari sono impostati sul senso orario (clockwise) partendo dal blocco all'angolo destro in alto A2 ("le 13:00"). Questo definisce la direzione generale del tracciato come oraria e significa che "l'avanzamento verso ogni blocco successivo avviene in modo orario". Per esempio, andare avanti da C porta in A1 e andare indietro da C porta in A2.
Ogni itinerario é impostato su "Both Directions" e tutti i deviatoi sono stati programmati per operare in entrambe le direzioni. Per esempio, con l'itinerario r4 (C-A1) il deviatoio t1 é impostato su diritto.
Tuttavia, durante le prove é diventati ovvio che tutte le loco in movimento devono essere orientate in senso orario. Questo significa che una vaporiera che procede in senso antiorario deve avere la testa rivolta nel senso errato. Per questo motivo, sono stati aggiunti the itinerari per permettere ad un loco di percorrere il tracciato in senso antiorario:
Questi itinerari sono stati settati su counter-clockwise tramite "From-To" con il senso di marcia "Forwards" (Avanti). Questo é quello che permette ad una vaporiera di percorrere il tracciato rivolta nella direzione "errata".
C'é un singolo gruppo di blocchi A1-A2, che é settato come sezione critica. Questo significa che se una loco prenota un blocco, esso prenoterá automaticamente gli altri.
L'obiettivo principale é quello di permettere ai treni di condividere il tracciato seguendo differenti percorsi allo stesso momento. Per esempio, un treno merci e uno passeggeri viaggia in senso opposto sulla stessa linea A1-A2 a nord (North). Oppure un treno minerario che porta carbone da D verso B, tornando nuovamente in D per ulteriore carbone. Le pianificazioni permetteranno all'operatore di programmare i differenti percorsi che possono essere presi dai treni senza avere la preoccupazione che uno blocchi l'altro. Rocrail gestirá tutti i minimi dettagli per assicurare che un treno possa superare l'altro ed entrambi possano seguire i rispettivi percorsi.
Using just basic blocks and routes two locomotives can be made to randomly move "around each other" on the layout, but not move around with any real purpose. For this reason, Schedules are used to define a "list of blocks" to be followed, and to allow more meaningful, enjoyable operations. Rocrail then uses the Routes to determine how to get from each block in the list to the next block.
When 2 locomotives both want to move into each others block, they will "deadlock" and not be able to move. In the simplest case, a 2 block layout A-B contains a locomotive in A that wants to move to B, and a locomotive in B that wants to move to A. Neither can move until the other locomotive gets out of its block, which the other locomotive cannot do until the first locomotive moves out of its block.
Rocrail must be able to resolve these conflicts, or fail with a message that says "This deadlock cannot be resolved." Note that you must design your layout to avoid deadlocks where possible, and make sure there is a solution available. Rocrail cannot make the "A-B" example above work, there is no solution. However, with a properly planned layout, Rocrail should be able to control all movements, halting one train temporarily while another one proceeds, and then moving the first train once the way is clear.
Critical Sections are groups of blocks that can only have one locomotive in them at a time. If a locomotive reserves one of the blocks in the critical section, all the other blocks are reserved for that locomotive at the same time. The top side of the Schedules Test Case layout is divided into two blocks to test this principle. A1 and A2 are linked so that if one locomotive reserves either block, it reserves both.
Work started on Schedule testing back in late spring of 2007, but with the onset of Summer, testing stopped for a while. It was renewed in the fall of 2007, with good results.
The first case was to test a single locomotive running a basic schedule, then test two locomotives running two schedules at the same time. For this reason, the first two schedules used were:
Note that these schedules were made to repeat by setting the Schedules drop-down in the Action tab to the same schedule. For example, schedule C-A1-A2-C had Actions > Schedules set to C-A1-A2-C.
Initially, a single locomotive running either of these schedules worked perfectly. However, running two locomotives at the same time would always deadlock in the A1-A2 part of the layout. This was fixed as of svn 1931. After the fix, one locomotive would run the first schedule while the other waits, then the second locomotive would run its schedule while the first waited.
Also, the locomotives used for initial testing were Electric locomotives, so even though they were moving correctly it was not obvious that they were moving backwards when running counter-clockwise
The next set of schedules tested Rocrail's ability to handle changing directions and non-circular schedules.
As of svn 1942, this worked perfectly. When the locomotive running the second schedule would enter A1, the other locomotive would halt in A2 and wait until the first locomotive was back in a siding. Then the waiting locomotive would continue past A1, and stop in C. The locomotive in the siding would move back out into A1, and the cycle would repeat.
This is an example of a Yard Switcher working while Main Line trains keep moving through the yard's entrance.
Rocrail could already be used to clean the layout randomly by simply attaching a cleaning car to a locomotive and starting it under Automatic mode. But because of all the stopping and starting involved, it was not very efficient, the cleaning car should be run at constant speed when possible. This schedule was designed to clean the layout more efficiently:
This was used as of svn 1946 to clean the layout, and also functioned perfectly.
The direction issue and locomotive placement became a problem when we tried to run the Dueling Dampfloks scenario originally envisioned back in the Spring. This quickly pointed out the following important points about Routes, Direction and Locomotive Placing:
Once Mark fully understood this, he got Dueling Dampfloks to run very well using these schedules:
You can see a short low-resolution video of the Dueling Dampfloks layout in action on You Tube: Dueling Dampfloks Video
Schedules are still evolving in Rocrail, and there are many unused fields in the dialog boxes that illustrate ideas that have not been implemented yet. Some of the ideas that still need to be developed are:
Sincronizzazione blocco This will allow trains to know that they are early, late or on time. Rocrail can then speed up, slow down, or even make a train wait as needed.
Each block already has a time associated with it in a Schedule. If the first block in the schedule is set for 0:00. and the next is set to 1:00, Rocrail should know if the train made it into the block at 0:30 (early), or 1:07 (late) and make a decision based on Time. Rocrail should hold a train in a block if it is early, and perhaps speed the train up if it is late. This is more complex than it seems.
Orari e uso dell'orologio This will allow schedules to be repeated only at specific times. Instead of having a schedule run, stop and then just run again, Rocrail should be able to run a schedule at 9:57, then 12:15, then 13:45. This is more complex than it seems, and brings up the idea of "Time" on the layout.
Gruppi di pianificazioni In the same way that we can link a set of routes into a schedule, we should be able to link a group of schedules into a Run. Note that we need a better word for this concept, but the idea is that the train first runs the Amsterdam to Paris schedule, then the Paris to Munich schedule, then the Munich to Amsterdam schedule.
Prioritá treno Fast trains should reserve blocks instead of slow trains where possible. However, a slow train must not be stopped indefinitely because there are too many fast trains using the track it needs. This is very complex, and implies aging, i.e. when a train is only a little bit late, you can stop it, but if it is very late, it must run with higher priority so it will not be "deadlocked" by faster trains that reserve the blocks it needs.
Binari di raddoppio Situations where a slow train is in front of a fast train should be handled as well, with the slow train "pulling to the side" at the next passing siding and allowing the fast train to get in front. This would mean setting up a single schedule with two or more lists of routes, or allowing you to specify two blocks for a single destination in a schedule. For example consider these two schedules:
We would always use the first schedule if no other train was on the layout. But if a train with higher priority was following this train, this train would use the second schedule and wait in C while the other train moves ahead of it.
Attivazione Funzione When a train completes a schedule, a specific function is activated. This might let a locomotive play a sound when it reaches its destination, or uncouple from its wagons. Using the Yard Schedule mentioned above, this might let one locomotive run 2 trains, by moving into a siding and coupling automatically, running a train out on the layout, moving back into the same siding, and then uncoupling using a Telex magnet.
This is one of the goals of the original Dueling Dampfloks layout, the idea of a switcher running two sets of wagons from each of the sidings while a main passenger train runs the layout.
This is already implemented, but it should be fully tested.
Attivazione uscita This will allow other actions to be taken when a schedule is completed, such as turning on or off lights, putting power on the rails in an isolated section, or any other kind of electrical action that can be controlled by an addressable decoder.
Le seguenti tabelle mostrano i dettagli di tutti gli elementi del tracciato.
|s1a1||B-enter, C-enter, A2-in|
|s2a1||B-in, C-in, A2-enter|
|s1a2||A1-enter, B-in, C-in|
|s2a2||A1-in, B-enter, C-enter|
|3||B||A1||all||t1 thrown, t3 straight|
|6||D||A1||all||t3 thrown, t4 thrown|
|6||E||A1||all||t3 thrown, t4 straight|
|1||B, A1, A2, B||cycle: 10 times||-|
|2||C, A2, A1, B||cycle: 10 times||using routes to/from will flip the direction bit of the train|
|3||D, A1, E, A1, D||cycle: 2 times||using routes to/from will flip the direction bit of the train|