Defining Movement Orders In Scenarios

From SignalWiki
Revision as of 19:01, 2 July 2011 by ErwinL (talk | contribs) (Created page with 'You can define movement orders for each scenario-defined train, either a spawning train or stabled train The following types of Movement Orders are available: 0: Renumber 1:…')

(diff) ← Older revision | Approved revision (diff) | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

You can define movement orders for each scenario-defined train, either a spawning train or stabled train

The following types of Movement Orders are available: 

 0: Renumber
 1: Turnaround
 2: Couple
 3: Uncouple
 4: Call
 5: ChangeDriver
 7: PullUp
 8: StopShort
 9: StopAhead
10: SwitchLock
13: StableCars
14: SpotCars
??: SpotCarsSpecify
16: unknown - functional in Amsterdam CS simulation
17: RunAround
18: ContentChanges

==General 

<SpawningConsist id="loc>9903" physics="7" maxTechAllowedSpeed="80" track="SPAWN_TC2_0" startTime="08:05:20" speed="80" type="EL" destination="Velp" commDestination="Vp" isEngineeringTrain="false" consistTemplate="28">
   <PlatformStops>
      Arnhem,7,--:--,08:30,Arnhem-Velperpoort,1,08:35,08:38
   </PlatformStops>
   <MovementOrders>
       <Order type="Turnaround" track="" station="Arnhem-kap" />
       <Order type="Couple" track="" station="Arnhem-berg" with="9903w" newID="9903" calls="true" callsForDelay="false" newDir="R" />
   </MovementOrders>
</SpawningConsist>


Return to Scenario Creation

Retrieved from ‘https://wiki.railsignalling.org/index.php?title=Defining_Movement_Orders_In_Scenarios&oldid=1648’