Changes for page Documentation
Last modified by Soeren Domroes on 2025/01/30 12:05
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. sna1 +XWiki.als - Content
-
... ... @@ -113,11 +113,11 @@ 113 113 114 114 === Station-to-Station === 115 115 116 -Fuctions $void railArrival(int train, int station)$and$int railDeparture(int train)$should be used at the end of every Station-to-Station-Controller.116 +Fuctions **void railArrival(int train, int station)** and **int railDeparture(int train)** should be used at the end of every Station-to-Station-Controller. 117 117 118 -At the end of every Station-to-Station-Controller the trains should stand in one station, because every Controller starts with the train in standstill.118 +At the end of every Station-to-Station-Controller the trains should stand in one station, because every controller starts with the train in standstill. 119 119 120 - 120 +Contact reading in triggers should only used when it is clearly determined which train will fire the contact. 121 121 122 122 === TrainController === 123 123 ... ... @@ -125,10 +125,8 @@ 125 125 126 126 === Speed: === 127 127 128 - 129 - 130 130 * SLOW: for the stations 131 -* CAUTION: for pointsandslowdown129 +* CAUTION: for slowdown (and optional points) 132 132 * NORMAL: for the other tracks 133 133 134 134 == Codestyle == ... ... @@ -141,8 +141,37 @@ 141 141 bool <track>_req[<trainAmount>] contains the requests for each track and train. Before the availability of arrays, we used bool <train>_<track>_req. 142 142 int <track>_perm contains the trainnumber of the train, who is allowed to drive on <track>. 143 143 144 -== Quit, PauseandCleanup==142 +== Deadlock Prevention == 145 145 144 +An example controller for deadlock prevention is located in// rail-repo: docs/deadlocks/resolve_deadlock.sct// 145 + 146 += C Controller = 147 + 148 +The C controller wraps the basic railway interface and creates an correct environment to run the generated controller. 149 + 150 +== Make Script == 151 + 152 +A make script written in Python is located in rail-repo: code/make.py 153 + 154 +This script will compiel the whole controller for simulation or real railway and optionally executes it.// 155 +// 156 + 157 +Calling**// python// //make.py//** without further command-line arguments will print a help message with all available command line options. 158 + 159 +Make Script Features: 160 + 161 +* Header-file will be included automatically 162 + 163 +Results are located in //rail-repo: code/build/// 164 + 165 +== Railway Interface == 166 + 167 +Provided functions are defined in// rail-repo: code/hostcode/controller.h// 168 + 169 +== Interaction == 170 + 171 +=== Quit, Pause and Cleanup === 172 + 146 146 Quit, pause and cleanup functionality is handled in the c interface. 147 147 148 148 **CTRL+C** (SIGINT)** **quits the controller
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 -9470 9961 +9471003 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9470 996/Documentation1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9471003/Documentation